Skip to content

Marker.io

Marker.io captures a screenshot and feedback from a page and gives your team an issue to inspect.

Visit Marker.io

What does a report give you besides the comment?

Marker.io can attach a screenshot of the page to a report. Ask the reporter what they tried and what they expected next. Check whether your project captures browser details, activity or other diagnostics as well. Use a page with fictional records when checking the capture, and keep sensitive pages outside the rollout until you know what leaves the browser.

Who can see or follow an issue?

Widget reporters can submit and follow their own reports without a paid seat. Invited guests can see other guest feedback by default on the project, with a setting to limit that. The report guide describes email updates for comments and resolution. Check the role and audience before asking a customer to send a screenshot.

What affects the bill and what does CSV keep?

Plans list how many team members manage reports. Team includes session replay and developer diagnostics. The export guide requires an admin or manager and Team or above. The CSV includes a screenshot URL. If your team needs to preserve the image, verify you can keep a separate authorized copy and check who can access the export.

Could someone else reproduce the broken button?

Sketch a fictional confirmation button that disappears on a small screen. Add the page, window size, last action and expected result to the report on paper.

  1. Mark what is safe to capture
    Circle the broken control on the sketch and leave the fictional billing and account details outside the capture.
  2. Compare two reports
    If both need the same fix at the same screen size, record their relationship. Keep a report from a different size if it needs a different fix.