Frequently asked questions

What’s the difference between Studio screenshots and the Screenshots section?

They sit at two ends of the same pipeline. Studio is where screenshots are made: you upload raw screenshots captured on your device, and Studio places them inside device frames, adds localized captions and backgrounds, and exports polished marketing images. The Screenshots section of a project holds the final, store-ready images — whether they came from a Studio export or were designed elsewhere — organized per device and locale, ready to push to App Store Connect.

How do I name files for bulk upload?

One fastlane-style grammar works everywhere — Studio and the Screenshots section read the same filenames:

locale_device_order.png — for example en-US_01.png, en-US_6.9_02.png, de-DE_iphone-6.9_01.png

• locale — the full store code (en-US, de-DE, zh-Hans…). Case is normalized (EN-us works), and bare short codes resolve to their store locale (gu → gu-IN, pt → pt-BR, en → en-US).
• device — optional; a device name (iphone-6.9, ipad-13) or just the size (6.9, 13).
• order — a 1-based number (01, 02…).

Parts are separated by underscores; locales and device names keep their hyphens.

How do I bulk-upload device screenshots in Studio?

In Studio, hit Bulk upload in the toolbar and drop raw app screenshots for every language at once. Here locale and order are required: de-DE_02.png fills the second device-bearing screen of your design for German (text-only screens are skipped in the count). The device part acts as a display size: add it (de-DE_6.9_02.png) to give the 6.9″ output its own screenshot, or omit it to reuse one image across every size. Studio previews exactly what will land where before importing, so a mis-named file is easy to spot.

How do I bulk-upload final screenshots in the Screenshots section?

Hit Bulk upload (or drop files anywhere on the panel) with the same naming. Here every part is optional: a file without a locale lands in your project’s primary language, a missing device is detected from pixel dimensions (1320×2868 → iPhone 6.9″, 2064×2752 → iPad 13″…), and files without an order sort by name. Order fixes the display order within that device and locale. A plain hero.png still works — primary language, device auto-detected.

Upload folder takes a whole directory at once and also understands fastlane’s layout: a locale subfolder (en-US/01.png, de-DE/01.png) sets each file’s locale, so an existing fastlane screenshots directory imports as-is. Either way, a review popup shows exactly what will land where — grouped by device and locale, reorderable, with unmatched files assignable by hand — before anything uploads.

How do screenshots get to App Store Connect?

From the Screenshots section, hit Push to App Store Connect. Locales sync one at a time with live progress, and each sync replaces what’s on App Store Connect for the locales it touches — re-syncing never stacks duplicates. Locales you don’t sync are left untouched.

Custom product pages follow the same staging flow: Studio always exports into the project’s Screenshots section first, and Push project screenshots on the page sends them to App Store Connect (replacing that page’s sets). Nothing you do in Studio touches the store directly.

Why did a sync tell me Apple is rate-limiting?

Apple caps how many App Store Connect API requests each key can make per hour. Heavy sessions — translating dozens of locales, syncing hundreds of screenshots — can use the hour’s budget. When that happens Storeline stops early and says so, because continuing would only burn more quota. It’s Apple’s limit on your key, not a Storeline outage; it resets on the hour, so retry a little later.

Can I undo a push?

Yes — every push is recorded in the project’s History with a snapshot of what it sent: your source copy, each language’s copy, the screenshots and app previews, and for store-side pushes (prices, contact details, product listings, custom product page copy, in-app events) the values themselves. Restore puts them back into your draft — one field, one language, every language, a screenshot set, or a whole recorded push — and nothing returns to the store until you push again. So an edit is always worth trying: the version before it is still there.

Entries can be annotated (“before the ASO experiment”), which also keeps them when older screenshot snapshots are pruned, and the whole history exports as JSON.

How does keyword research work?

It mines your competitors’ public App Store listings per storefront and has AI consolidate the strongest terms into a localized title, subtitle, and keyword field. Read the full explainer.

How are my API keys protected?

Encrypted with AES-256-GCM before storage, decryptable only with a master key held separately, and scoped strictly to your account. Clearing a key in Settings permanently deletes it from our servers. Read the security page.

Still stuck?

Email support@storeline.dev — we read everything.