The Build‑Ready Creative Kit: One Folder Every Founder Must Deliver for Screenshots, Preview Videos & Ads

Treat creative assets like code: one canonical folder, clear filenames, and machine-friendly exports. That prevents last-minute back-and-forths with engineers and avoids re-encoding errors in App Store Connect and Play Console that routinely delay releases.

A good kit contains three families: store screenshots (per device/locale), store preview videos (Apple App Preview + Play promo), and ad-ready variants (feed, tall, and story sizes). Each family should include a poster/frame, captions (text), and layered source files so fixes don’t require a full re-export.

Below is the minimum deliverable set for a mobile app launch. Keep the manifest at /manifest.json (example fields below) and name files exactly—engineers and automation expect consistent patterns.

Files to include per locale (en-US, fr-FR, etc.): screenshots, preview videos, poster frames, and ad variants. Follow the device dimension requirements for App Store (Apple) and Play Console (Google) when selecting sizes; upload errors are commonly caused by wrong pixel dimensions or codecs.

Commit preset exports so designers and engineers always produce identical outputs. Use these exact encoder settings when exporting JPG/PNG from Figma or Photoshop and MP4 from Premiere/FFmpeg. That removes subtle encoding differences that break App Store uploads.

Save these as named presets in your tooling (Photoshop Export Preset, Figma export guide, or an ffmpeg script). Include sample shell commands in /scripts/export-presets.sh so CI can regenerate assets when needed.

Ad platforms (Meta/Facebook, Instagram) display creative in multiple placements; upload flexible variants to let the ad system optimize placement. Create three core crops from your hero screenshot or scene: square (1:1), tall feed (4:5), and vertical (9:16) for stories/reels.

Name ad files with the campaign-friendly pattern so marketers can script uploads: ads/{campaignCode}_hero_1x1_v1.jpg, ads/{campaignCode}_hero_4x5_v1.jpg, ads/{campaignCode}_hero_9x16_v1.mp4. Include a captions.csv with ad primary text and call-to-action so a simple script can create ad sets.

Run this checklist as part of your release train. It’s short but catches the common blocking issues: wrong pixel sizes, missing stereo audio, incorrect filename casing, and missing locales. Automate as many checks as you can—AppWispr recommends a small preflight script that validates manifest.json and checks file dimension metadata.

If anything fails, regenerate from source layers and re-run export-presets.sh. Don’t re-encode from exported JPEGs; always keep original layered files for fixes.