The website feedback tool for visual QA.

A website feedback tool lets reviewers, clients and customers report an issue while looking at the page. With Gleap, they mark the spot on a screenshot of the page, describe what they expected and send. The report arrives in your inbox with the page URL, browser, operating system, screen size, session replay and console logs.

Yes. The Gleap widget opens a screenshot editor on the current page with a rectangle tool, a pen, a blur tool for private content and a color picker. The marked screenshot is attached to the report, so a clipped heading, a wrong image or an overlapping layout is shown, not described.

Yes. One script tag installs the Gleap widget on the site. Anyone who can open the page can report from it: no browser extension, no account, no developer tools. You configure the form, the fields it asks for and the languages it speaks.

Yes. Install the same snippet on staging and share the URL with reviewers. Your staging site's own access control still applies. Gleap projects and tags keep staging feedback apart from production reports, and the same setup can move to the live site at launch.

The marked screenshot, the description, the page URL, browser and version, operating system, screen size and pixel ratio, language, SDK version and session duration. With the web SDK's session replay and console logs enabled, the recording and the last requests come too. Custom data you attach through the SDK, such as the account or campaign, is shown on the ticket.

No. The same report carries a copy correction, a design detail, an unclear instruction or an idea. Your team decides the next step in the ticket: reply, assign, or link it to a request. Ideas that need votes and prioritization belong in your customer feedback software and on the public roadmap.

Same SDK, same report, a different job. The website feedback tool is for visual QA on websites: layout, copy and design issues marked on the page. In-app bug reporting is for defects in a product, where session replay, console and network logs and device data carry the investigation.

Website feedback points at a specific spot on a specific page. A survey asks a question you choose, to an audience you choose. Use in-app surveys for structured answers such as NPS or onboarding feedback, and the feedback tool for the page itself.

It lands in the Gleap inbox as a ticket with the screenshot and context. Your team replies to the reviewer, assigns it and sets a status. From Team, with the Investigate bugs skill on, Kai Support investigates new bug reports from the widget before they reach the inbox and attaches its finding with evidence.

Not without your team's review. A confirmed bug becomes a coding task that Kai Code starts on its own when you allow it, or that your team picks up. From Team, Kai Code plans the change, edits the code, runs the tests and opens a pull request that your engineers review and merge. Once a teammate confirms the fix is live, the reviewer hears back in the same conversation. That is how Gleap closes the loop.

It is one of the inputs. In self-driving development, a report from the page becomes evidence, a finding, a reviewed change and a shipped fix, with your team deciding at each step. Reports through the Gleap widget carry the context that makes the investigation possible. See how software teams run it in AI customer support for SaaS.

They all collect visual website feedback with annotated screenshots. Gleap keeps the report in the same inbox as your customer conversations, adds session replay and console logs from the same SDK, and on Team and up continues into investigation and code with Kai Support and Kai Code. Switching from one of them? Compare Gleap vs Marker.io, Gleap vs BugHerd, Gleap vs Userback and Gleap vs Usersnap.

No, but every plan starts with a 7-day free trial. Starter is $29 per month billed annually ($35 monthly) for one seat and one project: the widget with the screenshot editor, in-app bug reporting, console logs and custom data, plus live chat, Kai Support and Kai Copilot, billed by usage. Reviewers and clients report without an account. Starter has no ticket limit and keeps the full ticket history. Team ($149 per month billed annually, $179 monthly) adds unlimited seats and projects, session replay, integrations such as Jira and Linear, Kai Support's investigations and Kai Code, with their AI usage billed by the work they do. See pricing.