How to Debug an Error from a Screenshot on Mac

When something breaks on your Mac, the error message is usually the last place you want to look — a cryptic string that tells you what failed but not why, and never what to do about it. The fastest way to get unstuck is to stop reading it and start asking: screenshot the dialog, then let an AI model like Claude read it for you.

Why screenshot the error instead of retyping it

A screenshot captures more than the dialog — it includes the whole screen around it, which is usually the context that explains the problem. The app window, the state of the document, the menu bar. Reconstructing that in a search box means typing a partial string and hoping. Pasted into an AI, the whole picture is right there.

• Plain-English explanation of what the error actually means.
• Likely cause based on the visible context.
• Step-by-step fix, and whether it’s safe to retry.

Method 1: capture, then paste into an AI chat

Press ⌘⇧4 to select the error, then attach it to Claude (the app or claude.ai) and ask “what does this error mean and how do I fix it?”. Works with any app.

Method 2: debug while you capture, inside iShot

In iShot, take the screenshot and hit the AI action. The shot goes straight to an Anthropic Claude model and the answer streams back — no app switching. You bring your own Claude API key or an OpenAI-compatible endpoint, so the image goes only to the provider you choose.

Prompts that get a useful answer

• Explain — “in plain English, what is this error?”
• Fix it — “what are the concrete steps to resolve this?”
• Is it safe? — “is it okay to retry, or will I lose work?”
• Foundational — “is this a known issue with the app or OS?”

Frequently asked questions

Can AI read an error message from a screenshot?

Yes. Vision models like Claude can read text and context from an image, so you can paste a screenshot of an error and get an explanation and fix without typing the message.

Is it safe to share an error screenshot with an AI?

Avoid screenshots that contain passwords or sensitive data. In tools like iShot you set the provider yourself, so the image goes only to the model endpoint you configure and you see the billing on your own account.