iOS & macOS App Store Publishing

iOS and macOS App Store publishing guide, with a phone, desktop display and upload illustration.

A finished app still needs a release process: a signed build, an accurate product page, screenshots, privacy information and a clear path through App Review. For an app that runs on iPhone, iPad and Mac, those details span several platforms and asset formats.

This walkthrough brings the process together with the Prototypes Lab publishing guide and companion toolkit. Use the article as a working overview, keep the 21-page PDF beside your release checklist, and use the scripts for the repetitive image, video and policy-template tasks.

Get the guide and toolkit

Guide: 21-page PDF, approximately 80 KB. Toolkit: ZIP archive, approximately 14 KB. The supplied handbook and toolkit were prepared on November 20, 2026. Check Apple’s linked requirements again before each release.

Jump to: Release workflow · Store assets · Toolkit commands · Privacy · Encryption · Mac distribution · Final checklist

Build a repeatable release workflow

Start a release folder containing the source revision, dependency versions, app facts, store copy, screenshots, preview movies, review instructions and archive location. That record makes the next update easier to reproduce. Keep signing credentials and real customer databases outside it.

  1. Confirm your account and app identity. Check the Apple Developer team, App Store Connect access, agreements and any required banking or tax setup. Record the bundle identifier, app name, platforms, version, build number and intended countries.
  2. Prepare the release in Xcode. Verify signing and capabilities, increment the build number and include the correct icons and resources. Test fresh installation, upgrades, database migrations, permission prompts, accessibility, offline behavior and purchases. Check Apple’s current toolchain requirements before archiving.
  3. Create or update the store record. Prepare the description, screenshots, support and privacy URLs, age rating, pricing, availability and review contact. Keep every feature claim consistent with the build you will submit.
  4. Archive and upload. Use the distribution destination for the target platform, then archive in Xcode and upload through Organizer’s App Store Connect workflow. Wait for processing and resolve validation or compliance requests.
  5. Test the uploaded build. Use TestFlight to check the actual release candidate. Supply reviewers with working credentials when needed, safe sample files and precise instructions for unusual workflows.
  6. Submit, review and release. Select the processed build, complete the version and perform the final submission to App Review. After approval, release using your selected option and verify the public listing and installation.

Upload, submission and release are separate milestones. A successful upload means Apple received the build; it does not mean the version has been submitted or made available to customers. The PDF expands each step and links to Apple’s App Store Connect workflow.

Prepare screenshots and previews for each platform

Capture the app’s real interface using representative sample data. Resizing should preserve the UI and its proportions. A resized Mac screenshot does not become an accurate iPhone screenshot, and a screenshot canvas is not necessarily a valid preview-video canvas.

DestinationScreenshot examplePreview example
iPhone, Dynamic Island medium display1206 × 2622, portrait886 × 1920, portrait
iPad, 13-inch display2064 × 2752, portrait1200 × 1600, portrait
Mac2560 × 1600, landscape (16:10)1920 × 1080, landscape (16:9)

These are selected supported examples, not a complete list of required slots. Match your app’s supported devices and orientation to App Store Connect’s Media Manager. Apple maintains the full screenshot specifications and app preview specifications.

App previews are optional. Apple’s specifications allow 15–30 seconds, a maximum file size of 500 MB and up to 30 frames per second. The toolkit exports H.264 MP4 with stereo AAC audio. Watch the complete export before uploading: readable text, useful pacing and clear sound matter as much as the file properties. Upload the movie file itself to App Store Connect; a YouTube link cannot replace it.

Use the PublishingToolkit

Unzip the download and keep its files together. The media scripts require macOS, Python 3, ImageMagick 7, FFmpeg and FFprobe. If Homebrew is already installed, install the missing tools with:

brew install imagemagick ffmpeg python

Open Terminal in the extracted PublishingToolkit folder. For example, if you extracted it in Downloads:

cd "$HOME/Downloads/PublishingToolkit"

Replace the sample input paths below with your own captures. The wrappers create separate output files and refuse to overwrite existing outputs.

Resize screenshots without stretching the interface

bash resize_app_screenshots.sh \
  "$HOME/Desktop/AppScreenshots/iPhone" \
  "$HOME/Desktop/AppAssets/iPhone" \
  1206 2622 fit white

bash resize_app_screenshots.sh \
  "$HOME/Desktop/AppScreenshots/Mac" \
  "$HOME/Desktop/AppAssets/Mac" \
  2560 1600 fit black

fit preserves the entire image and adds padding. fill crops to fill the canvas; inspect the edges before using it. The script accepts PNG, JPG and JPEG files, removes transparency and writes 8-bit RGB PNGs. It processes one directory at a time, without recursing into subfolders.

Choose the right video operation

Keep make_app_preview.sh beside app_preview.py. Use resize for a movie that is already 15–30 seconds long:

