From screenshot to bug report in one keystroke
Right-click a capture. Get the app, version, macOS and window, as a Markdown table or a full report.
A screenshot of a bug is half a bug report. The other half is the stuff nobody types: which app, which version, which macOS, which display, light or dark, and which page. Developers ask for it every time. Reporters forget it every time.
Frayo writes that half for you.
It notes the setting while you capture
When you take a screenshot, Frayo saves a small note beside it. The note holds:
- the front app, its version and bundle ID
- the window title
- the page address, when the front app is Safari, Chrome, Arc, Edge or Brave
- the macOS version
- the display size and scale
- Light or Dark
- your locale
Anything it cannot read is left out. The note stays on your Mac.
The page address is trimmed first. The query string, the fragment and any login in the link are removed, since those often hold tokens.
Three actions
Right-click a screenshot, in the thumbnail menu or in the Library.
Copy as Markdown gives a heading and a small table:
### Checkout button does nothing
| | |
|---|---|
| App | Safari 19.0 (com.apple.Safari) |
| macOS | 26.1 |
| Display | 1512×982 @2x |
| Appearance | Dark |Copy Bug Report gives the longer template: Environment, Steps to reproduce, Expected, Actual, and the image reference. Fill in three lines and send it.
New Issue… opens a prefilled new issue in your browser, in GitHub or Linear. The title is the capture's name and the body is the bug report.
The image problem
A prefilled link cannot carry an image. So when you choose New Issue…, Frayo puts the image on your clipboard and says so. Paste it into the issue with ⌘V. It is one extra keystroke, and we could not find a way around it without uploading your screenshot to a server, which we will not do.
The copy actions help here too. They put the text and the image on the clipboard together. Paste into GitHub, Linear or Slack and you get the picture. Paste into an editor and you get the text.
Set it up
Settings → Integrations → Issue tracker. Type owner/repo for GitHub, or linear. That is all. If you leave it empty, New Issue… tells you where to set it.
Very long reports are cut to fit in the link. The template is short, so this should not bite.
Limits
- It works on screenshots, not recordings.
- The page address is read from the browser with an Apple Events request, so macOS may ask you to allow it. If you say no, the row is left out.
- The window title can be private. Check the report before you post it in public.
- Before you share a screenshot, look for the orange key badge that means Frayo found a possible secret. Redact first, then report.
Why this is useful
The best bug reports are boring and complete. This makes the boring part automatic, so you spend your time on the steps and the expected result.