guides
Bug reporting & debugging guides
Step-by-step guides for writing bug reports developers can act on — with Chrome’s built-in tools, and the faster way with Bugmark.
- guide
How to write a bug report developers can actually fix
A good bug report lets someone who has never seen the problem reproduce it in minutes. This guide covers the fields every report needs, a copy-paste bug report template, a real example, and the mistakes that send tickets back with "can't reproduce".
Read guide - guide
How to capture a HAR file in Chrome
Support teams ask for a HAR file when they need to see exactly what your browser sent and received. Here is how to record and export one from Chrome DevTools in about two minutes, and how to keep your cookies and tokens out of it.
Read guide - guide
How to capture console logs in Chrome
Console errors are often the fastest route to the cause of a web bug. This guide shows how to open the Chrome Console, keep messages across page loads, save the console log to a file, and share errors in a form developers can act on.
Read guide - guide
Steps to reproduce template and examples
Steps to reproduce (STR) are the part of a bug report developers read first and the part most often done badly. Use the template below, follow a few simple rules, and your bugs will stop coming back marked "cannot reproduce".
Read guide - guide
How to take a full page screenshot in Chrome
Chrome can capture an entire scrolling page as one image without installing anything. It is just hidden inside DevTools. This guide covers the built-in command, mobile-size captures, and what to do when the result looks wrong.
Read guide