Copy Image URL in Chrome: Every Method That Works (2026)

Right-click the image, choose Copy image address, done. That is the answer for maybe eighty percent of the times you need to copy image URL Chrome puts on the page. The other twenty percent is where people lose ten minutes: lazy-loaded placeholders, responsive srcset sets, CSS background images, canvas exports, blob URLs that die the moment you close the tab, and CDN links that return 403 the second you paste them anywhere else.

This guide covers the fast path first, then every failure mode and what to do about it. The goal is that you never again end up screenshotting an image because the URL would not copy.

The Fast Path: Copy Image Address

Chrome distinguishes between two context-menu entries that people constantly mix up:

• Copy image — puts the decoded bitmap on the clipboard. Paste it into Slack, Google Docs, Figma, or a mail client and the picture appears. There is no link, just pixels.
• Copy image address — puts the resolved src of that image element on the clipboard as text. Paste it into the address bar, a CSS file, a Markdown document, or a chat and you get a link.

When someone says they want to copy image URL Chrome is showing, they nearly always mean the second one. The wording trips people up because "address" and "URL" are the same thing here, and because Firefox calls it "Copy Image Link" while Safari calls it "Copy Image Address" too.

One useful detail: Chrome resolves the URL before copying. If the page markup contains a relative path like /assets/hero.webp, the clipboard gets the absolute https://example.com/assets/hero.webp. You do not have to reconstruct the origin yourself.

Keyboard route. There is no dedicated hotkey, because the browser has no way to know which image on the page you mean. You can get close: press Tab until focus lands on the image or its wrapping link, then press the Menu key on Windows keyboards or Shift plus F10 to open the context menu, then press the letter that is underlined for the copy entry. It works, but it is slower than the mouse for a one-off, and it fails on images that are not focusable.

Why the Copied Image URL Sometimes Does Not Work

You copy image URL Chrome handed you, paste it into a new tab, and get a 403, a 404, or a tiny grey placeholder. Four common causes:

Referer checking. Many CDNs and image hosts only serve the file when the request carries a Referer header from an allowed domain. Opening the URL directly sends no referer, so the server refuses. The image is not broken; hotlinking is blocked on purpose.

Signed URLs with expiry. Cloud storage buckets, Shopify, and most modern asset pipelines serve images through URLs with a signature and an expiry timestamp in the query string. The link works for minutes or hours, then permanently stops. If the URL you copied has parameters that look like a hash plus an Expires value, treat it as disposable.

Authenticated assets. Images behind a login — Slack uploads, private Notion pages, internal dashboards — return the login page or a 403 to anyone without a session cookie. The URL is correct; the requester is not authorized.

Content negotiation. Some servers return WebP to Chrome and JPEG to everyone else from the same URL. The link works, but the file your colleague downloads may not be the format you expected.

The practical rule: an image URL is a reference to a request, not to a file. If you need the image to survive, save the file. If you need the link to be shared, test it in an incognito window before you send it. That five-second check catches almost every one of these failures.

Lazy Loading, srcset, and the Wrong URL Problem

Modern pages rarely put a single plain URL in an img tag. Two patterns cause most of the confusion when you copy image URL Chrome has rendered.

Lazy-loaded placeholders. Many frameworks ship a tiny blurred placeholder in src and store the real image in data-src, swapping it in when the image scrolls into view. If you right-click before the swap, you copy a 20-pixel-wide blur. Fix: scroll the image fully into view, wait for it to sharpen, then copy.

Responsive srcset. An image element can declare five candidate files at different widths and let the browser pick based on viewport and pixel density. Right-click copies the one Chrome actually chose, which depends on your window size and display. On a 4K monitor you get the 2400px version; on a laptop you might get the 800px one. If you specifically need the largest available file, open DevTools, select the element, and read the full srcset list rather than trusting the context menu.

Picture elements with art direction. A picture element can serve a completely different crop on mobile than on desktop. The URL you copy is whichever source matched your current viewport. Resize the window and the answer changes.

None of this is a Chrome bug. It is the browser correctly telling you which image it is currently displaying. It just means the phrase "the image URL" is less singular than it sounds.

Using DevTools When Right-Click Is Not Enough

DevTools is the escape hatch for every case where the context menu cannot copy image URL Chrome is rendering. Four techniques worth knowing:

Inspect the element. Right-click the image, choose Inspect, and the Elements panel opens with the img node selected. Hover the src value and Chrome shows a thumbnail preview. Right-click the attribute value to copy it, or use the node context menu and pick Copy, then Copy element to get the whole tag including srcset.

