How to Request Apple Expedited Review (2026 Guide)

Quick answer: To get an Apple expedited review, first submit your build for review in App Store Connect, then fill out Apple's Request an Expedited App Review form and pick the app and platform. Apple only expedites cases of genuine urgency, mainly a critical bug fix or a release tied to an event you are directly associated with. Put the bug's reproduction steps (or the event name, date and your connection to it) in the App Review Notes field. Approval of the request is not guaranteed and Apple publishes no expedited turnaround time.

Releasing an app is stressful. Deadlines, last-minute bug fixes and launch campaigns all hinge on the App Store review clock. Apple expedited review exists for real emergencies, but it is not a free pass. This guide covers who qualifies, exactly how to submit the request, a copy-paste template, what happens afterwards and how to avoid needing it at all. Every rule below links to Apple's own documentation.

What is Apple expedited review?

Apple expedited review is a request to move a submission that is already in the App Review queue to the front of the line. According to Apple, App Review aims to review at least 50% of submissions in under 24 hours and 90% in under 48 hours (Apple Developer). If you face "extenuating circumstances, such as fixing a critical bug or timing your release to coincide with an event," you can ask for faster handling. Apple then expedites the review "as allowed by availability and demand."

It speeds up when your app is reviewed, not whether it passes. The App Store Review Guidelines still apply in full.
Only submissions that have already been sent to App Review can be expedited.
Apple says expedite requests "should be reserved for matters of genuine urgency."

Who is eligible? (Apple's two accepted reasons)

Apple's documentation names two qualifying situations (App Review – Expedited reviews):

Reason	What Apple asks you to include
Critical bug fix in a live app (crash on launch, broken login or purchases, data loss, security flaw)	Steps to reproduce the bug on the current App Store version, added to the Notes field when you submit.
Event-related release (a conference, sports event, product launch or broadcast your app is directly tied to)	The event, its date and how your app is associated with it. Apple recommends scheduling the release ahead of time if you can.

Usually not eligible: marketing campaign dates you control, new non-critical features, "the client wants it today", or making up for submitting late. These do not match the extenuating circumstances Apple describes.

How to request an expedited review: step by step

Get the build review-ready. Add everything App Review needs in the App Review Information section: Notes, a demo account or demo mode for account-based features, and up-to-date contact details. Apple notes that incomplete information delays review (source).
Explain the urgency in the Notes field. For a bug: what breaks, who is affected, and the steps to reproduce on the current version. For an event: the event name, date and your association with it.
Submit for review in App Store Connect. Wait until the status shows Waiting for Review. You cannot expedite a build that has not been submitted. New to this? See how to submit an app to the Apple App Store.
Open the expedite form. Go to developer.apple.com/contact/app-store/?topic=expedite (or App Store Connect > Contact Us > App Review > Request Expedited Review) and sign in with the developer account that owns the app.
Select the app and platform (iOS, macOS, tvOS, visionOS…) and write a short, factual justification. The template below works well.
Submit and watch your email and App Store Connect. Apple's contact guidance says not to use "Reply to App Review" to ask for an expedite. Use the form.

What to write: expedited review request template

Keep it short, specific and verifiable. Reviewers act on concrete facts, not adjectives like "urgent" or "critical".

Critical bug fix template

App: [App name] (Apple ID [1234567890]), version [1.4.1] currently Waiting for Review.
Issue: Version [1.4.0] on the App Store [crashes on launch for users on iOS 18.x / blocks sign-in / fails to restore purchases].
Impact: [e.g. 38% of daily active users affected since 22 Oct, per our crash reporter].
Steps to reproduce on 1.4.0: 1) [..] 2) [..] 3) [..]
Fix: 1.4.1 only contains the fix for this issue (no new features). Reproduction steps are also in the Notes field.
Contact: [name, phone, email]

Event-related template

App: [App name], version [2.0] Waiting for Review.
Event: [Official app of XYZ Conference], taking place [12–14 Nov 2026] in [city].
Association: [We are the organiser / official partner; attendees use the app for tickets and schedule].
Need: The build must be live by [11 Nov]. Event details are in the Notes field.

What happens after you submit the request

