Reduce PSD file size without losing layers
Need a smaller PSD without flattening or exporting? Most methods destroy something. This page compares them, and the tool below is the one that costs nothing.
There are two different problems hiding behind “my PSD is too big”. Either the file carries real pixel data that genuinely costs bytes, or it carries junk metadata that Photoshop accumulates with every paste and every save. The second problem is more common than most designers expect, and it is the only one you can fix for free without changing a single pixel.
Start with the tool below. If the “Saved” number is large, you are done. If it is near zero, scroll down to the comparison of lossy methods.
Every way to shrink a PSD, compared
| Method | Typical saving | What you lose | When to use it |
|---|---|---|---|
| Strip DocumentAncestors metadata (this tool) | 0% to 99%, depending on history | Nothing. Layers, masks and pixels are byte-identical. | Always first. It is free and reversible in the sense that nothing visible changes. |
| Turn off Maximize Compatibility | 10% to 40% | Flattened preview. Lightroom refuses to import such files, and Bridge and some older apps show no thumbnail. | Working files that only Photoshop opens. |
| 16-bit to 8-bit | About 50% | Colour precision. Visible only in heavy gradient grading. | Web and UI work, most illustration. |
| Link smart objects instead of embedding | Up to the size of the embedded originals | Portability. The PSD now depends on external files. | Large placed photos or RAW files. |
| Rasterize smart objects | Large | Non-destructive editing of that object. | Objects that are final. |
| Merge or flatten layers | Large | All editability of the merged layers. | Final deliverables only, and keep the layered master. |
| Lower resolution or crop | Proportional to pixel count | Detail. Irreversible. | When the document is oversized for its destination. |
| Export to JPG or PNG | 90% or more | Every layer. | Only for previews, never as the master. |
| ZIP the file | 5% to 20% | Nothing, but the recipient must unzip. | Sending a file that is already lean. |
Why the metadata method comes first
Every other row in the table trades something away. Metadata stripping does not, because
the field it removes is a history log that nothing reads. Photoshop writes a new
identifier into photoshop:DocumentAncestors each time content is placed or
pasted from another document, and it never deletes old ones. Each embedded smart object
also keeps its own copy of the list. On our test file that history was 648 MB of a 902 MB
document.
The tool reads the file, copies every section through unchanged, and rewrites only the XMP packet of the main document and of each embedded smart object with the ancestor list removed. Section lengths are recalculated so the result is a valid file. Because nothing else is touched, the output is deterministic: the same input always produces the same output.
What gets removed
photoshop:DocumentAncestors, the list of every document this file has ever borrowed content fromrdf:Bagandrdf:li, the RDF wrappers around each ancestor entry- The same structure inside every embedded smart object, recursively
Image pixel data, layer structure, smart objects, ICC profiles, guides, slices, and every other XMP field such as author, copyright and camera data are preserved. The output is a normal PSD that Photoshop opens identically to the original.
Doing it inside Photoshop instead
If you would rather stay inside Adobe’s tools, the community-maintained fix is an
ExtendScript that calls XMPMeta.deleteProperty on the ancestors field and
saves the file. It works, with three limitations: it needs Photoshop open, it processes
one file per run unless you wrap it in a Bridge batch, and it does not descend into
embedded smart objects, so files like our test case keep most of their bloat. ExifTool
can also remove the field, but it rewrites the whole file and is noticeably slower on
gigabyte documents.
Drop a PSD above to see the size reduction on your file. No upload, no signup.
Real numbers: before and after
The first row is a file we measured with this exact engine. It took 1.4 seconds on a laptop. The other rows are cases reported by Photoshop users on Adobe’s forums after removing the same metadata field.
| File | Before | After | Saved |
|---|---|---|---|
| Game art, 1920×1080, RGB 8-bit, many smart objects | 902 MB | 254 MB | 71.8% |
| Retouched photo passed between editors (Adobe Community) | 65 MB | 110 KB | 99.8% |
| Reused PSD template, images placed repeatedly (Adobe Community) | 100 MB | 7 MB | 93% |
Your result depends entirely on how much ancestor history the file carries. A PSD created in one sitting and saved once may shrink by only a few kilobytes. A file that has been a template for two years can lose most of its size.
Step by step
- Open the tool. Open psd.imtool.app in any modern desktop browser. Nothing to install.
- Drop the file. Drag the .psd or .psb file onto the drop zone, or click it to pick a file. The file stays on your device.
- Wait a few seconds. The engine reads the file in a Web Worker and removes the DocumentAncestors metadata from the main document and every embedded smart object.
- Download. Compare the before and after sizes, then download the cleaned copy. The original is untouched.
FAQ
How much can I actually save?
It depends on how bloated your XMP block is. Our own test file went from 902 MB to 254 MB. Files that have been passed between many designers or used as templates shrink the most. A file created fresh in one session may not change at all, because there is no ancestor history to remove.
Does it work with .psb files?
Yes. The engine handles both .psd and .psb (Large Document Format) using 64-bit offsets internally.
Will Photoshop still open the result?
Yes. The output is a standard PSD/PSB file. Photoshop opens it exactly as the original, just without the extra metadata. Affinity Photo, GIMP, Krita and Figma import open it too.
Why not just use Save As?
Save As keeps the same metadata. Even Photoshop’s own “Save a Copy” does not remove DocumentAncestors. You need to strip that data explicitly.
Is there a way to reduce a PSD that has no metadata bloat?
Yes, but each option costs something: switch from 16-bit to 8-bit, rasterize or link smart objects, merge finished layer groups, lower resolution, or turn off Maximize Compatibility. The table on this page lists what each one loses.
Can I run this on many files at once?
The browser tool handles one file at a time. For folders, the same engine is available as an open-source command-line utility, psd_ockham, which processes a whole directory.