Quick Answer
A bug report builder turns a rough description into the structured report maintainers need: numbered steps to reproduce, expected vs actual result, severity, and the exact environment. This free tool auto-detects your browser, engine, OS, viewport, screen, language, and timezone — every value stays editable — then formats everything (plus pasted console errors and a screenshot) as a GitHub-flavored Markdown issue, Jira wiki markup, or plain text. It runs entirely in your browser, requires no account, and nothing you type is uploaded.
How It Works
Pick a preset: Bug report, Feature request (relabels the fields), or Regression (adds "worked in version")
Describe the bug: title, one repro step per line (numbered automatically), expected vs actual, and severity
Confirm the environment: edit any auto-detected value (browser, OS, viewport, timezone…) and paste the page URL
Paste console errors verbatim and optionally drop in a screenshot to embed or attach
Copy or download the report as Markdown, Jira wiki markup, or plain text
Key Facts
- Three template presets: bug report, feature request (relabels the fields), and regression (adds "worked in version")
- Environment auto-detected: browser and version, engine, OS, viewport, screen and pixel ratio, languages, timezone, cookies, connection type where available
- Every detected value sits in an editable field marked "detected" — you confirm before exporting
- User-agent parsing is built in (Chrome, Edge, Firefox, Safari, Samsung Internet, Opera, mobile variants) with no external library
- Pasted console errors are re-indented, grouped into blocks on blank lines, and numbered (Error 1, Error 2…)
- Optional screenshot: embed as a data URL in Markdown (with a size warning past 2 MB) or reference ./screenshot.png and download the image separately
- Live preview in all three formats as you type, with copy and download (Markdown .md, Jira and plain text .txt)
- Your report is saved in this browser (localStorage) and survives a refresh; a one-click sample shows a realistic fictional bug
- Free with no account, no limits, and no uploads — the tool works offline once the page has loaded
Frequently Asked Questions
How does the environment detection work?
The tool reads browser APIs available on the page — navigator.userAgent, screen, window dimensions, navigator.languages, Intl.DateTimeFormat for the timezone, navigator.cookieEnabled, and navigator.connection.effectiveType where the browser exposes it. The user-agent string is parsed by a small built-in parser (no external library) that recognizes Chrome, Edge, Firefox, Safari, Samsung Internet, Opera, and their iOS variants, plus Windows, macOS, Android, iOS, Linux, and ChromeOS. Each detected value lands in an editable input marked "detected", so you can correct anything before it reaches the report.
Is this bug report builder free?
Yes — free with no account, no limits, and no watermarks. Tracker-side alternatives are usually part of a paid plan (for example, Jira Cloud Standard runs $8.60 per user per month on annual billing) and still make you assemble the report by hand; this tool just formats what you already know.
Is my data private?
Yes. The builder runs entirely in your browser with client-side JavaScript. Your report, pasted console output, and screenshot are never uploaded, logged, or shared — the only storage is this browser’s localStorage so a refresh does not lose your work, and Clear all wipes it. Screenshots above roughly 1.5 MB are kept for the session but not persisted across refreshes to respect storage quotas.
What is the difference between the Markdown, Jira, and plain text formats?
Markdown emits a GitHub-flavored issue body: bold section labels, a numbered repro list, a bullet environment list, and the console output in a fenced code block. Jira emits Jira wiki markup instead: h2. headings, *bold*, * bullets, and {noformat} blocks you can paste into a Jira description field. Plain text drops all markup for email or chat, using uppercase section headers and two-space indentation. The preview switches instantly and copy/download work per format.
How should I attach a screenshot?
Two ways. "Reference ./screenshot.png" keeps the report small — download the image with the button next to the thumbnail and attach it when you file the issue. "Embed as data URL" inlines the image directly in the Markdown, which suits pasting into systems without attachments, but the tool warns you above 2 MB because issue bodies that large are often rejected. You can switch modes at any time; the image itself never leaves your browser either way.
What makes a good bug report?
A minimal set of numbered reproduction steps anyone can follow, the expected and actual results stated separately, the severity in the reporter’s honest judgment (blocker means work stops; trivial means cosmetic), and the exact environment — browser, version, OS, viewport, and URL. Console errors pasted verbatim, not paraphrased, plus a screenshot of the failure state. This tool structures all of that; the sample button loads a fictional "Export button downloads .txt instead of .csv" report you can use as a model.