Word is silently downsampling your images every time you save. By default — across every version of Microsoft 365 Word shipping in 2026 — inserted images are compressed to 220 pixels per inch the moment the file is written to disk. That is a deliberate choice Microsoft made on your behalf, optimised for keeping document file sizes small rather than for keeping your images looking the way you inserted them.

If your images look fine in the editor and then visibly degrade after you save and reopen the file, you are not imagining it. You are also not going to fix it by re-inserting the picture at a higher resolution. The fix lives in three specific settings that Microsoft has buried four clicks deep, and getting them right is the difference between a document that reproduces cleanly at print and a document where every photograph looks like it was emailed in 2008.

The three settings that actually matter

Go to File → Options → Advanced, then scroll down to Image Size and Quality. Everything that controls how Word handles your inserted images on save is in that one panel.

There are three controls you need to understand:

Default resolution. This dropdown is the single most important setting in the panel. It determines the maximum pixels-per-inch Word will store for inserted images. The options are 220 ppi, 150 ppi, 96 ppi, and High fidelity. The default is 220 ppi — which means any image you insert at higher resolution is downsampled to 220 ppi on save. If you want Word to keep the original image data intact, you set this to High fidelity. Nothing else gets you the original pixels back.

Do not compress images in file. A checkbox immediately below the resolution dropdown. This is the belt-and-braces option: even with High fidelity selected, certain operations can still trigger compression. Tick this box and Word is supposed to leave your images alone entirely. In practice, the High fidelity setting and this checkbox are doing nearly the same job. There is no harm in enabling both, and there is a real cost to enabling neither.

Discard editing data. This one is more subtle. When you crop or apply effects to an image in Word, Word retains the original image data so you can revert. If you tick Discard editing data, Word throws that data away on save — and once it is gone, you cannot un-crop or restore the original. This is not strictly a quality setting, but if you have ticked it and applied edits, you lose the ability to recover from compression choices later. Leave it unchecked unless you specifically need to reduce file size and you are certain you will never need to undo your edits.

The trap that catches everyone

Here is the problem nobody warns you about: these settings are per-document, not per-application.

The Choose document dropdown at the top of the Image Size and Quality panel defaults to the currently open document. Change the resolution to High fidelity and tick the boxes, click OK, and you have configured one document — the one you happened to be working on. Open a new blank document and Word will be back to 220 ppi.

To set these for new documents, you have to change the dropdown to All New Documents before adjusting anything else. The change then applies to every new document you create from that point onward. Existing documents that you open later still carry their own per-document settings, so if you inherit a file from somebody else, check the panel again with that file open.

This is the setting that, more than any other, traps people who think they have fixed the problem. They configure one document, send the file to someone else, and the recipient sees the same compression behaviour as before — because the next document they open is using its own embedded settings.

Per-image override: the Compress Pictures dialog

If you want to make a specific image immune to whatever the document-level settings do, select the image, go to the Picture Format tab, and click Compress Pictures.

The dialog gives you two genuinely useful options. First, Apply only to this picture — when unticked, the resolution choice applies to every image in the document. Second, Target output, which lets you set the resolution for this image (or all images, if the first box is unticked) independently of the document default.

Use this dialog when: you have a single high-quality image — say, a chart or technical diagram — embedded in a document where the other images can afford to be compressed. You set the document-wide default to a smaller resolution to keep the file size reasonable, then use Compress Pictures with Use document resolution unchecked on the one image that needs to stay sharp.

Do not use this dialog when: you are trying to fix a quality problem after the fact. If Word has already compressed an image on a previous save, hitting Compress Pictures will not bring the pixels back. Once the image data is gone, it is gone. Replace the image with the original file from disk.

Format-specific behaviour: not all image types compress the same way

Word’s compression engine treats different image formats differently, and the difference matters more than the documentation admits.

JPEG. This is the worst case. Word re-encodes JPEGs on compression, which means it applies lossy compression on top of whatever lossy compression was already in the source file. Every save round-trips the image through the encoder again. After three or four edits, you can see the artefacts even at normal zoom.

PNG. More resilient. PNG uses lossless compression in the source, but Word will still downsample the resolution if the default is set lower than the image’s native ppi. The compression artefacts are less visible than with JPEG, but you are still losing pixels.

