How Long Does ICP Filing Take?

Quick answer
The provincial review commonly takes a few weeks, and the whole process from entity setup to approved filing usually takes about a month.
Corrections reset the clock in practice, because the application is not being reviewed while it waits for your response.
Domain real-name verification and entity registration often take longer than the filing review.
Any change of domain, registrant, or hosting provider means an update, which has its own wait.
Do not tie a launch date to the filing without a buffer; a rejected detail can cost another cycle.

How long does ICP filing take?

A complete, consistent application usually clears provincial review in a few weeks, and a realistic end-to-end estimate is about a month. The review itself is only one segment: before it starts you need the entity documents, a domain registered to that entity and verified, and a mainland hosting contract.

The variance is provincial and seasonal. Some administrations process quickly; others are slower or request more documents. Applications submitted around public holidays lose days. Treat any specific number as an average, not a commitment, and plan the launch around the buffer rather than the average.

Typical elapsed time, complete package
  Entity registration / document prep   days to weeks (existing entity: 0)
  Domain registration + real-name check 1-3 days after payment clears
  Hosting purchase + IP assignment      same day to a few days
  Provider review before submission     1-3 days
  Provincial review                     a few weeks
  Correction loop, if any               adds one cycle per round
  PSB filing after go-live              separate, commonly 30-day window

What makes it take longer?

Corrections are the main cause. A name mismatch, a missing authorisation letter, an unclear site description, or an expired identity document sends the application back. Each round adds the response time plus a new review queue, so two corrections can turn a month into six weeks.

Content category is the second. If the site appears to belong to a regulated category, the application is routed for additional review or an additional approval, which is a different process with a different timeline. Describing an ordinary app as a news or finance service is a self-inflicted delay.

Does the domain or host affect the timing?

Yes. A domain registered abroad may need to be transferred to an accredited registrar and verified before it can be filed, which adds days and sometimes requires a waiting period. A hosting provider that does not support filing in your province forces a change of provider, and that change restarts the hosting part of the package.

Changing the hosting provider after approval usually requires an update to the filing. The new provider submits the change, and the site may need to remain on the old provider until it is processed. Plan migrations around the filing calendar rather than the other way round.

How should you plan a launch around it?

Work backwards from the launch date and put the filing first. Entity and domain work can start months earlier and cost little to maintain. Submit as soon as the hosting is live, and keep a buffer of at least two weeks beyond the expected review for a correction round.

If the launch cannot wait, launch outside the mainland first and file for the mainland domain in parallel. Serving users from Hong Kong or Singapore is a legitimate interim step and does not create a compliance problem as long as the site is not hosted in the mainland. Moving to mainland hosting later is a migration, not a relaunch.

Where this bites vibecoders
AI-assisted teams tend to plan the build and treat compliance as a step after deploy. The filing is the longest dependency in a mainland launch, and it starts with paperwork that has nothing to do with code. Put it on the critical path before the first sprint, not after the app is feature-complete.

Where AI coding assistants get this wrong

Scheduling a launch date at the end of the expected review window with no buffer.
Starting the filing only after the app is built and deployed.
Changing the hosting provider during review.
Submitting with an expired identity document or business license.
Assuming a correction is a same-day fix.
Forgetting the separate public security filing after go-live.

Checklist

Start entity and domain work before the build.
Verify the domain registrant before submitting.
Submit as soon as mainland hosting is active.
Keep a two-week buffer beyond the expected review.
Respond to corrections the same day they arrive.
Calendar the PSB filing window after launch.

FAQ

Can ICP filing be expedited?

Not through an official fast track. Agents sometimes know the provincial process well enough to avoid corrections, which is the realistic form of speed. Anyone promising a guaranteed short approval is describing luck or a different process, not a service level the administration offers.

Does the review run on calendar days or working days?

Official windows are usually expressed in working days, so weekends and public holidays do not count. That is why a three-week estimate can stretch across a holiday period. Ask the provider how the province counts, and add the holidays to your own plan.

How long does a change of hosting take to process?

It follows the same provincial review path, though the package is smaller. Expect days to a couple of weeks, and keep the old hosting active until the update is approved. Shutting down the old site first can invalidate the record you are trying to transfer.

Does a new domain on an existing filing need a new review?

Generally yes, because the filing identifies the domains covered. Adding a domain is an update submitted through the provider. An existing filing for another domain does not automatically extend to the new one, even when the entity and hosting are the same.