Preview your app

The preview runs your application while you build it. Open it inside the editor or in a separate window using the preview controls.

Review changes

Wait for the preview to start and finish syncing. Most frontend changes appear automatically. Dependencies, backend changes or a restart can take longer; use the status and logs instead of assuming a fixed waiting time.

If the page looks stale, wait for the active run to finish, refresh and try again. Report persistent errors with the route and reproduction steps.

Preview is not an isolated database

A Supabase Web app shares its database, authentication and storage with the published app. Creating, editing or deleting data in preview can affect live users. Use clearly marked test records.

The managed payment flow keeps checkout in test mode on recognized preview addresses. A custom Stripe integration must configure its own test keys.

A preview may pause when inactive and need time to resume. Publishing creates a separate app version; see Production.

With managed payments, the preview always pays in test mode with card 4242 4242 4242 4242, also after real payments are activated. Products and prices keep the same identifiers in the preview and on the published site.