Publish the app
Publish a snapshot to the generated lovable.app URL or a connected custom domain. Later project changes stay off the live app until you choose Publish changes.
Review the release your visitors will actually use. Paste the lovable.app URL or custom domain, send one link, and collect comments with page, browser, device and screenshot context attached.












Loved by1,250+Agenciesand companies in 100+ countries
Lovable's Project comments and shared preview links are strong tools for feedback while the app is being built. Guests can pin comments on a preview without a Lovable account when comments are enabled.
For client approval on the shipped experience, four differences matter:
Lovable anchors Project comments to elements in the project preview. The published app is a separate snapshot at its own URL and only changes when you publish again.
Free and Pro preview links expire after 7 days. Business and Enterprise can choose 24 hours, 7 days, 30 days or no automatic expiration, while a published lovable.app URL is the ongoing app address.
When a shared preview link expires or is deleted, guest commenting through that link stops. That makes it useful for a review round, but different from a durable approval record tied to the published release.
Guest comments notify the project owner in Lovable and collaborators reply from the project. Delivery teams may still need Jira, ClickUp, Slack or a client-facing record that survives project handoff.
How it works
Publish a snapshot to the generated lovable.app URL or a connected custom domain. Later project changes stay off the live app until you choose Publish changes.
Paste the published URL into BugSmash and share the resulting link. Reviewers work on the live release without access to the Lovable editor, project chat or source code.
Every comment carries the page, element, browser, device and screenshot. Track status, capture approval, or route the item into the team's task system.
Review the lovable.app URL or custom domain that visitors use, separately from the latest working preview in the editor.
Open the same review at desktop, tablet and mobile sizes and keep each comment tied to its viewport.
Every issue arrives with the environment and screenshot needed to reproduce it.
Lovable publishes snapshots only when you choose Publish changes. Keep feedback and approval associated with each reviewed release.
Reviewers can sign off without receiving access to the Lovable editor, project chat or source code.
Send actionable comments into the task and communication tools used after the build leaves Lovable.
Lovable separates the latest working preview from the published snapshot. Choose the URL that matches what you want reviewed.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public app on a lovable.app URL | Works | Paste the published URL and start the review. |
| Public app on a custom domain | Works | Publish the project and wait until the connected domain is live, then paste the domain. |
| Active shared preview link without a password | Works while active | Use it for an in-progress round. Free and Pro links expire after 7 days; published URLs are the better long-term record. |
| Password-protected shared preview link | Works while active | Enter the preview-link password in the review window. Business and Enterprise control its expiration. |
| Workspace or custom-audience published app | Access-dependent | Lovable requires invited viewers to sign in with the permitted email. Use a public review release or the BugSmash Feedback Widget when that access flow blocks URL review. |
| App login using a username and password form | Works | Sign in to a test account inside the review window. Social and SSO-only flows need the BugSmash Feedback Widget. |
Ask Lovable to add the BugSmash script to the app shell when reviewers need to comment inside a stateful or authenticated flow. Keep Lovable's Project comments for build feedback; use the BugSmash widget for the published experience and the broader approval workflow.
From preview feedback to published-app sign-off, keep founders, agencies and product teams aligned on the same Lovable release.

Collect structured beta feedback on the published app instead of reconstructing the browser, page and device from a message.
See how
Move from in-project review to a client approval record tied to the published snapshot and ready for handoff.
See how
Review landing pages, responsive states and conversion flows, then route actionable changes into the tools used to ship them.
See howA comment on the published release becomes a task with the URL, selected element, screenshot, browser and device details already included.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the published app beside the pitch deck, product PDF, demo video, launch images, email campaign and mobile build, with every approval in the same project.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

Use a shared preview link for work in progress and the published URL for release approval. Lovable says the preview always shows the latest working version, while the published app is a snapshot that changes only when you publish again.
Paste your published Lovable URL and send the first review link in under a minute.
