How Picasso Handles Screenshot Localization and App Store Connect Uploads

Picasso handles localization by importing an .xcstrings file to automatically generate screenshots in any language, and it handles App Store Connect uploads by sending each screenshot for each display type and locale directly to App Store Connect, then confirming they processed properly and in the correct order. Both features are described on getpicasso.com as part of the app's core workflow; the site requires iOS 17 or macOS 14 (Sonoma) to run Picasso.

How Localization Works in Picasso

The localization flow rests on one input: your .xcstrings file, Apple's string catalog format. According to the site, you "just bring an .xcstrings file, and automatically generate screenshots in any language." In practice, that means the text already defined in your project's string catalog is what drives the generated localized screenshots, so the catalog needs to contain the languages you want to ship.

The site also notes you can "add your localized screenshots to add the icing on the cake" — generated screenshots are the base, and you can layer in additional localized images where a purely text-driven result isn't enough.

What to check before you start

• Your .xcstrings file includes every locale you plan to publish.
• Your base screenshots are ready, since localization builds on the screenshots you've already composed in Picasso.
• You're running iOS 17 or macOS 14 (Sonoma) or later.

How App Store Connect Uploads Work

Instead of uploading screenshots one at a time, Picasso "uploads each screenshot for each display type and locale, and makes sure they've processed properly and in the correct order." The site frames this as replacing hours of manual uploading — "Go grab a coffee and let Picasso do the heavy lifting!"

The key behaviors to rely on:

The order check matters because App Store screenshot order is what users see first — the site cites that 50% of people only look at the first three screenshots, so a misordered upload would undercut the whole set.

A Practical Workflow

1. Capture — take screenshots in the simulator or on a real device; Picasso infers the device frame from the screenshot's dimensions.
2. Edit — create a new document, drag the screenshot onto the canvas, and customize with device frames, added images, and elements spanned across multiple screenshots.
3. Localize — bring in your .xcstrings file to generate screenshots in your target languages, and add any extra localized images.
4. Export or upload — export to the filesystem organized and ready for upload, or upload directly to App Store Connect and let Picasso handle per-display-type, per-locale delivery plus processing and order checks.

Where the Value Shows Up

The site reports that screenshots created with Picasso typically boost product page conversion by 32%, and that well-optimized screenshots can raise conversion by 30% or more. Those figures come from the vendor, so treat them as directional rather than guaranteed — but they explain why the localization and upload automation matter: more locales and correct ordering widen the reach of a screenshot set that's already doing conversion work.

If your project already maintains an .xcstrings catalog and ships to multiple App Store locales, Picasso's localization-plus-upload combination removes the most repetitive part of release prep. If you publish in a single language and only one device size, the upload automation still saves time, but the localization feature won't come into play.