Fastlane-compatible ZIPs ready for deliver.

Folder structure Fastlane expects

Set output.format to fastlane_zip and appscreenshotapi adds an archive.url to the render response, packaged by locale with deterministic filenames. The output is built for teams that already run Fastlane deliver as part of a release branch or CI workflow.

Typical paths look like en-US/iphone_6_9/01_home.png and de-DE/iphone_6_9/02_paywall.png, which keeps screenshots stable in diffs and easy to inspect before upload.

{
  "canvas": { "preset": "appstore.iphone_6_9" },
  "slides": [
    {
      "headline": { "lines": ["Track every habit"] },
      "screenshot": { "url": "https://acme.app/shots/home.png" }
    }
  ],
  "output": {
    "locales": ["en-US", "de-DE"],
    "format": "fastlane_zip"
  }
}

No glue script for packaging

The render handles design, frames, captions, locale folders, file ordering, and ZIP creation in one request. Your lane downloads the archive, extracts it, and points deliver at the screenshots directory, or skips the ZIP and lets the CLI arrange the CDN images into the same folders.

Store upload actions should still remain an explicit human approval step in CI, especially for production App Store Connect publishing.

API details

Format output.format = fastlane_zip

Render POST /v1/renders with slides, canvases, locales, and captures

Download archive.url in the render response (also via GET /v1/renders/{id})

Use it in a release pipeline

Render the set from CI with POST /v1/renders, check the compliance lint report, then download the finished images for review before App Store Connect or Google Play upload.

Start with the API docs or request an API key.