InterLAB tools · Masking · steps · GitHub/GitLab/Jira

Screenshot → Bug report

Add a screenshot or a screen recording, hide personal data, mark the problem and the steps — the tool builds a bug report with reproduction steps, environment and parsed logs, checks its quality and exports it to GitHub, GitLab or Jira.

Free, no sign-up

Files never leave the browser: images and videos stay only in this tab's memory, the report text in localStorage. PNG export is re-encoded through a canvas — metadata (EXIF, location) is removed.

Screenshots and screen recordings

Drag images or videos here, paste a screenshot from the clipboard (Ctrl+V) or choose files. Images: PNG, JPEG, WebP up to 20 MB; video: MP4, WebM up to 500 MB.

Drop files here or paste a screenshot (Ctrl+V)

The browser asks what to share; one frame is taken and the capture stops immediately.

Images

No images yet.

How the tool works

Files
PNG, JPEG, WebP images — drag and drop, paste from the clipboard (Ctrl+V) or choose files; MP4 and WebM video — a frame at the right moment becomes an image with a timestamp; a screen capture — only on click, one frame.
Markup
Hide with a solid fill or large-block pixelation, boxes, arrows and step markers; undo and redo; the same with numbers from the keyboard. The original is untouched: hidden areas are burned only into the exported PNG.
Description
The problem type suggests “expected” and “actual” templates and what to attach; the title is checked for specificity; the environment can be filled from the browser as a starting point.
Logs
Console output, error text or HAR is parsed with rules: error messages, the first app frame in the stack, HTTP errors with token-free URLs.
Check and export
A scan for secrets and personal data in the text with masking, a rule-based quality check, a mandatory “I checked the images” tick, then Markdown for GitHub/GitLab, Jira wiki, text, PNG and JSON.

Severity and priority

Level	Definition
S1 — blocker	A core function is unavailable, data is lost or corrupted, or security is at risk; no workaround.
S2 — major	An important function works incorrectly; a workaround exists but is awkward.
S3 — moderate	A function misbehaves with an easy workaround; noticeable layout defects.
S4 — minor	Cosmetic issues, typos, small misalignments; usage is not affected.

S1 — blocker

Definition: A core function is unavailable, data is lost or corrupted, or security is at risk; no workaround.

S2 — major

Definition: An important function works incorrectly; a workaround exists but is awkward.

S3 — moderate

Definition: A function misbehaves with an easy workaround; noticeable layout defects.

S4 — minor

Definition: Cosmetic issues, typos, small misalignments; usage is not affected.

Severity — how badly the bug gets in the way

Priority is the fix order; it is usually set by the product owner, not the reporter:

P1 — fix immediately
P2 — in the current sprint or release
P3 — schedule it
P4 — when there is time

Report quality check

The table is generated from the same code as the check. “Required” rules keep the report “not ready”; “recommended” ones make it “almost ready”.

ID	Rule	Level	How it is checked
BUG-Q01	The title exists and is not too short	required	At least 12 characters and 3 words
BUG-Q02	The title is specific	recommended	Besides words like “not working”, “bug”, “error” there are at least 2 meaningful words
BUG-Q03	Reproduction steps exist	required	At least one non-empty step
BUG-Q04	Steps start from a defined state	recommended	Preconditions are filled, or step 1 is “Open / Go to / Sign in…”, or contains a URL
BUG-Q05	The expected result is described	required	“Expected result” is not empty and not a template
BUG-Q06	The actual result is described	required	“Actual result” is not empty and not a template
BUG-Q07	The environment is stated	recommended	Browser and OS (or device) are filled
BUG-Q08	No secrets or personal data in the text	required	The scan for tokens, keys, passwords, emails, phones, card numbers and tokens in URLs finds nothing
BUG-Q09	Images reviewed by a person after the last edit	required	“I have checked…” is ticked after the last image change
BUG-Q10	Severity is set	recommended	A level S1–S4 is chosen
BUG-Q11	Image markers match steps	recommended	Every marker number is within the number of steps
BUG-Q12	Expected and actual differ	recommended	The texts are not identical

BUG-Q01

Rule: The title exists and is not too short
Level: required
How it is checked: At least 12 characters and 3 words

BUG-Q02

Rule: The title is specific
Level: recommended
How it is checked: Besides words like “not working”, “bug”, “error” there are at least 2 meaningful words

BUG-Q03

Rule: Reproduction steps exist
Level: required
How it is checked: At least one non-empty step

BUG-Q04

Rule: Steps start from a defined state
Level: recommended
How it is checked: Preconditions are filled, or step 1 is “Open / Go to / Sign in…”, or contains a URL

BUG-Q05

Rule: The expected result is described
Level: required
How it is checked: “Expected result” is not empty and not a template

BUG-Q06

Rule: The actual result is described
Level: required
How it is checked: “Actual result” is not empty and not a template

BUG-Q07

Rule: The environment is stated
Level: recommended
How it is checked: Browser and OS (or device) are filled

BUG-Q08

Rule: No secrets or personal data in the text
Level: required
How it is checked: The scan for tokens, keys, passwords, emails, phones, card numbers and tokens in URLs finds nothing

BUG-Q09

Rule: Images reviewed by a person after the last edit
Level: required
How it is checked: “I have checked…” is ticked after the last image change

