What does this error mean?
Show Scrny.
Screenshot any cryptic error — Windows blue screen, macOS dialog, browser console, package-install failure — and Scrny tells you what it means and the first three things to try. Plain English, in seconds.
Eight kinds of error. One shortcut to a fix.
Each tile below is a real-world error type Scrny's vision engine recognises in plain screenshots — system dialogs, terminal traces, browser console, install logs.
One screenshot in. A plan out.
Same flow you'd expect at the command line — read the dialog, translate the code, rank the fixes by what's most likely to work first.
Three fixes, ranked by likelihood.
Scrny doesn't hand back one possibility — it hands back the top three, ordered cheapest-and-most-likely first, so you don't reinstall your OS before checking the obvious.
Toggle your VPN off and retry the site.
- Open your VPN client and click Disconnect.
- Reload the page in your browser.
- If the page loads, the VPN's DNS was the issue.
Didn't help? Try fix #2 — flush DNS cache.
Flush the DNS resolver cache.
- macOS:
sudo dscacheutil -flushcache - Windows:
ipconfig /flushdns - Reload the page; the resolver will re-query.
Still broken? Try fix #3 — switch DNS resolver.
Switch your network's DNS resolver.
- Open System Network settings → DNS.
- Add 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google).
- Reload the page; resolver queries are routed through them now.
None of these worked? Re-screenshot — there might be more context.
Same error in. Four very different responses out.
Each panel below is what you'd actually see if you brought the same DNS error to that tool. The structural differences matter more than the feature checklist.
Not the right tool? Try another mode.
Scrny ships four modes, each tuned for a different shape of question. Use the one that matches what's on your screen.
Stop googling error codes.
Show them to Scrny.
Questions, answered.
Can Scrny tell me what this error message means? +
Yes — that's exactly what Tech Support mode does. Screenshot any error dialog, console output, or trace and Scrny reads the whole block, translates it into plain English, and gives you the first three things to try. No copy-pasting cryptic codes into a search bar.
Does it work on Windows / macOS / Linux errors? +
All three plus Android and iOS. Vision Engine reads OS dialogs, kernel panics, blue screens, system service crashes — anything visible on your screen. Platform-specific error codes (Windows HRESULT, macOS NSError, Linux exit codes) all get explained with the convention they came from.
What about browser console errors and stack traces? +
Scrny reads DevTools console output verbatim — JavaScript exceptions, CORS / CSP / TLS warnings, network panel 5xx errors, the works. Stack traces are read with file paths and line numbers preserved, so the suggested fix can point at the right call site rather than a vague "check your code".
How is this different from pasting the error into ChatGPT? +
Three things: (1) screenshot input means you don't lose formatting — error codes, line numbers, surrounding context all come through together; (2) responses are structured as "what it means + first three fixes" instead of a conversational paragraph you have to parse; (3) it's faster — P50 2.4 seconds vs ChatGPT's typical 10-20 seconds for a thoughtful answer.
Does it actually suggest a fix or just explain? +
Both. Every Tech Support response is structured: a one-line plain-English explanation of what the error means, then three concrete fixes in priority order — cheapest first. So you try the 30-second fix before reinstalling anything.
Will it leak my screenshot anywhere? +
No. Screenshots are sent to Scrny's vision pipeline, used to generate the answer, and not retained beyond the active session. We don't train models on customer screenshots and we don't index them anywhere searchable.