HEIC, HEIF, AVIF, WebP. These are handled through Windows codec extensions, and Word’s behaviour depends on whether the extensions are properly installed. When the codecs work, Word treats these formats similarly to JPEG — re-encoding on compression. When the codecs are missing, the image fails to insert at all (see the dialog string article on the Word cannot insert the picture from the specified file error).

SVG. Vector graphics behave differently entirely. SVGs are not downsampled in the same way — they are stored as vector data internally — but they can be flattened to raster during certain operations like PDF export. Word’s SVG support also has rendering issues separate from the compression question.

The Mac problem nobody fixes

If you are working on macOS, there is a separate problem layered on top of all of the above: the Do not compress images in file setting frequently does not stick. Users report setting it, closing the document, reopening, and finding the box unchecked. Reports of this go back several years and continue to surface in Microsoft Q&A threads in 2026.

The official Microsoft response is that the setting is “document-specific, not application-wide.” That is true, but it does not explain why even per-document settings appear to revert on Mac builds. The reliable workaround is to set the resolution to High fidelity explicitly — it appears to stick more reliably than the checkbox — and to verify the setting after every save.

OneDrive AutoSave changes the game

If your document lives in OneDrive or SharePoint and AutoSave is on, you are saving constantly. The compression logic runs against newly inserted images on the next save — and with AutoSave that next save can fire within seconds of you dropping an image into the document.

This is the path that catches people who never explicitly hit Save. They insert a high-resolution image, AutoSave fires before they have had a chance to think about settings, and the compressed version is now the version on disk. The original pixels are gone. The fix is the same — configure the document-level settings before inserting the image — but the urgency is higher with AutoSave active because there is no manual save moment at which you might remember to check.

What to set them to

Pick the use case that matches yours and follow the corresponding recommendation. Do not pick the most demanding option just because it sounds safest — High fidelity on a 200-page document with embedded photos can balloon your file beyond what email and SharePoint accept.

For documents going to print. Default resolution: High fidelity. Do not compress images in file: ticked. This is the only setting that will give you reliable reproduction at print resolution.

For documents being read on screen and shared electronically. Default resolution: 220 ppi (the default). Do not compress images in file: unticked. This is the sensible balance.

For documents heading to web display, intranet pages, or quick reference. Default resolution: 150 ppi. File size matters more than image fidelity here, and 150 ppi looks essentially identical at typical screen viewing distances.

For email distribution where file size is constrained. Default resolution: 96 ppi or use the Compress Pictures dialog with email-target settings. Acknowledge upfront that you are trading quality for transmission.

The principle is to configure these settings before you insert images. Setting them after the fact does not retroactively rescue compressed pixels — Word has already discarded the original data.

When the settings still won’t hold

A handful of edge cases will defeat even the right settings:

  • Save As to a different format. Saving a .docx as .pdf goes through a completely separate export pipeline with its own quality controls. The same problem exists in PowerPoint and is worth understanding in detail — see PowerPoint image quality loss when exporting to PDF for the equivalent issue, which uses the same underlying Office export engine.
  • Copy-paste between Word and other Office apps. Pasted images sometimes inherit the source application’s compression settings rather than the destination’s. PowerPoint’s Compress Pictures decision tree covers the parallel settings on that side.
  • Templates. If you save High fidelity into a .docx but distribute it as a .dotx template, the template’s per-document settings travel with new documents created from it — which is actually the correct way to lock these settings in across a team.

For the complete cross-application picture — every setting in every Office app that affects image quality, and the relationship between them — see Microsoft 365 image quality settings: every toggle that affects it.

The honest summary

Word’s image quality defaults are wrong for anyone who cares about how their images look. They are right for Microsoft’s goal of keeping document file sizes manageable — and that is a legitimate goal, just not necessarily yours.

Three minutes in File → Options → Advanced → Image Size and Quality with the dropdown set to All New Documents fixes this permanently for every document you create from that point on. The cost is larger file sizes. The benefit is images that look the way you inserted them. For most professional work, that trade is worth making once and forgetting about.

If you have been wondering why your inserted images keep looking worse than the originals on disk: now you know. It is not your eyes, it is not your monitor, and it is not the image file. It is a 220 ppi default that Microsoft has been quietly applying for over a decade.