Asset Naming Generator
Generate consistent, sortable file names for screenshot and icon sets across locales and devices.
Generated output
SCREENSHOT NAMING CONVENTION Pattern: app_locale_device_position.png — zero-padded position keeps files sorted in store-upload order. [App name (short, no spaces)]_[Locale code]_[Device / size key]_01.png [App name (short, no spaces)]_[Locale code]_[Device / size key]_02.png [App name (short, no spaces)]_[Locale code]_[Device / size key]_03.png [App name (short, no spaces)]_[Locale code]_[Device / size key]_04.png [App name (short, no spaces)]_[Locale code]_[Device / size key]_05.png With version tracking (recommended when you archive old sets): [App name (short, no spaces)]_v[Version number]_[Locale code]_[Device / size key]_01.png Folder structure: store-assets/screenshots/[Version number]/[Locale code]/[Device / size key]/ Rules: — lowercase everything, hyphens inside keys, underscores between segments — locale uses store codes ([Locale code]), device keys stay consistent (iphone-69, iphone-65, ipad-13) — never reuse a number for different content across locales: 01 is the same message everywhere
A localized store presence multiplies fast: ten screenshots, two device sizes, and fifteen locales is already three hundred files, before icons, feature graphics, and version history. Without a naming convention, that folder becomes “final_v2_FR_new (1).png” chaos — the wrong-locale upload waiting to happen. This generator produces a systematic scheme that encodes app, locale, device, position, and version into every file name.
Pick the fields your pipeline needs and the tool assembles names like appalize_ios_en-US_iphone-69_ss-01_v3.png — machine-parseable for upload scripts and fastlane’s deliver, human-scannable in a file browser, and sorted correctly by every operating system out of the box.
How to generate your naming convention
- 1
Enter your app identifier — a short lowercase slug that prefixes every asset.
- 2
Choose the components to encode: platform, locale code, device class, asset type, position, and version.
- 3
Set your locale list and device sizes, and the tool expands the full matrix of file names for your set.
- 4
Copy the generated names into your export pipeline, or use them as the renaming map for existing files.
- 5
Adopt the scheme in your design tool’s export settings so future assets are born correctly named.
What a good asset naming convention encodes
Five fields cover nearly every store pipeline: platform (ios/android), locale as a BCP 47 code (en-US, de-DE, pt-BR — the same codes App Store Connect uses, which prevents mapping bugs), device class (iphone-69, ipad-13, phone, tablet7), asset type with position (ss-01 through ss-10, icon, feature-graphic), and a version or date stamp for tracking creative iterations. Zero-pad every number: ss-01 not ss-1, or alphabetical sorting will file position 10 between 1 and 2 in every file browser and upload script you ever use.
Just as important is what to leave out: spaces (they break shell scripts and URLs), uppercase (case-sensitive and case-insensitive filesystems disagree about them), and meaning-free words like “final” or “new” that go stale the moment a revision lands. Separate fields with underscores and keep values internally hyphenated — en-US, iphone-69 — so a script can split on underscore and get clean fields every time.
Why naming discipline pays off at upload time
Store upload automation is built on parseable names. fastlane’s deliver, for instance, expects screenshots organized in locale-named directories and uploads them in filename order — which means your naming convention is your screenshot order. A scheme with encoded locale and zero-padded position lets one script route three hundred files to the right storefront slots; a folder of ad-hoc names means an afternoon of manual drag-and-drop in App Store Connect per release, with the wrong-locale mistakes that fatigue produces.
The convention also functions as version control for creative. When conversion dips after a screenshot refresh, ss-03 files stamped v2 and v3 let you diff exactly what changed and roll back the specific frame; “Screenshot final (2).png” lets you guess. Teams that A/B test store creative aggressively treat the version field as mandatory for this reason — creative experiments are only as auditable as the file names behind them.
Frequently asked questions
What is a good naming convention for app store screenshots?
Encode platform, locale, device, position, and version in a fixed order with underscores between fields: for example appalize_ios_en-US_iphone-69_ss-01_v3.png. Use lowercase, hyphens within field values, and zero-padded numbers so files sort and parse correctly everywhere.
Do file names affect ASO or store rankings?
No — stores discard file names at upload, and users never see them. The payoff is operational: correct-locale uploads, script-friendly automation, and auditable creative versions. The ranking effect is indirect, through the mistakes a good scheme prevents.
Why zero-pad screenshot numbers?
Because alphabetical sorting puts ss-10 between ss-1 and ss-2, scrambling your screenshot order in every file browser and — worse — in upload tools like fastlane that process files in name order. ss-01 through ss-10 sorts identically alphabetically and numerically.
Which locale codes should I use in file names?
The same BCP 47 codes App Store Connect uses: en-US, de-DE, pt-BR, zh-Hans, and so on. Matching the store’s own codes means your upload scripts can map files to storefronts without a translation table, eliminating a whole class of wrong-locale bugs.
Does this work with fastlane deliver?
Yes — deliver expects screenshots grouped in locale-named directories and uploads them in filename order. Generate names with the locale field, sort files into matching folders, and the zero-padded position field gives deliver the exact screenshot order you planned.
Should icons and feature graphics follow the same scheme?
Yes — swap the asset-type field: icon-1024, icon-512, feature-graphic in place of ss-01. One scheme across every asset type means one parser in your scripts and one convention for the team to remember.
Skip the file management entirely
Appalize’s Screenshot Studio generates, localizes, and organizes your screenshot sets internally — then uploads them to the right App Store Connect locale slots directly, no folder wrangling required.
Related free tools
App Store Screenshot Size Calculator
Look up every required screenshot resolution for the App Store and Google Play in 2026.
App Icon Size Reference
Every iOS and Android icon dimension in one table — store, launcher, and adaptive specs.
Screenshot Order Planner
Plan the sequence of your store screenshots so the first three do the selling.
App Icon Resizer
Upload one 1024×1024 icon and download every required iOS and Android size instantly.