You can't copy an image out of Google Docs
Copy the image. Paste it into chat, into Miro, into a tweet. Nothing arrives. So you paste it into Notes, drag that to the Desktop, find the file, and upload it — four steps to move a picture two centimetres.
Facts cited
| Google Docs monthly users | 1 billion | Workspace statistics, 2026 |
|---|---|---|
| Google Workspace users overall | 3 billion+ | Google, 2025 |
| Global life expectancy | 73 years | World Bank, 2023 |
Assumptions low → high
| What we can't measure | low | likely | high |
|---|---|---|---|
| Docs users who ever try to copy an image out | 10% | 20% | 40% |
| Times per year they do it | 3 | 6 | 20 |
| Seconds lost to the workaround ritualCopy → paste into a second app → drag out as a file → locate it → upload. Against ~3s for a copy-paste that worked. | 20s | 40s | 90s |
Who can fix it
- Owner
- Google (Docs clipboard / editor)
- Channel
- Google Docs Help Community · Workspace feedback
There’s an image in a Google Doc. You want it in a chat message. The obvious move — copy, paste — produces nothing useful at the other end. So you perform the ritual instead:
- Copy the image in Docs
- Paste it into some other app that will accept it — Notes, Preview, a scratch document
- Drag it from there onto the Desktop to get a real file
- Find that file and upload it
Four steps, two intermediary apps, and a stray file left on your Desktop — to move a picture from one window to another.
Why it happens
The clipboard is multi-format by design. When you copy, an app can publish the same content in
several representations at once — rich text and plain text, or an internal object and a plain
image/png bitmap — and each receiving app takes whichever flavour it understands. That’s how
copy-paste manages to work at all between unrelated programs.
Google Docs publishes its own internal representation, which only Docs and a few Google surfaces know how to read. Anything else — Slack, a chat box, Miro, a tweet — looks at the clipboard, finds no format it recognises, and gets nothing. Docs already has the image bytes. It simply doesn’t offer them in a form the rest of the computer speaks.
The math
1B Docs users × 20% × 6 times/yr × 40s = ~20 lifetimes / year
The fix
Put a standard bitmap on the clipboard alongside the private format. One extra flavour, published at copy time, and every one of those four steps collapses back into paste. The receiving app doesn’t need to know anything about Google Docs — that’s exactly the point of a multi-format clipboard.
The principle: the clipboard is an interop surface, not a private channel. If you put something on it, include at least one representation the rest of the world can read. An app that only speaks to itself on a shared bus is a walled garden inside a system designed for exchange.
Estimates. The Docs and Workspace user counts are cited; the share of users who attempt an image copy and how often are reasoned figures. Behaviour also varies by browser, OS and destination app — some combinations do carry the image through — so the per-target matrix should be tested before naming any specific pairing as broken. The confident claim is the pattern: an internal-only clipboard format.
Also worth noting Docs offers escape hatches (right-click → save to Keep, or File → Download as a web page to extract images). They confirm the bytes are right there; they just aren’t on the clipboard.
Difficulty to fix: easy
The image is on your screen. You pressed copy. The bytes exist. Everything needed for this to work is already in memory — the only thing missing is a format anyone else can read.
Read this case's source — _cases/015-google-docs-image-copy.md