How to reduce DWG file size

Step 1 — PURGE unused named objects

Start with PURGE, the single biggest win for most files. Type PURGE to open the dialog, tick 'Purge nested items' and the option to purge registered applications, and purge repeatedly until nothing is left to remove. PURGE deletes unused blocks, layers, linetypes, text styles, dimension styles and more — definitions that sit in the file taking up space even though nothing references them.

Unused block definitions are usually the heaviest offenders, especially in drawings that have had many blocks inserted and deleted over time. The deleted insertions leave their definitions behind, and only PURGE clears them. Run it more than once, because purging one item can free another to be purged.

Step 2 — OVERKILL duplicate geometry

Duplicate objects — lines drawn exactly on top of each other — inflate the entity count invisibly. Run OVERKILL, select all (ALL then Enter), and at tolerance 0 with default settings let it delete the true duplicates. The command reports how many it removed, and the file usually shrinks on the next save.

Duplicates accumulate from repeated copy-paste, exploded blocks and merged drawings. Clearing them not only reduces size but fixes hatches and area measurements that the duplicate boundaries were breaking. Keep the tolerance at 0 for a whole-drawing pass so you do not accidentally remove close-but-distinct geometry.

Step 3 — AUDIT to clean the database

Run AUDIT and answer Yes to fix errors. A drawing carrying database errors can hold onto bloat and behave unpredictably; AUDIT repairs broken handles and references, which sometimes frees space and always leaves the file structurally sound for the steps that follow.

Think of AUDIT as the structural pass between the content-cleaning of PURGE/OVERKILL and the final rewrite. It rarely produces the biggest size drop on its own, but it ensures the other steps are working on a healthy file rather than fighting corruption.

Step 4 — Manage embedded images and PDFs

Raster images and PDFs are a frequent hidden cause of huge files, especially if they were embedded rather than referenced. A single high-resolution scan can dwarf the vector geometry. Open the External References palette (XREF) and check what image and PDF underlays are attached, and at what resolution.

Where possible, reference images and PDFs externally rather than embedding them, so their weight lives outside the DWG. If an image is embedded and no longer needed, remove it. If you need it but it is overscaled, a lower-resolution copy of the raster will cut the file size sharply while staying perfectly legible at drawing scale.

Step 5 — WBLOCK the whole drawing to a fresh file

After purging, overkilling and auditing, the most effective single move on a stubborn file is to rewrite it from scratch. Run WBLOCK, choose 'Entire drawing' as the source, and save to a new filename. Writing the whole drawing out builds a brand-new DWG that contains only referenced, live data — it sheds orphaned and fragmented internal structures that even PURGE cannot reach.

The new file is frequently much smaller than the original for identical visible content. This 'wblock to a fresh file' trick is the professional's last resort for bloat and often the most dramatic, turning a sluggish multi-megabyte drawing into a lean one in a single operation.

Habits that keep files small

Prevention beats cleanup. Purge before issuing or archiving any drawing, so files leave your hands lean. Reference base plans and images as xrefs and image attachments rather than copying or embedding them, which keeps weight outside the host file. Avoid exploding blocks needlessly, since exploding multiplies entity counts and seeds duplicates.

Keep your reusable symbol library tight — each block wblocked clean, audited and purged — so the components you insert never drag bloat into a host drawing. A drawing built from lean, well-made blocks and live references stays small naturally, and the cleanup routine above becomes an occasional tune-up rather than a regular rescue.

One more habit worth forming is checking file size as you work, not just at the end. If a drawing suddenly jumps in size after a particular operation — pasting in another file, embedding an image, exploding a large block — you know exactly what caused the bloat and can address it immediately while the cause is fresh. Catching weight early, at the moment it enters the file, is far easier than hunting through a finished drawing for whatever made it heavy.