How do I test my Lovable app?

Work through core user flows manually in Preview and on a published link, on desktop and mobile, as a logged-out user and as a normal account — not just as the builder.

How do I test mobile devices?

Open the published site on a real phone (or use your browser's device toolbar as a fallback) and check layout, tap targets, forms and navigation at common breakpoints.

Submit every form with valid, invalid and empty data, confirm error messages appear, and check that submitted data actually lands where it should (database, inbox or integration).

How do I test user registration?

Sign up with a real and a duplicate email, confirm verification emails arrive, check password rules, and confirm a new account only gets the access it should.

How do I test password reset?

Request a reset with a real account, confirm the email arrives with a working link, complete the reset, and confirm the old password stops working and the reset link can't be reused.

How do I test payments?

Run a real Stripe test-mode transaction end to end — checkout, webhook, database update and confirmation email — before switching to live keys.

How do I test admin permissions?

Log in as a non-admin account and try to reach every admin action directly (URLs, buttons, API calls) to confirm the server — not just the UI — blocks it.

Try reading and writing data as a different logged-in user and as a logged-out visitor to confirm row-level security actually blocks what it should, rather than assuming the policy is correct.

Check that every page has a unique title and meta description, images have alt text, the site generates a sitemap, and preview the page as a search engine or social share would see it.

How do I test website speed?

Run the published (not local) URL through a tool like Google PageSpeed Insights or WebPageTest, and check real load times on mobile data, not just your fast office wifi.

How do I test different browsers?

Open the published site in at least Chrome, Safari and Firefox on both desktop and mobile, and check layout, forms and any browser-specific features work in each.

How do I check for broken links?

Click through every nav item, footer link and CTA yourself, or ask Lovable to list every link on the site so you can verify each one resolves before launch.

How do I check for console errors?

Open your browser's developer console on every key page of the published site and look for red error messages — then ask Lovable to fix each one by name.

How do I back up my project before launch?

Q: What should I check before launching a Lovable website?

Run through security, forms, auth, payments, mobile display, browser compatibility, speed, SEO basics and broken links before you hit Publish.

Last checked 31 Aug 2026

Short answer

Bookmark the current state in Version history, and push to a connected GitHub/GitLab repo via Git sync so you have a full backup outside Lovable too.

Two layers of backup

Lovable keeps an automatic Version history of your project, but before a launch it's worth deliberately creating a clear restore point, plus a copy outside the platform.

Bookmark a version: open Version history and bookmark the current, working state with a clear label (e.g. "pre-launch, all tests passed"). This makes it easy to find and revert to later, distinct from the constant stream of auto-versions.
Connect Git sync (GitHub, including Enterprise, or GitLab) if you haven't already, and push the current state. This gives you a full commit history outside Lovable, which is useful even if Lovable's own history is fine — it's a genuinely separate copy.
Download the code as an extra local copy if you want a backup that doesn't depend on any third-party service being available.

Recommended order right before launch

Finish and test all changes.
Bookmark the version in Version history.
Push to Git sync (or set it up now if you haven't).
Publish.
If something goes wrong after publishing, use Version history to revert to your bookmarked version rather than trying to manually undo changes.

A prompt if you're not sure Git sync is connected

Confirm whether this project is connected to a GitHub or GitLab repository via Git sync, and if not, help me set that up before I publish.

What usually goes wrong

Relying only on Lovable's automatic versioning and never bookmarking a clear "known good" point, making it harder to find the right version later among many auto-saves.
Setting up Git sync for the first time after something has already broken, instead of before launch when it's simple.
Forgetting that database schema/data isn't captured by code version history — if you're relying on Lovable Cloud, ask Lovable about your data backup options separately from code versioning.

Sources

Was this answer helpful?