How-To Guide 17
How to export an App Store localization delivery pack.
The delivery step should not be where stills, translations, and preview videos drift apart. This workflow turns the approved launch system into one organized export pass so each locale leaves the project with the right still-image files, video variants, and reusable source intact.
What You'll Build
One release pack containing grouped still-image exports, localized variants, and preview-video clips for each market.
What You'll Use
Export grouping, locale naming, device branches, motion variants, and reusable project cleanup.
Screenshot Plan
Capture 1 grouped locale pack, 1 export settings view, 1 preview-video grouping, 1 named output structure, 1 completed render, and 1 final reviewed delivery folder.
Step 01
Gather the approved stills, captions, and video branches in one project.
Do not start exporting from a half-merged state. Pull together the cleaned localized captions, mockup variants, and preview-video branches so the project reflects the real launch pack before any files leave the canvas.
Screenshot To Add
The final release project showing grouped locale stills and motion variants together before export.
Step 02
Open the export controls and separate deliverables by market, device, and format.
Use the structure from the batch export App Store screenshots and preview videos feature page so every output leaves the project with a clear device and locale label. This is where release ops discipline matters most.
Screenshot To Add
Export settings open with stills, locales, and preview-video clips grouped into clear delivery buckets.
Step 03
Check that every locale has the right still-image and video pairings.
Review the output map carefully so the Japanese stills do not accidentally leave with the German preview clip or the wrong device branch. Clean grouping is the difference between a reusable delivery system and a launch-night scramble.
Screenshot To Add
A delivery overview where still-image and video variants are checked for each market before render begins.
Step 04
Render the full pack without flattening the reusable source project.
Let the project output the files, but keep the underlying template, mockup branches, and motion scenes editable for the next version. Export should create a delivery artifact, not destroy the system that made it possible.
Screenshot To Add
The full localization pack rendering while the editable source project stays intact in the background.
Step 05
Review the shipped files against the approved locale sequence.
Before handoff, compare the exported pack to the last approved mockup and caption review. This is the final QA checkpoint that catches missing locales, wrong file groupings, or preview-video variants that did not render with the latest text.
Screenshot To Add
One final review pass comparing exported locale files against the approved source scenes.
Step 06
Archive the release pack and keep the master launch system ready for the next update.
Finish by saving the delivered files and leaving the reusable project alive for the next release cycle. The pack is done, but the master template, mockup family, caption system, and motion branches should still be ready for the next version bump.
Screenshot To Add
The completed localization delivery pack archived beside the reusable Bezel Studio project that remains ready for the next launch.