Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Collect visual feedback on a website built with Next.js. Create a BugSmash Website project with a public URL or a site protected by Basic Auth, then share its review link for contextual comments. Other application logins, SSO, CAPTCHA, VPN and network restrictions may require the Feedback Widget or HTML workflow. This is not a native Next.js integration: BugSmash reviews the resulting browser page and does not connect to Next.js itself. The .vercel.app address is an illustrative Vercel-hosted deployment, not a hostname supplied by Next.js itself. Other hosts and custom domains can also serve the published frontend. https://your-app.vercel.app Platform clarification: this is a generic BugSmash Website project workflow, not a native Next.js integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your Next.js application
Paste a browser-accessible deployment URL, send one review link, and collect comments on the routes your users will actually open. Every note keeps its page, browser, device and screenshot context.
Loved by1,250+Agenciesand companies in 100+ countries
Next.js controls how the application is built and rendered. Review still happens on the deployed result.
Next.js officially supports Node.js servers, Docker containers, static exports and platform adapters. Node.js and Docker support all framework features, while static export support is limited and adapter support varies.
Those deployment choices change what a reviewer can exercise. Four boundaries matter:
01
The development server is not the review release.
The official scripts separate next dev from next build and next start. Use a deployed build or an intentionally shared tunnel instead of treating localhost as a durable client URL.
02
A static export has deliberate feature limits.
Next.js can export HTML, CSS and JavaScript for static hosting, but features that require a server are unavailable. Review against the same deployment mode planned for release.
03
Adapter support depends on the platform.
The Next.js documentation states that support varies across adapters and hosting integrations. Validate the routes and runtime behavior on the actual target platform.
04
One page does not represent every route or state.
File-system routes, dynamic segments, server-rendered data and client interactions can produce different browser states. Include the routes and test data that need approval.
BugSmash adds the review layer around the deployment:
review the accessible application route by route, keep comments tied to the rendered interface, and preserve an approval record outside the framework and hosting provider.
How it works
Three steps to a reviewed Next.js application
11
Deploy the build you want reviewed
Use the Node.js, Docker, static-export or adapter-based deployment that matches the release, then confirm its browser URL is accessible to reviewers.
22
Send one review link
Paste the deployed URL into BugSmash and share the generated link. Reviewers open the rendered application without needing repository or hosting-dashboard access.
33
Resolve feedback route by route
Each comment carries the page, selected element, screenshot, browser and device. Assign it, update its status, or send it into the team's delivery tools.
Review the deployed Next.js experience, route by route
Comment on rendered routes
Attach feedback to the interface the reviewer sees instead of translating it into a pathname and component description.
Review responsive layouts
Check desktop, tablet and mobile states from one link and keep the viewport with every comment.
Capture browser context
Browser, device, screenshot and page URL arrive with each report.
Cover server and client behavior
Review routes using the same rendering and runtime mode as the intended release.
Keep deployment sign-off
Preserve the review record independently of later builds, cache updates or hosting-provider changes.
Route work to the right owner
Turn visual feedback into tasks for design, frontend, backend or platform teams with the original context attached.
Will it work on my Next.js deployment?
BugSmash reviews a browser-accessible deployment. The hosting platform, runtime and application access controls still determine what the reviewer can open.
Your URL
Review by URL
What to do
Public Node.js or Docker deployment
Works
Paste the deployed URL and review the complete application.
Public static export
Works
Paste the static-site URL and review the routes included in the export.
Accessible hosting-provider preview
Works
Use the provider's preview URL after confirming the reviewer can open it.
Preview protected by a shared Basic Auth gate
Works
Authenticate inside the review window, then continue to the application.
localhost from next dev
Not directly
Deploy the build or expose the local server through a secure HTTPS tunnel.
Application behind login or SSO
Access-dependent
Use a permitted test account for a standard login flow, or install the BugSmash Feedback Widget for stateful or SSO-only sessions.
Using the BugSmash Feedback Widget in a Next.js application
Add the BugSmash script to the rendered application when reviewers must remain inside authenticated, personalized or long-lived client state. Install it in the browser-facing application, regardless of the deployment runtime.
The feedback workflow for teams using Next.js
From preview deployments to production releases, keep product, engineering and QA teams reviewing the same deployed Next.js application.
Ship faster togetherThe all-in-one workspace for product teams.
Get started free
MayaMake this hero image full-bleed
Live WebsiteURL
product-launch.mp4
0:42 / 3:15
LeoTrim the intro to 0:03
VideoMP4
sneaker.glb
AvaSmooth these edges a bit
3D ModelGLB · GLTF
Quarterly Review
Q3 Performance
Revenue up 24%1.2k new usersNPS score 62Churn down 3%
BugSmash3 / 18
SamUpdate the Q3 numbers
Slide DeckPPT
Your summer sale starts now 🌞
A
Acme Store
to you
9:24 AM
Up to 40% off
Summer essentials, restocked
Shop the sale
NoahStronger CTA copy here
EmailHTML
9:41
Good morning
Dashboard
Balance
$4,280
ZoeAlign the chart legend
Mobile AppAndroid · iOS
Annual Report2025 in review
This 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.
Fig 1. Coastal expansion, 2025
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.
No. Next.js officially supports Node.js servers, Docker containers, static exports and platform adapters. Use any browser-accessible deployment that supports the framework features your application needs.
Can I review a hosting-provider preview URL?
Yes when the URL is accessible to the reviewer. Preview URLs and their access controls are hosting-provider features rather than a requirement of Next.js.
Should I review next dev?
The next dev command starts the development environment. For client review, use a deployed build or intentionally expose the local server through a secure HTTPS tunnel.
Does a static export behave like a server deployment?
Not in every case. Next.js documents static export as having limited feature support because server-required features are unavailable. Review the deployment mode you plan to release.
Can I review dynamic routes?
Yes when the deployed application exposes them and the reviewer has the required data and access. Include each route and state that needs approval in the review plan.
Will adapter-based hosting support every Next.js feature?
Not necessarily. The Next.js deployment documentation says adapter support varies, so verify feature support in the platform's documentation and review on the target deployment.
Can reviewers test a signed-in application?
A standard login flow can be reviewed with a permitted test account. For SSO-only or long-lived stateful sessions, use the BugSmash Feedback Widget inside the application.
Do reviewers need repository access?
No. They review the deployed browser interface, not the source repository or hosting dashboard.
Ship Next.js applications without chasing feedback
Paste an accessible Next.js deployment URL and send the first review link in under a minute.
BugSmash adds the review layer around the deployment:
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks
MayaMake this hero image full-bleed
product-launch.mp4
LeoTrim the intro to 0:03
AvaSmooth these edges a bit
SamUpdate the Q3 numbers
Up to 40% off
NoahStronger CTA copy here
ZoeAlign the chart legend
EllaTighten this paragraph
TheoBoost the warm tones
MiaCut the dead air at 1:12