When a website will not let you save an image

You right-click a picture on a website and the menu that opens has no Save Image option, or the option is there and the file it produces is a single grey pixel. Sometimes dragging the image to the desktop does nothing at all, as though it were never really an image in the first place. This is one of the more confusing small frustrations on the web, because the picture is clearly right there, visible, loaded, sitting on the page. The reason it will not save is almost always technical rather than sinister, and once you know which of four things is happening, the fix is usually quick.

Before any of that: a saved image is still someone else's work. Nothing below is about getting around a site that has deliberately made its images hard to take. If a business has gone out of its way to block saving, the honest response is to respect that rather than route around it, the same way you would leave a locked door alone rather than pick it. What follows is for the ordinary case: keeping something for your own reference, a mood board, a repair manual you need to remember, a room you liked the look of.

Why does right-click offer nothing at all?

The single most common cause is that the picture is not an image element on the page. It is a CSS background, painted onto a div the same way a wall gets painted, rather than an img tag sitting in the page's content. A browser's right-click menu only offers to save an image when it recognises an actual image element under the cursor, so a background image gets the ordinary page menu instead, the one with Back and Reload on it, because as far as the browser is concerned there is no picture there to save.

You can usually still get it. Right-click the picture and choose Inspect (or Inspect Element), which opens the browser's developer tools. Look for a line reading background-image: url(...) in the styles panel on the right, click the small colour swatch or thumbnail next to it, and most browsers will show you the image and let you open it in a new tab, from where a normal right-click and Save Image works. It looks technical the first time and takes about ten seconds once you have done it once.

The image is a canvas or an SVG, not a picture file

Some of what looks like a photograph on a page is not stored as a photograph at all. A canvas element is a blank rectangle that JavaScript draws pixels onto after the page loads, the way a chart library draws a graph. An SVG is a set of drawing instructions, lines and shapes and fills, rather than a grid of pixels. Right-click a canvas and you will often see Save Image As anyway, because the browser treats whatever is currently drawn on it as a picture, but the result can be lower quality than what you are looking at, since some canvases redraw at a different resolution than they display. An SVG usually will not offer a save option at all, because it is not raster image data. The developer tools trick above works here too: find the <svg> or <canvas> element, and for an SVG you can copy its outer HTML and save it as a .svg file directly.

Has the image not actually loaded yet?

Lazy loading delays an image until you scroll near it, which is good for the site's speed and bad for anyone trying to save the picture the moment the page opens. What is visible on screen at that point can be a low-resolution placeholder, a blurred stand-in, or nothing at all until the real file arrives a moment later. Right-clicking too early saves the placeholder, not the picture. Scroll the image fully into view, wait a second or two for it to sharpen, and try again. If the site uses infinite scroll or loads images only when a thumbnail is clicked into a larger view, open that larger view first.

A transparent layer is sitting on top of it

Some sites put an invisible element directly over an image, sized to match it exactly, so that a right-click lands on the overlay instead of the picture underneath. The overlay might carry no content of its own, just enough to intercept the click. This is usually a deliberate choice by the site rather than an accident, and it is worth pausing on that distinction. If a business has built a layer specifically to stop casual saving, whether to protect a photographer's work, a paywalled preview, or a print sale, that is a decision they are entitled to make about content they made or licensed. The honest response is not to defeat it. Screenshot the page instead, described below, or move on.

What actually works every time: take a screenshot

Whatever is happening underneath, a screenshot captures what your screen is already showing, and no CSS trick, canvas, lazy-load delay or overlay can stop that, because it never touches the page's code at all. It is also the most respectful option on this list: you are keeping a picture of what you saw, at the quality your screen displayed it, rather than reaching past whatever the site put in place. On a Mac, four shortcuts cover every situation.

1. Shift-Command-4 turns the pointer into a crosshair. Drag across just the picture and release, and macOS saves a file of exactly that area to the desktop.
2. Shift-Command-4, then tap the Space bar turns the crosshair into a camera. Move it over the browser window and click, and macOS captures that whole window, complete with its drop shadow, without you needing to select an exact rectangle by hand.
3. Shift-Command-5 opens the Screenshot app's own toolbar, with buttons for the whole screen, a window, or a selected portion, plus an Options menu for where the file saves and whether a timer runs first. Useful when you want to see the choices laid out rather than remember a shortcut.
4. Add Control to any of the above (for example Control-Shift-Command-4) and macOS copies the screenshot straight to the clipboard instead of saving a file to the desktop, ready to paste directly into another app.

Apple documents all four in its own guide to taking a screenshot on Mac, including the Control modifier for copying instead of saving.

Be honest with yourself about the trade-off. A screenshot is a lower-quality copy: it captures your screen's resolution, not the original file, so it will look softer if you ever zoom in close, and it carries none of the original image's metadata. For a reference you are keeping to remember a look, a layout or a colour, that loss barely matters. For something you needed at full print resolution, it is a real limitation, and no amount of screenshotting fixes that. In that case the honest options are asking the site or the person who posted it directly, or accepting that the image is not available to you at that quality.

Whatever route you use, save the source with it

An image on its own, saved by any of the methods above, starts losing its value the moment you forget where it came from. You will remember the room, the colour, the layout, but not whose it was or which site had it, and a picture you cannot credit or find again is a much smaller thing than the one you meant to keep. Copyright does not care how an image reached your desktop: a screenshot, a saved file and a downloaded original are all still someone else's work, held for your own private reference rather than published anywhere. Keeping the source link alongside the image is not a formality. It protects you if anyone ever asks where it came from, and it protects the person who made it, because you still have a way back to them.

This is the same discipline worth building around anything saved from someone else's work, covered in more detail in how to keep the posts you save on Instagram. Muse keeps a note field next to every image for exactly this, the link and a line about where something came from, sitting right beside the picture rather than in a separate tab you will never reopen.