Paste the app URL
The development version at version-test, or the live app. If it is behind a login, sign in to a test account inside the review window.
Most Bubble apps live behind a login, which is where most review tools stop. The review window is a real browser, so you sign in to the app inside it and comment on the real screens, with real data.












Loved by1,250+Agenciesand companies in 100+ countries
Bubble has a strong preview and debugger for the person building. It has nothing for the person reviewing.
"The dashboard looks wrong on my laptop." No browser, no screen size, no screenshot, no repeat case.
Which is why most Bubble feedback ends up as a screenshot pasted into Slack.
A comment on "the empty state" and a comment on "the list with forty rows in it" are different comments on the same page, and prose cannot tell them apart.
Bubble deploys are frequent and there is no record of which version a piece of feedback was against.
How it works
The development version at version-test, or the live app. If it is behind a login, sign in to a test account inside the review window.
Your client or tester opens it in their own browser. No Bubble editor access and no BugSmash account.
Every comment carries the page, the element, the browser and a screenshot, and can be pushed into Jira, ClickUp, Linear or Slack.
Comments attach to the thing on the page, so "this heading" is unambiguous without a marked-up JPEG in an email.
Desktop, tablet and mobile in the same link. Responsive is most of the job on a Webflow build, so a desktop-only review is half a review.
Blog posts, case studies, product templates. Each published Collection page is a URL, so each one is reviewable.
Every comment records what the reviewer was on. No follow-up thread to work out why you cannot reproduce it.
Republish, add a new version, and compare against what the client signed off on last round.
Who approved, on which version, on what date. That record stays with you, not with the Webflow site.
The review window loads the page in a real browser session, so anything you can sign in to yourself, you can sign in to here. Nothing is handed over to BugSmash and no credentials are stored.
| Your URL | Review by URL | What to do |
|---|---|---|
| Development version at yourapp.bubbleapps.io/version-test/ | Works | Paste and go. Review before you deploy to live. |
| Live app on bubbleapps.io or a custom domain | Works | Paste and go. |
| App behind a username and password login | Works | Sign in to a test account inside the review window. This covers most Bubble apps. |
| Sign in with Google, or another social provider | Not supported | Install the Feedback Widget so the review layer runs inside the app. |
| Deeply stateful screens, multi-step workflows, plugins | Varies | A proxy renders a page, not a whole session. For flows that depend on state, use the Feedback Widget so reviewers comment inside the app as they use it. |
One script in Settings › SEO and metatags, in the page header field, so it loads across the app. Use version-test while reviewing and take it out before you deploy to live.
From version-test UAT to cross-browser QA, keep founders, agencies and product teams aligned on the exact screen being reviewed.

Client UAT on the development version before deploy, on a list you can close out instead of a call you have to transcribe.
See how
Beta testers report what they saw, on the screen they saw it, with the browser already attached.
See how
Cross-browser QA on a no-code app without asking testers to fill in a form describing their setup.
See howA comment on the hero section becomes a ticket with the URL, the element, the screenshot and the browser already attached.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
A Webflow launch is rarely only a Webflow launch. The same project holds the pitch deck, the brand PDF, the launch video, the ad creative, the email template and the mobile build, each reviewed the same way, each on the same approval record.

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.

Yes, and this is the main reason Bubble teams use it. The review window opens your app in a real browser session, so a test account signs in there exactly as it would in Chrome. BugSmash never takes the credentials and does not store them. Social sign-in is the exception, and the Feedback Widget covers that case.
Paste your Bubble URL and send the first review link in under a minute.
