Practical guide · 3 min read
Screenshot will not paste into your AI app? Find the failing step
Diagnose capture, clipboard, format, destination, and image-reading problems with one harmless file.
Find the step that failed before changing your screenshot settings.
Capture, clipboard, attachment, and the model's answer are four different steps. A black image is a different problem from a valid image that never reaches the chat. Changing the file format will not fix the wrong destination window.
Run one small test
Use a harmless image with a few colored shapes. Keep the same file while you test each step. Do not use a customer record, private conversation, or API key as the fixture.
| What happened | Check next | What the check establishes |
|---|---|---|
| No image was captured | Open the saved file, if one exists; check the capture permission and selected region | Whether the failure happened before the destination app |
| The file opens correctly but paste does nothing | Focus the destination's image-capable composer; try its file-attachment control with the same file | Whether the input can accept that file through another route |
| A filename or text appears instead of an image | Copy the image pixels from an image viewer, then paste into the composer | Whether the clipboard contains the representation that input expects |
| The image attaches to the wrong conversation | Remove it from that draft and choose the intended window and input | Whether destination selection caused the problem |
| The attachment appears but the answer misses the detail | Inspect image size, crop, legibility, and the actual question | Whether the source image contains enough legible context |
An attachment test does not need a sent message. Stop when you can see the expected image attachment in the draft, then remove it. Sending a test prompt is a separate check.
Check permissions at the failing step
Apple documents screen-capture access under Privacy & Security in System Settings. Check the app that performs the capture, rather than granting access to unrelated apps. Apple's permission guide describes the current controls.
For a baseline capture, Apple's Mac screenshot guide explains region capture and copying a capture to the clipboard. If that baseline works but an app-specific shortcut does not, record the app, version, shortcut, and visible result. You have narrowed the failure; you have not proved that every destination is compatible.
Change the format only after checking the file
Open the image in Preview. If the destination rejects that file, export a separate PNG or JPEG copy and attach the copy. Keep the original so you can compare the result. Renaming a .heic file to .png does not convert its contents.
Record whether the problem affects a file attachment, a clipboard paste, or both. A successful file upload can coexist with a failed clipboard paste. That difference is useful when you report the problem.
If you are still in LazyScreenshots onboarding, finish the walkthrough before testing automatic app switching. Onboarding skips automatic app switching.
For repeated screenshots, LazyScreenshots' capture-to-AI workflow gives you a shorter route. Check the selected app and the actual conversation before sending. If auto-paste fails, the saved image and manual attachment route let you continue while keeping the failure reproducible.
Give support something they can reproduce
Send the operating system and app versions, the input method, the image's actual format and dimensions, and the smallest nonsensitive file that fails. Describe the visible result: no attachment, wrong window, rejected file, or unreadable image. Include whether the same file worked through the attachment button. Remove the test image from unsent drafts when you finish.
Disclosure
Ali owns LazyScreenshots. That creates a conflict when he writes about LazyScreenshots or reviews competitors, so relevant pieces say so plainly. These articles are research and opinion, not independent third-party ratings.