Copy text from screen when an app blocks selection

To copy text on screen when the app will not let you select it, press the capture shortcut, drag a region over the words and press Copy. Lass0 reads the pixels on your device and puts the text on your clipboard as plain text, rich text, Markdown or a layout view. The app's selection rules do not decide the result. You still need to check the output, because the reading is only as good as the words on screen.

This guide covers why some text cannot be selected, how to set up the macOS permission, what the capture keeps, a worked example from Lass0's own samples, and how to check copied text before you paste it. The product page for this topic covers the feature side.

Unselectable text has a few causes

Selection fails in a few common places. Some apps draw their text rather than placing it in a field the clipboard can read. Error dialogues, installers and licence screens can all work this way. A video frame or a game may show words that no text field holds at all. In each case the words are visible even though the clipboard has nothing to offer, so the route is to read the displayed region rather than the underlying text.

The same idea lets you copy any text on screen that you can see. The capture does not need the app to cooperate. It needs the region to be displayed on your machine, and it needs the text to be large enough for the reading to be useful.

Remote desktop text: check the clipboard route

Remote desktop windows are a special case. The words are on your screen, but the remote session may not share its clipboard with your computer. Microsoft's documentation shows how that happens. For Azure Virtual Desktop, clipboard redirection between the remote session and the local device is disabled by default for newly created host pools, and where settings disagree, the most restrictive one applies. Microsoft Learn's guide to clipboard redirection sets out the configuration options.

A remote window can therefore be readable on your screen while ordinary copy and paste fails. Screen capture reads what is displayed on your own machine, so the remote clipboard setting does not stop it. A window that is minimised is not displayed, though, so bring it back on screen before you drag. Test the route on a harmless window before you depend on it for work.

Copy text from screen mac: set the permission first

On a Mac, macOS will not let an app read the screen until you allow it. Apple's Mac User Guide puts the control under Privacy and Security, in the list for screen and system audio recording, where each app has its own on or off switch. Apple's guide to controlling screen and system audio recording sets out the steps.

Lass0's documentation gives the same route in shorter form: Privacy and Security, then Screen Recording. If the permission is off, the selection overlay shows “Screen recording is off” with a button to open System Settings. After you turn Lass0 on, quit and reopen it. Do this before a real task, not during one. Then test with a sentence you already know, so you are not learning the setup while someone is waiting for the text.

What the capture keeps

The image is read on the device and is not kept. The local timeline keeps the extracted text and its structure, as the offline OCR guide explains. Screen OCR does not change that, but the text can still be sensitive. An error dialogue may show an account name, a file path or a token, and the reading cannot tell which words matter. Treat the timeline as a local record of your work, and remove captures you no longer need.

A worked example from Lass0's own samples

Lass0's example captures were recorded on a Mac on 13 October 2026, using the on-device model qwen3-4b-instruct-2507 (build q4_k_m-1). Two are useful here: a storage warning dialogue and a short code block in a rendered page. The table lists what each one recorded and what a reviewer should check. Both outputs were compared with their source images.

Table: each sample's recorded counts and what a reviewer should check. The counts are the product's own metadata, not a benchmark.

The storage dialogue came through as the source shows, so only its figures need a glance. The code block is the warning case. Its text reads well at a glance, yet the brackets are the parts a programmer needs most, and two of them are missing. Paste code into an editor and count the brackets before you trust it. Keep the source open beside the paste whenever the text matters.

A different machine or a different model version may give a different result, so record the version you used with each test. The sample shows that a clean-looking result can still hide a broken character, which is why the check matters more than the speed of the first paste.

Copy error message text, then check the codes

Error messages are the most common reason to copy from a screen, and they carry the details support teams need: codes, file names and numbers. Lass0 aims to keep those exact, and the storage sample kept its figures intact. Even so, check codes character by character. Zero and the capital letter O look alike, as do the digit one and a lower-case l.

Capture the message while it is still on screen, because a dialogue that closes cannot be read again. Then look for anything that should not leave your machine. An error may print a path, an account name or a token. Follow the steps in how to remove secrets from text before you paste it into a ticket or a chat.

Improve a poor capture

Tesseract, an open source recognition engine, says it works best on images at 300 dpi or more, and that it may be beneficial to resize images that fall short (Tesseract's image quality guide). Small text on screen may fall below that level, so start with the app itself. Zoom in before you capture, include the whole line rather than cutting words at the edge of the region, and capture again at a larger size if the first result looks wrong.

A clean capture makes the review faster than correcting the output by eye. The OCR quality checks guide explains how to compare the output with the source.

When the text can be selected

If you can select the words, use the clipboard. It is faster, and it skips the recognition step. A PDF with a text layer is a common case, and the copy text from PDF guide covers broken lines and scanned pages. An image someone sent you is different: open it on screen and capture the region. If you need headings and tables kept, the screenshot to Markdown guide covers that output.

Choose the output before you copy

Copying from a screen gives you text, and the format decides how much structure survives. Plain text suits a single error message. Markdown suits a block that should stay a code block or a list. The layout view keeps spacing when alignment matters, and rich text helps when the destination accepts formatting. Choose the format that matches where the text is going, not the one you used last time.

A short test before you need it

Choose a harmless window and test the whole route. Capture a sentence you already know, paste it into a plain editor and compare the words. Then repeat the test in your remote session, because a remote window may behave differently from a local one. Before you copy text from my screen for work, note the app version and the output format you used. If the result matches, the setup works for that kind of text. If it does not, record the exact message and the step that failed, so the fault is clear to whoever fixes it.

Selection is one way to get text off a screen, not the only way. Capturing what is displayed lets you copy the words you can see. The review step decides whether those words are correct and safe to paste, and that review matters more than how quickly the first paste arrives.

Questions, answered

Can Lass0 copy text from a remote desktop?

If the remote window is on your screen, Lass0 can read it, because it reads what is displayed. The capture runs on your own device, so the remote session's clipboard settings do not decide whether the capture works. Ordinary copy and paste between the remote session and your computer is a separate route, so test it on its own.

Why does macOS ask for screen recording permission?

macOS lets an app read the screen only after you allow it. Turn Lass0 on under Privacy and Security, then Screen Recording, and quit and reopen Lass0. If the permission is off, the selection overlay says so and offers a button to open System Settings.

Is the captured image saved?

No. Lass0 reads the pixels in memory and does not keep the image. Its local timeline keeps the extracted text and its structure, and you choose how long that history stays.

What should I check in copied text?

Check numbers, codes, brackets and punctuation against the source before you paste. Small symbols are the easiest to misread. If the text is small on screen, zoom the app and capture again.