Deploy the rendering mode you plan to ship
Publish the static build or adapter-backed on-demand build, then verify every route in scope opens from the review environment.
Paste a browser-accessible Astro deployment, send one review link, and collect comments on the pages and interactive states people will actually see. Every note keeps its page, browser, device and screenshot context.
Loved by1,250+Agenciesand companies in 100+ countries
Astro's build output uses static mode by default. Pages can instead use on-demand rendering, which requires an adapter for the chosen server runtime. A normal build writes to dist by default.
Those choices change what a reviewer can open. Four boundaries matter:
astro dev runs a local development server. astro preview serves the built static directory locally and Astro explicitly says it is not designed for production. Deploy the build or intentionally expose a secure HTTPS tunnel.
Static mode prerenders pages by default. On-demand rendering requires an adapter and a host that supports the selected runtime, so review on the intended deployment target.
astro build creates deployment output, in dist by default. A hosting service or server must publish that output at an address reviewers can reach.
Pasting a URL does not bypass deployment access, application authentication, or hosting controls. Supply permitted access or use the Feedback Widget inside the browser-facing site when appropriate.
How it works
Publish the static build or adapter-backed on-demand build, then verify every route in scope opens from the review environment.
Paste the accessible deployment URL into BugSmash and share the generated link. Reviewers comment on the rendered site without repository or hosting-dashboard access.
Each item keeps the page URL, selected element, screenshot, browser and device so the team can reproduce and route the change.
Attach a note to the visible interface instead of translating it into a component or file description.
Check desktop, tablet and mobile views and retain the viewport with each comment.
The page URL, browser, device and screenshot arrive with the report.
Review prerendered pages and accessible on-demand routes on the same deployment mode intended for release.
Preserve review decisions independently of later builds, adapter changes or hosting updates.
Turn visual feedback into work for content, design, frontend or platform teams with its original context.
BugSmash reviews a browser-accessible Astro deployment. Rendering mode, hosting configuration and access controls determine what reviewers can open.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public Astro static deployment | Works | Paste the hosted site URL and review the pages included in the build. |
| Public adapter-backed on-demand deployment | Works | Use the deployed URL after verifying the adapter and runtime behave as intended. |
| Accessible hosting preview | Works | Share the preview URL after confirming reviewers can open every route in scope. |
| Preview protected by supported Basic Auth | Works | Provide the permitted Basic Auth credentials through the supported review flow. |
| astro dev or astro preview on localhost | Not directly | Deploy the build or expose the local server through a secure HTTPS tunnel. |
| Site behind application login or SSO | Use the Widget | Install the Feedback Widget in the site so reviewers can comment while remaining inside the authenticated browser session. |
Add the BugSmash script to the browser-facing Astro output when reviewers need to remain inside authenticated or stateful routes. Install it in the rendered site, independent of whether the route is static or rendered on demand.
Keep content, design, engineering and QA reviewing the same deployed site and rendering mode.

Review complete pages and responsive layouts on a deployment stakeholders can actually open.
See how
Receive visual reports with the route, selected element, browser, device and screenshot already attached.
See how
Validate static and on-demand routes on the intended adapter and hosting target before release.
See howMore platforms
Read the published workflow guide for another website builder, CMS, framework or AI site platform.
A comment on the deployed site becomes a task with the page, selected element, screenshot, browser and device context attached.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the site, campaign PDF, walkthrough video, launch images, email and presentation in one review project with one approval trail.
No. BugSmash reviews the browser-accessible deployment rather than connecting to Astro, its source files or its adapter.
Paste an accessible Astro deployment URL and send the first review link in under a minute.