Read background-image from Styles. CSS background images have no image element, which is why right-click never offers you a copy option for hero banners and decorative art. Select the element in the Elements panel, look at the Styles pane, and find the background-image declaration. The URL sits right there in the value, and Chrome renders a small preview swatch next to it. Copy the text between the parentheses.

Filter the Network panel by image. Open DevTools, switch to Network, click the Img filter, and reload the page. Every image request the page made is listed with its full URL, size, and status. This is the fastest way to find the largest asset on a page, to catch images loaded by JavaScript after render, and to see the real URL behind a redirect chain. Right-click any row and choose Copy, then Copy link address.

Check the Application panel for cached assets. If an image is served from a service worker cache, the Network panel shows it as coming from ServiceWorker rather than the network. The Application panel under Cache Storage lists the cached entries with their keys, which are the original URLs.

For a broader tour of these panels, see chrome devtools tips and tricks — the Network filters in particular pay for themselves the first time you need to find one asset on a heavy page.

Blob URLs and Data URIs: When There Is No Real Link

Sometimes you copy image URL Chrome reports and get something that starts with blob: or data:. These are not addresses on a server, and understanding the difference saves a lot of pointless retrying.

Blob URLs look like blob:https://example.com/ followed by a UUID. They point at a binary object living in the memory of that specific tab, created by JavaScript — commonly for images that were decrypted, generated, cropped client-side, or streamed. The URL is valid only inside the document that created it. Paste it into another tab and you get an error. Close the tab and the object is garbage collected. There is no way to turn a blob URL into a shareable link; you have to save the image with Save image as and upload it somewhere yourself.

Data URIs start with data:image/png;base64, followed by the entire file encoded as text. They are real and self-contained — paste one into an address bar and the image renders. But they can be hundreds of kilobytes of unbroken characters, most chat clients truncate them, and many form fields reject them by length. For small icons and inline SVGs a data URI is genuinely useful in CSS. For a photo, save the file instead.

Canvas-rendered images have no URL at all. A chart drawn on a canvas element, a map tile composited at runtime, a photo editor preview — there is no img element and no request in the Network panel. Right-click on a canvas gives you no copy option. Your options are Save image as if the site implements an export, a screenshot, or the DevTools console if you are comfortable calling the canvas export method yourself.

SVG sprites are a related edge case. If an icon is rendered from a use reference into a sprite sheet, the copyable URL is the whole sprite, not the single icon. You get all fifty icons in one file.

Copy Image URL in Chrome on Mobile

The steps to copy image URL Chrome shows on a phone start with a long-press, but the wording and reliability differ by platform.

Chrome on Android. Long-press the image. The context menu offers Open image in new tab, Download image, Copy image, and Copy image address. The last one is what you want. If the image is wrapped in a link, the menu also shows Copy link address for the destination page — two entries that look nearly identical and produce completely different results, so read carefully.

Chrome on iOS and iPadOS. Because Chrome on iOS runs on WebKit, the menu is closer to Safari. Long-press gives Save Image, Copy Image, and Open Image in New Tab. To get the URL as text, open the image in a new tab and then copy the address from the omnibox. It is an extra step but it is reliable.

The pasteboard caveat. On iOS, copying an image URL and then switching apps can trigger the paste notification banner, and some apps read the clipboard aggressively. If you are copying links to private assets, be aware of what else is reading your pasteboard.

Mobile URL handling generally is fiddlier than desktop; how to copy url on mobile chrome covers the page-level equivalents and the gestures that work across both platforms.

Image URL vs Page URL: Which One Do You Actually Need

This is the decision people get wrong most often, and it is worth being explicit about.

Send the image URL when you need the asset itself: pasting into a CSS file, an img tag, a Markdown document, an OG-image field, a design tool that accepts a remote URL, or a bug report where the exact file matters.

Send the page URL when you need context: sharing an article that happens to have a chart, pointing a colleague at a product listing, or filing a ticket about a layout problem. The page URL keeps the image alive even after the CDN rotates the asset path, and it does not break when signed URLs expire.

Send both when you are filing a visual bug. The page URL tells the reader where to look, the image URL tells them exactly which asset rendered. Two lines, no ambiguity.

In practice the page URL is what you need far more often, and it is also the one people copy the slowest — Ctrl+L to focus the address bar, Ctrl+C to copy, Escape to restore focus, three keystrokes and a lost cursor position. The Ctrl+Shift+C extension collapses that to one keystroke from anywhere on the page. It requests clipboard permission only, makes no network calls, and collects no data — which matters when the tabs you are copying from are internal dashboards. It does not touch images; it does the page URL, which is the half of the job you do fifty times a day.

