# Package Size Estimation

Entrance：Work Preview Area>>>Package Size Estimation

<figure><img src="https://695199083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4PyzU9CRLR4XKbxmIEid%2Fuploads%2FIyA5D0LgFTXyMa9IofH1%2Fimage.png?alt=media&#x26;token=5fe6a209-9247-405b-9baf-e8e8dad2cebe" alt=""><figcaption></figcaption></figure>

## <mark style="color:blue;">1.Package Size Estimation Intro</mark>

* When launching playable ads, different channels have varying requirements for the package size (👉For details, please refer to:  [#currently-supported-a-d-networks--test-apps](https://doc.playturbo.com/export-and-deployment/playable-upload-specifications-for-networks#currently-supported-a-d-networks--test-apps "mention")).

  Therefore, during the creation process, **it is important to manage asset sizes to control the overall package size.**
* The "Package Size Estimation" feature allows you to check the <mark style="color:red;">current package size</mark> at any time during production.
* It is recommended to use the  "Package Size Estimation" feature multiple times throughout the production process to prevent exceeding the size limit.

## <mark style="color:blue;">2.Package Size Estimation Operations</mark>

* Click the "Package Size Estimation" button below the project preview area to obtain the current package size of the project (please wait for a moment).
* Once the estimation is complete, the package size under **high**, **medium**, and **low** quality dimensions will be displayed, providing a reference before applying or downloading the project.*(**Please Note: The estimated package size serves as an approximate reference. Due to different platform packaging mechanisms, the actual exported package size may vary.**)*
* Additional Notes: For the high/medium/low quality indicators, the platform applies different compression parameters to images, audio, video, and other assets in the project. Since compression rates vary across assets, there is no fixed compression ratio.
* <mark style="color:red;">Please Note: The actual package size is calculated based on the assets that</mark> <mark style="color:red;"></mark><mark style="color:red;">**have been added**</mark> <mark style="color:red;"></mark><mark style="color:red;">to the project.</mark>

<div align="left"><figure><img src="https://695199083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4PyzU9CRLR4XKbxmIEid%2Fuploads%2FMZ5YEOBtAZu8WmI5T9u3%2Fimage.png?alt=media&#x26;token=33b2e7c8-2359-4225-8441-e2e9e43d1238" alt=""><figcaption></figcaption></figure></div>

## <mark style="color:blue;">3.Asset Size Recommendations</mark>

1）Currently, the platform has the following requirements for the size of different types of assets (👉 [#id-4.asset-upload-format-requirements](https://doc.playturbo.com/playable-tools-content-editor/content-editor-user-guide/top-asset-library/project-assets#id-4.asset-upload-format-requirements "mention")) :

* Video: < 3MB
* Audio: < 1MB
* Static Image: < 1MB
* Sequence: < 8MB
* DragonBone: < 1MB

2）<mark style="color:red;">Please Note:  If you need to add a large number of sequences or video assets to your project, it’s recommended to</mark> <mark style="color:red;"></mark><mark style="color:red;">**compress the files externally**</mark>  <mark style="color:red;"></mark><mark style="color:red;">or</mark>  <mark style="color:red;"></mark><mark style="color:red;">**adjust the implementation method**</mark> <mark style="color:red;"></mark><mark style="color:red;">first, based on the current size requirements. This helps control the overall asset size!  Otherwise, if the package significantly exceeds the size limit, compression during the download stage may fail, leading to rework.</mark>

Related Reading: [#id-4.compress-the-work](https://doc.playturbo.com/playable-tools-content-editor/content-editor-download-and-apply#id-4.compress-the-work "mention")

**💡 File Compression Tools**

* Common software for compressing videos: Handbrake
* Popular website for compressing images: [Tinyjpg.com](http://tinyjpg.com/)

**💡 Image Optimization Tips**

* Pay attention to the actual export resolution. Always export images at their final display size (for example, 600 × 600 instead of 2000 × 2000).
* Use JPG instead of PNG where possible. JPG can significantly reduce file size while maintaining sufficient visual quality.
* Avoid exporting images at the “highest quality” setting. For example, in JPG format, Quality 100 vs. Quality 80 shows little to no visible difference to the human eye.
* Combine multiple small images into a single larger image before exporting.

**💡 Video Optimization Tips**

* Video settings:\
  Set the resolution to 720p or 1080p (do not use 2K or 4K).\
  Use a frame rate of 24fps or 30fps.\
  Encode the video in H.264 format.
* Split the video into multiple clips based on interaction nodes. This helps maintain higher visual clarity for each individual segment.

**💡 Project Optimization Suggestions**

* Review commonly used elements such as product logos, CTA buttons, instructional text, and guiding hand indicators. Avoid adding them repeatedly in every scene. Instead, add them once in the **Global Settings** layer so they can be reused across all scenes.
* For standard content and simple animations (such as guiding hand effects), it is recommended to use a **single image with animation** rather than image sequences or video, to further reduce file size.

<div align="left"><figure><img src="https://695199083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4PyzU9CRLR4XKbxmIEid%2Fuploads%2FxL90FMuvomW2znb5wJ1i%2Fimage.png?alt=media&#x26;token=5f215fc1-e661-49bc-9903-1557e3a050d9" alt="" width="560"><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.playturbo.com/playable-tools-content-editor/content-editor-user-guide/editing-page-module-intro/work-preview-area/package-size-estimation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.