Yannick
App Store creative assets · 2026
An approved asset is not yet a published placement.
Keep design, file validation, asset review, placement assignment, and live verification as distinct steps in your release handoff.
Prepare
Export a named, validated set with a clear source design.
Review
Track the asset's approval independently from its use.
Verify
Check the correct placement, language, and live page.
Asset Library brings creative images, screenshots, and previews into a reusable App Store Connect collection. The operational risk is confusing the file, its review state, and the placement where it appears. This guide shows a practical handoff that keeps those identities separate, so a designer's latest export does not silently become the wrong campaign's artwork.
Quick answer
Upload files to Asset Library, submit them for review, and assign compatible approved artwork to the intended placement. Standalone creative review can happen without a new app version. Publishing a placement is a separate action: use Preview, confirm the localization, and verify the resulting page.
What Asset Library does and who can use it
Apple uses Asset Library to manage screenshots, app previews, and creative assets across placements and sizes. Eligible roles include Account Holder, Admin, App Manager, and Marketing. A standalone creative submission can be reviewed against the latest app version before you choose where to use the file.
Keep three states in your release checklist: exported locally, approved by Apple, and published in a placement. A filename called 'final' establishes none of them. That distinction matters when a campaign is scheduled, a localization changes, or a CPP reuses an earlier asset.
Bring your screenshots and brand materials into the graphics studio to develop the artwork, then validate and publish the final assets in App Store Connect.
Prepare an export manifest before upload
Use names that identify the app, placement, audience, locale, and revision. A pattern such as routeapp_search_cycling_en-US_r03.png makes a file easier to reconcile with a brief. This is our recommended naming convention, not a required Apple format. Store the editable source beside the manifest, not in an email attachment that gets lost.
Validate the downloaded file: image dimensions, file extension, actual encoding, lack of transparency, and visible content. Check video frame rate, duration, playback, and poster frame where relevant. An editor preview is not evidence that the export meets upload requirements.
| Field | Example | What it prevents |
|---|---|---|
| Placement / audience | Search / cycling | A default header used for a narrow campaign |
| Locale / revision | en-US / r03 | A translated or obsolete file uploaded by mistake |
| Source / export | Editable design + final PNG | Manual edits applied only to the exported copy |
| Approval / assignment | Pending / not assigned | Treating upload as proof of publication |
| Owner / live check | Named reviewer + dated check | An unverified release with no accountable handoff |
Upload and submit a standalone creative asset
In App Store Connect, select the app, open Asset Library, use the add button, choose Upload Creative Assets, select the files, and upload. Inspect each item and submit it for review when ready. The library's compatibility information helps identify where a file can be used.
Treat approval as a reusable asset state rather than a page launch. Keep the approved file tied to its source revision. If review fails, correct the issue in the source and produce a new clearly identified candidate instead of changing unrelated artwork to chase an unexplained rejection.
Assign the header or search placement and preview it
On the app version page, find Product Page Information and its Header and Search Results controls. Add a new asset or browse compatible library assets, save, and use Preview. Apple provides device, orientation, and language previews; inspect the actual combination you intend to release.
For a version already live, Apple documents choosing approved assets through Browse Assets and publishing the update without a new app version. For a new version, follow its review and release workflow. Universal assets can share the header placement with search; other files need their own search assignment. Follow the current App Store Connect controls rather than treating every asset as universally reusable.
Reuse assets without losing the campaign context
A compatible approved file can save production work, but compatibility is not the same as relevance. Before reusing an image on a CPP, compare the audience, promise, and supporting screenshots. A cycling result and a walking route may share a brand system without deserving the same artwork.
Keep one revision log for the creative source and another for placement assignments. If you remove a file from a placement, record that action separately from archiving or deleting a library item. Do not assume a cleanup action has the same effect across every page that reused the asset.
Troubleshoot the handoff in the right order
If upload fails, inspect the file before redesigning it: exact dimensions, supported format, alpha, and video settings. If the file uploads but cannot be assigned, inspect approval and placement compatibility. If the placement saves but looks wrong, inspect the chosen locale, crop, and poster frame. These are different failures with different remedies.
Finally, inspect the live page after the relevant approval and publication step. Record the device, locale, date, and asset revision you checked. The workflow is complete only when the intended artwork is in the intended placement—not when someone clicks Export in the studio.
- File valid? Compare the downloaded artifact with Apple's specification.
- Asset approved? Check its current review state in the library.
- Placement correct? Check page, audience, locale, and compatibility.
- Live verified? Inspect the released experience and record the result.
Continue the workflow
Primary sources and verification notes
Platform requirements and software capabilities change. These sources were reviewed for this guide on October 7, 2026; open the current source again before publishing assets, enabling production access, or standardizing a team workflow.
- Apple: manage your App Store assets: Asset Library, review, placement assignment, previews, and updates to live pages.
- Apple: creative asset specifications: The current image and video upload requirements. Check them again before final export.
- Apple: custom product pages: Audience-specific pages, keyword intent, unique URLs, and deep links.
Asset Library Guide FAQ
Can I get creative assets reviewed without a new app version?
Yes. Apple documents standalone creative submissions through Asset Library, reviewed against the latest app version. Assigning and publishing an asset is a separate step.
Does removing artwork from a placement delete the file?
Apple distinguishes removal from a placement from deletion or archiving in Asset Library. Check the current item state and reuse before performing a library cleanup.
Does AppLaunchFlow publish these assets automatically?
This guide uses AppLaunchFlow for creative preparation and exports. Use App Store Connect to review and assign the artwork; do not infer publishing or CPP configuration from the studio's export action.
