Deploy the target-specific build
Follow the deployment target's documented setup, then confirm server-rendered or SPA routes behave correctly at an accessible browser URL.
Paste a browser-accessible Remix deployment, send one review link, and collect comments on the routes and application states people will actually use. Every note keeps its page, browser, device and screenshot context.












Loved by1,250+Agenciesand companies in 100+ countries
The Remix v2 deployment guide says Remix runs on your server, but it is not your server. Current Remix documentation directs new projects to React Router v7, whose framework mode supports fullstack hosting and static hosting.
That separation creates four review boundaries:
Remix templates have target-specific files, commands and environment variables. Review on the server, worker, container or static host intended for the release.
Remix SPA mode uses ssr: false and produces a client index.html. The HTTP server must provide an SPA fallback so valid application paths resolve to that file.
The Remix SPA guide says vite preview can inspect the production build locally but is not designed for use as a production server.
Pasting a URL does not bypass deployment access, application login, or hosting controls. Reviewers need permitted access to every protected route in scope.
How it works
Follow the deployment target's documented setup, then confirm server-rendered or SPA routes behave correctly at an accessible browser URL.
Paste the deployment URL into BugSmash and share the generated link. Reviewers work on the rendered application without code or infrastructure access.
Each comment keeps the page URL, selected element, screenshot, browser and device so the team can reproduce the reported state.
Attach feedback to the visible route instead of translating it into route-module or component language.
Check desktop, tablet and mobile views and retain the viewport with every report.
The page URL, browser, device and screenshot arrive with each comment.
Review the actual hosting mode, including server-rendered behavior or static-host SPA fallback routing.
Preserve the review record independently of later builds, runtime changes or hosting configuration.
Turn visual feedback into work for design, frontend, backend or platform teams with the original context.
BugSmash reviews a browser-accessible application. The selected Remix or React Router runtime, hosting mode and application access rules determine what reviewers can reach.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public fullstack Remix deployment | Works | Paste the deployed URL and review the server-backed application. |
| Public Remix SPA-mode deployment | Works | Use the hosted build after verifying its SPA fallback handles direct route requests. |
| Accessible hosting preview | Works | Share the preview URL after confirming the target-specific deployment is complete. |
| Preview protected by supported Basic Auth | Works | Provide the permitted Basic Auth credentials through the supported review flow. |
| Local development server or vite preview | Not directly | Deploy the application or expose the local server through a secure HTTPS tunnel. |
| Routes behind application login or SSO | Use the Widget | Install the Feedback Widget in the application so reviewers can comment while remaining inside the authenticated browser session. |
Add the BugSmash script to the browser-facing application when reviewers must stay inside authenticated, personalized or long-lived client state. Install it in the deployed UI, independent of the server adapter or SPA host.
Keep product, design, engineering and QA reviewing the same deployed runtime and routes.

Review complete routes, loading states and responsive layouts on a deployment stakeholders can open.
See how
Receive visual reports with the route, selected element, browser, device and screenshot already attached.
See how
Validate target-specific runtime behavior, SPA fallbacks and access-controlled routes before release.
See howA comment on the deployed application becomes a task with its route, 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 application, product PDF, walkthrough video, campaign images, email and presentation in one review project with one approval trail.

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.

The official Remix documentation says the latest version of Remix is now React Router v7 and directs developers who want the latest framework features to the React Router documentation.
Paste an accessible Remix deployment URL and send the first review link in under a minute.
