Automate App Store Screenshots with the Genshot CLI and API

CLI quick start

Install the published client, authenticate once, and generate from local screenshots. The command prints the Generation ID before it waits so a script or agent can retain it.

npm install --global @genshot/cli@latest
genshot login
genshot generate --screenshot ./home.png ./details.png \
  --target-store app_store --count 4 \
  --prompt "Clear productivity story; preserve the real UI"

Plan before spending credits

The plan workflow researches an optional public product URL, drafts distinct campaign angles, and returns an editable Creative Brief without using credits. Approval freezes the brief and starts paid generation, so treat approval as an explicit release gate.

genshot plan create --source-url https://apps.apple.com/app/id123 \
  --screenshot ./home.png ./details.png \
  --target-store app_store --count 4 \
  --prompt "For solo consultants who need a calm daily overview"
genshot plan show brief_123 --json
genshot plan edit brief_123 --file ./brief-content.json
genshot plan approve brief_123

Inspect and refine without losing traceability

Use the history commands to recover a Generation ID and inspect attempts, random seeds, models, and provider request identifiers. Refinement creates a replacement while retaining the immutable original.

genshot generations list
genshot generations inspect gen_123 --json
genshot refine gimg_123 --region 0.1,0.15,0.8,0.25 \
  --prompt "Shorten the headline" \
  --preserve "product UI" "brand colors" --accept

REST API example

Direct API requests use a gsk_ bearer key. This example starts from a public source URL. For local files, first use the documented upload-presign flow and send the resulting source image identifiers.

curl -X POST https://api.genshot.dev/api/v1/generations \
  -H "Authorization: Bearer gsk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "version": 2,
    "targetStore": "app_store",
    "targetImageType": "store_screenshot",
    "sourceUrl": "https://apps.apple.com/us/app/example/id123456789",
    "prompt": "Bold headlines, real UI, premium 3D product world",
    "imageCount": 4
  }'

A safe CI or agent workflow

1. Step 1

   Capture or collect source UI

   Use deterministic UI tests when possible. Remove private and unstable account information.

2. Step 2

   Create a plan

   Let the agent draft, but require a person to approve claims and credit-spending actions.

3. Step 3

   Generate and persist identifiers

   Store the generation manifest with the release candidate.

4. Step 4

   Validate files

   Check the App Store screenshot requirements, source UI fidelity, captions, and sequence.

5. Step 5

   Review before store publishing

   Use the explicit App Store Connect review and publish workflow; Genshot does not remove the need for product, privacy, and policy review.

How this differs from Fastlane snapshot and frameit

These workflows can complement each other. Fastlane can capture stable source UI; Genshot can use those files as creative inputs. Keep the boundary explicit so a generation tool is never mistaken for a UI-test system.