For the deeper comparison of Chrome context-menu copying versus keyboard copying, see copy link address chrome.

A Practical Workflow for Collecting Images

If you are gathering reference images — moodboards, competitor research, documentation screenshots, asset audits — a repeatable process beats improvising each time.

1. Scroll the whole page first. This forces every lazy-loaded image to resolve to its real source. Do this before you copy anything.
2. Open DevTools, Network, Img filter, then reload. You now have a complete list of every image the page loaded, sorted by size if you click the column header.
3. Copy the page URL once and paste it at the top of your notes as the source of record.
4. Copy image addresses for the specific assets you need, one per line under the page URL.
5. Test one link in an incognito window. If it 403s, the whole batch is referer-protected and you should download the files instead of collecting links.
6. Download rather than link for anything that must persist. Signed URLs and CDN paths change. A file in a folder does not.

The step people skip is number five, and it is the one that saves the most rework. Discovering that every URL in a fifty-line document is dead a week later is a genuinely annoying afternoon.

Extensions and When They Help

There are extensions that add bulk image extraction — grab every image on a page, filter by dimensions, download as a zip. They are legitimately useful for asset audits and scraping product catalogs, and they save real time compared to fifty right-clicks.

They also want broad permissions. Reading every image on every page means "read your data on all websites," and image-download extensions have a poor track record on data collection. Two guardrails before installing one:

• Prefer narrow scope. An extension that runs on click rather than on every page load has a smaller blast radius.
• Check what it does with the list. Some tools upload the discovered URLs to a server for processing. That is a copy of your browsing history in a form that reads exactly like one.

For most people the built-in Chrome flow plus the DevTools Network panel covers the job without adding anything. Install a bulk tool when you are doing this weekly, not for a single project, and read the permission ask carefully before you commit to it.

Frequently Asked Questions

How do I copy an image URL in Chrome? Right-click the image and choose Copy image address. Chrome writes the fully resolved source URL of that image element to your clipboard, converting relative paths to absolute ones. Copy image, the entry directly above it, copies the pixels rather than the link.

What is the difference between Copy image and Copy image address? Copy image puts the actual bitmap on the clipboard so you can paste it into a document, a chat, or a design tool. Copy image address puts the text of the URL on the clipboard so you can paste it into a browser bar, a stylesheet, or a message. Pick based on whether the destination wants a picture or a link.

Why does the image URL I copied start with blob or data? A blob URL points at an object held in the memory of the tab that created it, so it only works inside that tab and dies when the tab closes. A data URI contains the entire image encoded as base64 text, which is valid but often too long to paste into chat or form fields. In both cases, saving the image file is the reliable path.

How do I copy the URL of a CSS background image? Right-click offers no copy option for background images because they are not image elements. Open DevTools, select the element in the Elements panel, find the background-image declaration in the Styles pane, and copy the URL from inside the parentheses. The Network panel filtered to images is a good cross-check.

How do I copy an image URL in Chrome on Android or iPhone? On Android, long-press the image and tap Copy image address. On iOS, Chrome uses the WebKit menu, so the most reliable route is Open Image in New Tab and then copy the address from the omnibox. Watch out for images wrapped in links, where the menu also offers the page URL under a similar-looking label.

Why does a copied image URL show a 403 error when opened in a new tab? The server is checking the Referer header, requiring a session cookie, or validating a signed token in the query string. The image loads inside the original page and refuses direct requests, which is deliberate hotlink protection. Download the file instead of sharing the link.

Is there a keyboard shortcut to copy an image URL in Chrome? No dedicated shortcut exists, because Chrome cannot know which image on the page you mean without a pointer or focus target. You can Tab to a focusable image, open the context menu with Shift plus F10, and select the copy entry from the keyboard, but it is slower than the mouse for a single image.

Copy the Link, Not a Screenshot

Learning to copy image URL Chrome renders is a two-second job when the page is simple and a DevTools exercise when it is not. Learn the difference between Copy image and Copy image address, scroll lazy-loaded pages before you copy, check for blob and data prefixes, and use the Network panel filtered to images whenever the context menu falls short. Test one link in incognito before you build a document around fifty of them.

For the page URL — the link you actually copy dozens of times a day — install Ctrl+Shift+C. One keystroke, no address bar round trip, free, clipboard permission only, and no data leaves your machine. Pair it with the image techniques above and you have both halves of URL copying covered.