bash make_app_preview.sh resize \
  "$HOME/Desktop/preview.mp4" \
  "$HOME/Desktop/iphone-preview.mp4" \
  886 1920

For a longer recording, choose between preserving the full sequence at a faster speed and selecting a shorter excerpt:

# Fit the entire sequence into 29.8 seconds.
bash make_app_preview.sh speed \
  "$HOME/Desktop/long-demo.mp4" \
  "$HOME/Desktop/mac-preview.mp4" \
  1920 1080 --seconds 29.8

# Keep a 20-second excerpt, starting at 45 seconds.
bash make_app_preview.sh trim \
  "$HOME/Desktop/long-demo.mp4" \
  "$HOME/Desktop/excerpt.mp4" \
  1920 1080 --seconds 20 --start 45

Speed mode calculates the required speed factor from the source duration and adjusts audio tempo with the video. Trim mode keeps normal speed and discards the surrounding material. Append --mute to replace the audio with silence. The tool is intended for SDR footage; identified HDR input is rejected. A 29.8-second target leaves some margin below the 30-second limit.

Make privacy disclosures specific to the app

The supplied HTML is an unfinished template. Before generating a policy, inventory local files and databases, network requests, SDKs, analytics, support messages, cloud storage, backups, permissions, purchases and account deletion. Describe what the shipped app actually does.

Keep the public policy, App Privacy answers and applicable privacy manifests consistent. Apple’s App Privacy guidance includes data handled by integrated third parties. An offline-looking interface or an encrypted database alone does not establish that the app collects no data.

cp privacy-policy.example.json MyApp-privacy.json

# Replace every placeholder in MyApp-privacy.json first.
python3 generate_privacy_policy.py \
  MyApp-privacy.json MyApp_privacy_policy.html

open MyApp_privacy_policy.html

The generator checks required fields and date/email formatting, escapes inserted HTML and refuses to overwrite an existing policy. It cannot verify the truth of the answers. Review the generated page, then publish the finished policy at a public HTTPS URL and link it from the app and App Store Connect. A local development address is not accessible to App Review or customers.

Answer encryption questions for the released product

The toolkit’s Encryption_Answers.txt separates two SQLCipher scenarios:

  • Protecting the app’s own database: SQLCipher encrypts local application data at rest, without exposing a general database-encryption utility.
  • Encrypting user-selected databases: a utility such as SQLiteTools lets users encrypt or decrypt compatible databases using their own passwords or keys.

Both use encryption, but they describe different product capabilities. Use the matching worksheet, confirm the library version and data flows, and assess the app’s actual functionality and distribution territories. A library’s classification is not automatic approval for every app that embeds it. Follow Apple’s export-compliance process and any applicable documentation requirements.

Set ITSAppUsesNonExemptEncryption from the confirmed assessment: NO when the app has no encryption or all its encryption is exempt; YES when it uses non-exempt encryption. Do not select an answer simply to dismiss “Missing Compliance.” Apple documents the declaration in ITSAppUsesNonExemptEncryption. The worksheet supplies conditional descriptions, not a completed legal classification.

Keep Mac App Store and direct distribution separate

For the Mac App Store, test the signed, sandboxed release build with the entitlements it needs. Database tools deserve particular attention to file selection, read/write access, exports and persistent access across launches.

Direct distribution follows a different route involving Developer ID signing and notarization. It does not create an App Store listing or replace App Review. The PDF includes a separate notarization example; use Apple’s macOS distribution guidance for the route you choose.

Check the release before submitting

  • Correct team, bundle ID, platforms, version and unique build number.
  • Accepted Xcode/SDK combination; fresh installs and upgrades tested.
  • Accurate screenshots and readable, fully reviewed preview movies.
  • Working public support and privacy pages, with verified contact details.
  • Privacy labels, manifests, permissions and actual data flows aligned.
  • Encryption assessment, territories, documentation and Info.plist consistent.
  • Working review access, sample files and purchase/restore instructions.
  • Processed build selected, metadata complete and final review submission made.

After release, inspect the store page and install the public app on a clean device. Retain the archive, symbols, source revision, submitted assets and release decisions so the next update starts from a known record.

What is inside the download?

FilePurpose
README.txtSetup, examples and a reusable privacy-policy writing prompt.
resize_app_screenshots.shBatch resizing, padding/cropping and opaque PNG output.
make_app_preview.sh
app_preview.py
Resize, speed and trim modes with output-property checks.
Application_privacy_policy.htmlReusable HTML draft with explicit placeholders.
privacy-policy.example.jsonThe app-specific facts worksheet.
generate_privacy_policy.pyGenerate a new HTML policy from completed facts.
Encryption_Answers.txtSQLCipher descriptions and conditional compliance guidance.

The tools prepare assets and draft text; they do not log in to Apple or submit the app. The accompanying PDF contains the detailed size tables, release checklist and primary references.

Scroll to Top