App Store Multi-Language Metadata and Screenshot Batch Management (with AI Translation) Tutorial

App Store Multi-Language Copy and Screenshot Batch Management (with AI Translation) Tutorial

App Store listing information must be maintained per language — name, description, keywords, screenshots, and so on. Once the number of languages grows, filling each one in by hand turns into repetitive busywork. In its "Apps" feature, AppUploader provides three capabilities built specifically to solve this problem: batch screenshot upload, AI translation, and store information export/import folders.

Batch Upload Screenshots, Auto-Categorized by Device Size

Open an app's version detail page and go to the "Screenshot Management" tab:

1. Check the languages you want to upload screenshots for (multiple selection allowed).
2. Drag in or select screenshot images — there is no need to pre-sort them into folders by device size. The system automatically identifies and categorizes each image by its pixel dimensions into the corresponding device size, then uploads them in batch to all selected languages.
3. Images whose dimensions don't match any App Store device are skipped automatically and won't interrupt the overall upload process.
4. After uploading screenshots for one language, use "Copy screenshots to other languages" to copy that entire set to other languages in one go. You can optionally clear the existing screenshots of the same type under the target languages first, to avoid duplicating old and new.

Preview videos support similar per-device/per-language management. After upload, Apple transcodes them asynchronously and the status later becomes "Completed". You can set the poster frame time point; if left blank, Apple automatically picks the middle frame.

Use AI Translation to Generate Multi-Language Copy at Once

Under the "Metadata Editing" tab, first select a language you have already filled in as the source language, then click "Translate to other languages":

• Description, keywords, what's new, and promotional text are translated automatically and written into the other languages you selected.
• Name and subtitle do not participate in translation — they are app-level shared fields, so all languages share the same value; changes take effect only with the next version review.
• Promotional text is special: it can take effect at any time without review, making it suitable for quick adjustments to marketing copy.

Each field is annotated with whether it is required by App Store, so you won't miss required content after translation and fail the review submission.

Export to a Folder for Offline Editing, Then Batch Import Back

If you prefer editing copy in bulk locally with a text editor or version control tool (such as Git), you can export a version's store information into a folder structure:

1. On the version detail page, click "Export to folder" and enter the export path (leave it blank to use the default directory). You can optionally export screenshots and preview videos as well (large and time-consuming — check as needed).
2. Exported directory structure: the root config.yaml stores categories/copyright/age rating, review_information.yaml stores review information separately, metadata/<language>/ holds one .txt file per field, and screenshots/videos go in the screenshots/ and previews/ directories respectively.
3. After editing, click "Import from folder". Import is a partial update: only the parts actually present in the folder are applied. For example, if the folder contains only review_information.yaml, only the review information is updated; empty files are skipped and won't wipe out existing content on Apple; when screenshots/ or previews/ directories exist, the screenshots or videos for the corresponding language/size are replaced entirely.
4. After the import completes, a summary is displayed: the number of updated, skipped, and failed items, plus detailed results for each item, making it easy to verify.

This export/import mechanism is particularly well suited to multi-person collaboration on reviewing copy, or to putting store information under version control history.