BUG-Q10

Rule: Severity is set
Level: recommended
How it is checked: A level S1–S4 is chosen

BUG-Q11

Rule: Image markers match steps
Level: recommended
How it is checked: Every marker number is within the number of steps

BUG-Q12

Rule: Expected and actual differ
Level: recommended
How it is checked: The texts are not identical

Check rules v1.0 of 2026-10-13

Problem types and their templates:

Problem type	Title template	What to attach
Broken layout / overlapping elements	[Page]: [element] overlaps [element] at [N] px width	A screenshot with the area highlighted and the window width.
Truncated text	[Page]: “[field]” text is cut off when [condition]	A screenshot and the full text that should be visible.
Wrong data	[Page]: [field] shows [what], expected [what]	A screenshot with the value highlighted and where the correct value comes from.
Error message	[Page]: “[error text]” when [action]	A screenshot of the message, the console output and the failing network request.
Blank screen / crash	[Page]: blank screen after [action]	Console output (the error stack) and a screen recording of the crash.
Slow loading	[Page]: loading [what] takes [N] s	Timing from a stopwatch or the Network tab, connection speed, a video.
Broken image	[Page]: image [which] does not load	A screenshot and the image URL from the Network tab (response status).
Accessibility: contrast, focus	[Page]: [element] — [no visible focus / low contrast]	A screenshot with highlighting, the Tab order, the measured contrast.
Console error	[Page]: console error “[text]” when [action]	The full console output (stack) and the steps that trigger it.

Broken layout / overlapping elements

Title template: [Page]: [element] overlaps [element] at [N] px width
What to attach: A screenshot with the area highlighted and the window width.

Truncated text

Title template: [Page]: “[field]” text is cut off when [condition]
What to attach: A screenshot and the full text that should be visible.

Wrong data

Title template: [Page]: [field] shows [what], expected [what]
What to attach: A screenshot with the value highlighted and where the correct value comes from.

Error message

Title template: [Page]: “[error text]” when [action]
What to attach: A screenshot of the message, the console output and the failing network request.

Blank screen / crash

Title template: [Page]: blank screen after [action]
What to attach: Console output (the error stack) and a screen recording of the crash.

Slow loading

Title template: [Page]: loading [what] takes [N] s
What to attach: Timing from a stopwatch or the Network tab, connection speed, a video.

Broken image

Title template: [Page]: image [which] does not load
What to attach: A screenshot and the image URL from the Network tab (response status).

Accessibility: contrast, focus

Title template: [Page]: [element] — [no visible focus / low contrast]
What to attach: A screenshot with highlighting, the Tab order, the measured contrast.

Console error

Title template: [Page]: console error “[text]” when [action]
What to attach: The full console output (stack) and the steps that trigger it.

Limitations

The tool does not read text in images and does not find personal data in them by itself — a person does; the secret scan covers only the report text.
Pixelation uses 12–48 px blocks, so text under it is unreadable. Pixelated small areas are sometimes attacked by brute-force reconstruction, so use a solid fill for passwords, tokens and card numbers.
The secret and personal-data scan is pattern-based: it hints, it does not guarantee. It will not recognise unusual keys or people's names.
The environment filled from this browser may differ from the one where the bug happened.
The “new issue” link passes the text in the page address: a long report is shortened (the full text is copied to the clipboard), and images must be attached manually.
Images and videos are not kept after a page reload — only the report text is.

Privacy

Files never leave your browser: images and videos are processed in this tab's memory and are not uploaded anywhere.
PNG export re-encodes the image through a canvas: the source file's metadata (EXIF, location, device model) is removed.
The report text and versions are stored in this browser's localStorage; “Clear all” deletes them.
Text goes to GitHub or GitLab only after your confirmation — in the address of a new tab.
Analytics receives only the fact of an export and its format — no content.
The result reaches us only if you send a request yourself and keep the “Attach the result” box ticked — the form shows exactly what will be sent: the title, severity, frequency, environment, number of steps and check results. Images and videos never go with the request, and neither do console logs or the page address with parameters.

Related tools

All tools · 40

Release readinessAn evidence-backed check matrix: CI, migrations, backups, a rollback plan, monitoring, risk exceptions and sign-off → a GO / NO-GO decision.

User flow testerA user-flow builder → ready Playwright tests guarded against running on production, coverage of key routes and a pass/fail results view.

API Mock StudioImport OpenAPI or define endpoints → test data, different HTTP responses, delays and errors, a request log, contract checks and a ready mock server.

UI consistency checkerDesign tokens vs CSS: off-system colours and sizes, WCAG contrast, screenshot comparison against an approved baseline, and triage.

MVP validation toolkitHypotheses with thresholds, a landing page and lead form, UTM links, a funnel, interviews and an experiment report → continue, pivot or stop.

Proposal builderProposal templates for IT projects: scope, phases, estimate, timeline, assumptions and exclusions, versions with number control, approval and PDF.

Tell us about your task — we'll review your request and get back to you

Need a product quality audit?

The InterLAB audit is a paid review of the UI, code and testing process with prioritised fixes. The first short conversation about the format is free.

The first short conversation is free — we choose the format
NDA — yours or ours
Pricing after a brief and an agreed scope

Message on WhatsApp