Contractor‑Ready Creative Kit: Exact Folder Structure, Filenames & Specs to Deliver Screenshots, Preview Videos & Ads Without Rework

Give contractors one unambiguous place to save every deliverable. Use a top-level folder named with your app slug and version so assets link to a release (example: myapp_v1.2_creatives). Inside that, split by channel then by device/orientation. This avoids mixups (e.g., Android phone vs tablet) and makes automation scripts predictable.

Use this exact tree — copy it into briefs and shared drives. It keeps filenames deterministic so scripts, QA checklists and your Play/App Store upload process can reference exact paths.

Deterministic filenames let you script QA, automate metadata generation, and reduce human error during store uploads. Use a short, consistent pattern: [appslug]_[target]_[device]_[size]_[variant].[ext]. Example: myapp_ios_6.5_1284x2778_en-US_01@3x.png.

Keep locale and variant at the end so localized folders can reuse the same naming pattern. For videos put duration and fps in the name: myapp_ios_preview_6.5_30s_30fps_stereo.mp4. That makes it immediate whether the file meets App Store Connect expectations and helps engineers wire CI checks.

App Store previews require strict settings: H.264 or HEVC as Apple documents, progressive scan, stereo audio (even if silent), 30 fps recommendation for many device targets, and exact device pixel dimensions. Export presets should produce files that App Store Connect accepts without re-encoding. Keep a small set of final exports named to match device targets (6.5, 5.5, iPad landscape, Vision Pro 2D).

Google Play is more flexible for screenshots and promo videos, but maintain a minimum resolution and aspect ratio rules: for screenshots provide at least two images and produce phone (1080×1920) and tablet variants. For ads, standardize on 1080px shortest side for feed creatives and 1080×1920 for Stories/Reels. Meta recommends MP4 or MOV for video, JPG/PNG for images and keeps file sizes under 30 MB for images and up to several GB for video; still, optimize to 4 GB or less for ad upload stability.

Make a one‑page brief that answers the three questions a contractor needs: Who (audience), What (assets & variants), and Why (goal + KPI). Attach the folder tree and give explicit acceptance criteria (see next section). Keep it short — contractors should be able to start work from the brief alone.

Include references (examples/), tone-of-voice for captions, required on-screen copy, and a link to the exact export preset file or the codec/dimension checklist. Provide a “do not change” list for elements like logos, legal text, and primary CTA color to avoid late rounds of reviews.

Even with correct filenames and presets you'll save time by shipping only files that pass automated and manual checks. Provide contractors a short checklist that is executed before upload: verify resolution/ratio, codec/fps, audio channel, filename pattern, and a visual QA for legibility and cropping at small sizes.

Include a machine-check script example (one‑line or CI job) that validates file names and image/video dimensions. When a file fails, contractors must include a short note explaining why and what they changed; that keeps accountability high and prevents repeated mistakes.