App Review evaluates the request. If accepted, your submission is reviewed sooner "as allowed by availability and demand." Apple does not publish an expedited turnaround time.
Track progress on the App Review page in App Store Connect. Statuses move from Waiting for Review to In Review, then to approval or Unresolved Issues (review statuses).
If App Review only needs more information, reply to its message instead of resubmitting. Resubmitting starts a new review.
For a bug fix update where Apple finds other, unrelated issues, Apple may offer a Bug Fix Submission. You accept by replying to the message and fix the other issues in your next version (source).
Set the version release to Manual or Automatic beforehand, so an approved build goes live the way you planned.

Why expedite requests fail or get ignored

The reason is not urgent: marketing timing, new features or internal deadlines.
No submission in the queue: the build has not been submitted for review yet.
Vague justification: no reproduction steps, no event date, no impact numbers.
The build itself is not approvable. Expedite only gets you a faster answer. Apple says over 40% of unresolved issues relate to guideline 2.1 App Completeness: crashes, placeholder content, broken links, missing demo accounts (source). See our list of App Store rejection reasons and how to fix them.
The fix is bundled with lots of unrelated changes. A small, focused hotfix matches the "critical bug fix" story. A feature release does not.

Pre-request checklist

Build tested on devices running the latest OS. No crashes, broken links or placeholder text.
Demo account or demo mode provided. Contact details up to date.
Privacy policy and support URL work. App Privacy details match what the app collects.
Notes field explains the urgency (repro steps or event details).
You can answer App Review follow-up questions within minutes, not days.

Want to catch these before Apple does? Forvibe's App Store review simulation checks your code and store listing against Apple's guidelines before you hit submit. See also how to check an app before App Store submission.

Alternatives that reduce the need to expedite

Phased release: release iOS/macOS/tvOS updates to users with automatic updates over 7 days (1% → 2% → 5% → 10% → 20% → 50% → 100%), and pause for up to 30 days if something breaks (Apple).
Feature flags and server-side config let you turn off a broken feature without shipping a new binary.
Submit early and schedule the release ("Automatic, no earlier than" a date) for event launches, as Apple itself recommends.
Use TestFlight to catch crashes before production. External TestFlight builds also go through Beta App Review. See TestFlight.
On Google Play there is no equivalent public expedite form. Use managed publishing and staged rollouts in the Google Play Console.

How Forvibe helps you avoid emergency expedite requests

Forvibe centralises App Store and Google Play release work so you submit earlier and with fewer surprises:

Review simulation flags likely rejection reasons (missing restore button, account deletion, privacy gaps, placeholder screenshots) before upload.
Version management and TestFlight management keep builds, notes and testers in one place.
Store listing manager, Screenshot Studio and AI localization finish metadata fast, so listings are never the bottleneck.
An ASO agent and workflow automation take repetitive release chores off your plate.

See Forvibe plans → or read our app launch checklist for App Store and Play Store.

FAQ

How long does an Apple expedited review take?

Apple publishes no expedited turnaround. It says it expedites "as allowed by availability and demand." For context, standard review aims for 50% of submissions in under 24 hours and 90% in under 48 hours. Developers on forums report anywhere from under an hour to a day or more, so treat any number as anecdotal.

Where is the Apple expedited review form?

At developer.apple.com/contact/app-store/?topic=expedite, also reachable from App Store Connect > Contact Us > App Review > Request Expedited Review. Sign in with the account that owns the app.

Can I request an expedited review for a brand-new app?

Apple's rules don't limit expedites to updates. The same two reasons apply (critical bug or event). Note that Apple says apps with limited review history may need extra verification time (source).

Does expedited review increase my chance of approval?

No. It only changes the timing. Your app is held to the same App Review Guidelines.

How often can I request an expedited review?

Apple publishes no quota, but it asks that requests be "reserved for matters of genuine urgency." Using the form for routine releases undermines future requests.

Can I ask for an expedite by replying to App Review?

No. Apple says not to use "Reply to App Review" to request an expedited review or to appeal. Use the dedicated Contact Us form (source).

Is there an expedited review on Google Play?

Google Play has no public expedite request. Plan releases with managed publishing and staged rollouts in the Play Console.

Apple Expedited Review: How to Request It (Steps, Template, FAQ)