Google Lens ‘Copy Text’ Vanishing from Chrome? Here’s How to Fix It

If you’ve been using Chrome’s built-in Google Lens integration to grab text from a webpage, you may have hit a deeply annoying wall lately. You right-click, choose “Search this tab with Google Lens,” draw your selection perfectly — and then watch the “Copy text” and “Translate” options flash onto the screen for a split second before vanishing entirely.

You’re left staring at only “Copy as image,” which is no help when you actually need the text. You’re not imagining things, and you haven’t broken anything. This is a confirmed rendering bug affecting Chrome on desktop.

---

The Problem

The issue specifically strikes users of Chrome’s native side-panel Lens integration on desktop. The selection process works perfectly — the bug surfaces only at the final step, when the context menu attempts to render the text-recognition action buttons.

The “Copy text” and “Translate” options appear momentarily, then disappear, leaving the menu incomplete. It’s repeatable, frustrating, and blocks a genuinely useful workflow.

---

Why It’s Happening

The root cause is a rendering conflict between Chrome’s hardware acceleration compositor pipeline and the Google Lens web overlay UI container. In plain terms: the part of Chrome responsible for drawing frames on your screen is racing against the part that needs to attach OCR (text-recognition) data to the menu buttons.

Chrome loses that race. Before the text layers have a chance to bind properly, the viewport refreshes and discards the context-dependent buttons. The result is a menu that looks broken — because, briefly, it is.

The good news is that this is a Google-side rendering issue, and several workarounds can sidestep the conflict entirely while you wait for an official patch.

---

How to Fix It: Step-by-Step Workarounds

Step 1: Disable Hardware Acceleration

Since the bug lives in the GPU compositor pipeline, the most direct fix is to remove that pipeline from the equation entirely. This forces Chrome to use software rendering instead, which resolves the timing conflict.

1. Open Chrome and click the three-dot menu (⋮) in the top-right corner.
2. Go to Settings and scroll down to the System section.
3. Toggle off “Use hardware acceleration when available.”
4. Click the “Relaunch” button that appears to restart Chrome.
5. Try the Google Lens selection again and check whether “Copy text” and “Translate” now stay visible.

Note: Disabling hardware acceleration may make Chrome feel slightly less smooth during scrolling or video playback on some machines. If performance suffers noticeably, re-enable it and try the next steps instead.

Step 2: Test in an Incognito Window

If the hardware acceleration toggle doesn’t resolve it, a browser extension may be the culprit. Ad blockers, text-manipulation tools, and certain privacy extensions are known to interfere with overlay UI injection — which is exactly how the Lens context menu renders its buttons.

1. Press Ctrl + Shift + N (Windows/Linux) or ⌘ + Shift + N (Mac) to open a new Incognito window. Extensions are disabled by default in Incognito.
2. Navigate to the same webpage where you experienced the bug.
3. Right-click and trigger “Search this tab with Google Lens” again.
4. If “Copy text” and “Translate” appear and stay put, an extension is to blame.
5. Go to chrome://extensions, disable your extensions one by one, and retest in a normal window to identify the offending one.

Common suspects: uBlock Origin, Grammarly, and browser-level text-selection modifiers are frequent causes of overlay injection conflicts. Try disabling these first.

Step 3: Reset Chrome’s Layout Cache

If neither of the above steps works, Chrome may be holding onto a corrupted temporary overlay layout from a previous session. A settings reset clears these cached files and restores Chrome’s UI rendering to a clean state.

1. Open Chrome and go to Settings.
2. In the left sidebar, click “Reset settings.”
3. Select “Restore settings to their original defaults.”
4. Read the confirmation dialog — this will reset your startup page, new tab page, search engine, and pinned tabs, but it will not delete your history, bookmarks, or saved passwords.
5. Click “Reset settings” to confirm, then relaunch Chrome and test the Lens overlay again.

Good to know: This reset specifically targets corrupt configuration and UI state files. Your browsing data stays completely intact.

---

Need the Text Right Now? Use This Instant Workaround

If none of the above steps resolve the issue immediately — or if you simply need to extract text urgently — there’s a seamless bypass available right now.

1. In the broken Lens overlay, choose “Copy as image” (the option that does stay visible).
2. Open a new tab and navigate to lens.google.com — the standalone Google Lens web app.
3. Paste the image directly into the interface (Ctrl + V / ⌘ + V).
4. Lens will process it and give you full text extraction and translation options without any of the Chrome overlay rendering issues.

It adds one extra step, but it’s fast, reliable, and completely sidesteps the compositor bug entirely.

---

Wrapping Up

Rendering bugs like this one are an unfortunate side effect of how tightly modern browsers integrate first-party AI tools with a deeply complex GPU pipeline. The interaction between the compositor and the overlay UI is a genuinely tricky boundary to get right across every combination of hardware and OS.

The workarounds above — particularly disabling hardware acceleration or running in Incognito — resolve the issue for the vast majority of affected users. Google is aware of compositor-layer conflicts with Lens overlays, and a layout patch addressing the root cause is expected in an upcoming Chrome stable update.

In the meantime, lens.google.com is your trusty backup. If one of these steps fixed it for you, drop a note in the comments below — and if you’re still seeing the bug after trying everything, let us know your Chrome version and OS so we can dig deeper.