Bring your fastlane metadata folder.Keep the format, gain an undo.
Your listing already lives in fastlane's metadata folder: one folder per locale, one text file per field, checked into git. MetaRun imports that exact layout in a single previewed change, shows you the per-locale diff before anything writes, and exports the same folder back whenever you want. It is fastlane deliver's upload, with the review step deliver never had.
Parsed 9 locales. 23 fields differ from the live listing; unchanged fields stage nothing. Review the diff and confirm.
- 01
Point at the folder you already have
Pick your fastlane/metadata directory: name.txt, subtitle.txt, description.txt, keywords.txt, release_notes.txt, promotional_text.txt, and the URL files, one folder per locale. Parsing happens in your browser; only the listing text is sent.
- 02
Diff against the live listing
The import previews as one change set: every field in every locale diffed against what is actually on the App Store. Fields that already match stage nothing, so re-importing is always safe. Locked surfaces, unknown locales, and over-limit values are skipped with named warnings instead of failing the import.
- 03
Confirm once, applied via the official API
One confirm applies the whole set through the App Store Connect API: app-level fields to the listing, version fields to your editable draft. deliver uploads blind; here nothing writes until you have seen the exact before and after, and the applied change lands in a recorded history.
- 04
Export back out anytime
One click regenerates the identical metadata folder layout from the live listing: drop it in your repo, hand it to a translator, or feed it to any fastlane pipeline. Works from the workspace, from MILO, or from your IDE over MCP.
deliver uploads. It never shows you what changed.
fastlane deliver made metadata-as-text-files the standard, and the folder format is genuinely good: reviewable in pull requests, translatable by agencies, versioned in git. What deliver never had is a safety layer. It pushes whatever is in the files over whatever is live, with no diff, no confirmation, and no way back; a stale checkout or a bad merge becomes your store listing.
MetaRun keeps the format and replaces the upload. The same folder imports as a staged change with field-level before/after per locale, applies only on your confirm, and is recorded in a change history. Unchanged fields are skipped automatically, so importing is idempotent: run it after every translation round without fear.
Your existing pipeline keeps working
Because the interchange format is unchanged, everything that produces or consumes fastlane metadata folders still fits: Crowdin and Lokalise integrations that write per-locale files, translation agencies that return an edited folder, CI scripts that assemble release notes. The folder they emit is the folder MetaRun imports, and the review of their work is the import diff itself.
Export closes the loop. The current listing regenerates as the exact folder layout, so you can keep metadata in the repo, commit the store's real state after edits made in MetaRun or by MILO, and never depend on MetaRun to get your own data back. No lock-in is a feature, not a promise.
The rules Apple enforces, surfaced before you write
Apple locks listing fields by state: name, subtitle, description, and keywords need a version in an editable state, while promotional text updates instantly. An import respects those rules up front: locked fields are skipped with the reason and the fix, not discovered as a rejection. Character limits (30 for name and subtitle, 100 for keywords, 170 for promotional text, 4,000 for descriptions) are checked per field, and an over-limit value skips that field alone, never the import.
Two guarantees hold everywhere: an import never clears a field, because an empty or missing file means leave it alone; and nothing reaches the App Store without the previewed diff being confirmed. Both hold identically whether the import runs from the workspace, through MILO, or from an IDE over the MCP server.
- deliver files per locale understood
- 9
- Previewed change for the whole folder
- 1
- Fields ever cleared by an import
- 0
- Import and export, same format
- 2-way
Frequently asked questions
Can I import my fastlane metadata folder into MetaRun?
Yes. Pick your fastlane/metadata directory in the Listing workspace and MetaRun parses it in your browser, diffs every field in every locale against the live listing, and stages one previewed change you confirm before anything is written.
Is this an alternative to fastlane deliver?
For metadata, yes: it reads and writes deliver's exact folder format, but every upload becomes a previewed, confirmable, recorded change instead of a blind push. Your git-based metadata workflow keeps working; it just gains a diff and an undo trail.
Which fastlane metadata files are supported?
Per locale: name.txt, subtitle.txt, description.txt, keywords.txt, release_notes.txt, promotional_text.txt, support_url.txt, marketing_url.txt, and privacy_url.txt. Non-localized files like copyright and category files are recognized and reported, and managed through their own MetaRun tools instead.
What happens to locales or fields that cannot be imported?
They are skipped with a named warning: locked surfaces (a live app with no editable version), locale codes Apple does not support, values over Apple's character limits, and empty files. The rest of the import proceeds; one bad file never fails the folder.
Can an import delete or clear parts of my listing?
No. Absent files and empty files mean leave the field alone, unchanged fields stage nothing, and everything that would change is shown as a before/after diff you confirm first. Applied imports are recorded in the change history with every previous value.
Can I export my listing back to the fastlane format?
Yes, one click produces the exact metadata folder layout from the current listing, as a zip or as structured data over the MCP server. Keep it in your repo, send it to translators, or leave with it: your listing is never locked in.
Does this work from my IDE or through MILO?
Both. The import and export are MetaRun registry tools, so MILO can run them in chat or voice and any MCP client (Claude Code, Cursor) can call them from your editor: an agent can read the folder from your repo and stage the import, with the same confirm gate protecting the store.
Related capabilities
Capability file 06
Metadata editor
Bulk-edit every locale of your listing with preview, apply, and one-tap revert.
Open fileCapability file 04
Listing translation
AI-translate your name, subtitle, description, and keywords into 40 locales.
Open fileCapability file 07
MCP server
Drive your entire App Store from Claude Code or any MCP-capable IDE.
Open fileMILO standing by
14-day free trial. No credit card. Your keys stay encrypted.