← BACK

Follow these general file preparation and optimization guidelines when getting ready to build your demo:

  • Keep in mind that there are different output file size limitations for demos made for different platforms.
  • Record and export video, music, and sound effect as separate files. See also the tips for video and audio recording and editing.
  • Don’t compress video assets and high-encoded videos when building a demo. All video assets in Studio are automatically spliced and compressed to RF 26 + 30 FPS for publishing.
  • Compress your static assets like images and fonts before importing them to Studio.
  • If you need to optimize your assets, consider using programs like ImageOptim for image compression and Handbrake for video compression.
  • Organize your files in a single location and name them to reflect the associated scenes and transitions in the storyboard. See also File Naming Conventions below.

Supported Asset Types
Type Format Comments
Video

MP4

MOV

Exported video files should be H.264 codec, 30 FPS, and have high resolution of 1920 x 1080.

See also Video Recording Tips.

Audio MP3

Mono channel and 96 kbps are recommended.

See also Audio Recording Tips.

Images

JPG

JPEG

PNG

  • Use JPG format for images that don’t need transparency.
  • Compress all images to the lowest resolution possible while still maintaining acceptable quality across different mobile devices.
  • Don’t use images larger than 540 x 960 or 960 x 540 pixels.
Fonts

OTF

TTF

Compress all font assets before importing them to Studio.

File Naming Conventions

To expedite the demo creation process, maintain consistent naming conventions for your assets to help you recognize them, for example, when you need to select them from menus in different panels.

  • Avoid using spaces or special characters. If needed, use hyphens or underscores in place of spaces.
  • Omit articles, prepositions, and other insignificant words.
  • Avoid using ALL CAPS. Use title case to help you distinguish between the words.
  • Use meaningful, easy-to-recognize names for asset files to reflect their contents and purpose in the demo, for example:
    • Splashscreen
    • Endcard
    • Background-Music
    • White-Close-Button
    • Green-Checkmark
    • Home-Run
    • Enemy-Turn
  • Avoid using acronyms and abbreviations. If you choose to use them, opt only for commonly known ones, for example, CTA for a “call to action” or SFX for “sound effects,” especially if you are preparing files for another person to use.
  • Avoid numbering files starting with 01 or a similar prefix. While it may help you sort the files initially, issues may arise if you need to add assets at a later time. In Studio, you can use the search field in the Assets panel to find the necessary files.
  • Don’t include asset types in file names, for example:
    • DO: Move1-Loop, Move1-Action, CTA-Button
    • DON’T: Move1-Loop-Video, Move1-Action-Sound, CTA-Button-Image
      Media asset types are indicated by icons in the Assets panel, labels in the UI, such as Play Video actions, and their file extensions.
  • Use the same file name for assets that are intended to be used in the same scene, for example:
    • DO: Move1-Action for both video and sound effect
    • DON’T: Move1-Action-Video and Move1-Action-Sound
      The file extensions will help you distinguish between Move1-Action.mp4 and Move1-Action.mp3.

Updated June 12, 2019