Drop 20 Pounds with InDesign


This article originally appeared in InDesign Magazine #39, December 2010/January 2011. Subscribe now!
Cruft: Something unpleasant that accumulates over time. Unproductive, wasteful, doesn’t add value, obsolete, redundant.
InDesign documents can get needlessly heavy, slowly accumulating visible and invisible cruft as you work on them. The longer the document, and the longer you work on it, the more likely it is to become crufty and laden with excess. While there is nothing inherently bad about these files, we believe that they can lead to corruption (where the documents can “go bad”), confusion (where you may lose track of what’s in your documents and how you created them), and a general slow-down of productivity.
Similarly, the files you print or export (such as PDFs and SWFs) may be far larger than they need to be, leading to long upload/download times, print times, and frustrated viewers. Fortunately, you can reduce the file sizes of both your InDesign documents and the files you export in some simple ways.
Click the image below to read the article as a PDF, or continue to read the article as HTML:

What Makes an INDD
Let’s start by taking a look at what makes up an InDesign file. InDesign files are technically database files, which enables InDesign to do a lot of clever things, like unlimited undos and crash recovery. However, all databases have a certain amount of overhead—like an infrastructure that takes up room all by itself.
If you create a new blank document and save it without making any changes, it will be about 1 MB. That’s without any content, just the basic document structure made up of the four S’s: spreads, styles, swatches, and settings. The majority of that is the document’s ICC CMYK profile, which takes up about 700K.
Then, as you work with the document, you’ll see the file size grow each time you save it. This makes sense: As you add text, place graphics, and create new objects, you’re adding information that has to be housed in the file. But what may not make as much sense is that when you remove content from the file, it does not shrink in size.
You can try this little experiment in cruft-creation yourself. Create an empty document. Save and note the file size. Now place a photo. Again save and note the file size. Now delete the photo. Although the document appears to be back to its original, empty state, if you save and check the file size you’ll see it’s just as big (actually slightly bigger) than when the photo was placed in the file! What gives? The ghost of the photo still haunts the file, lurking in the digital darkness! What you deleted was the rectangle that contained the photo. So it no longer appears on the page. But all the other information regarding that photo, including the proxy image and XMP metadata is apparently still there. That, dear friends, is cruft.
The worst thing you can do in terms of creating cruft is to copy and paste (or drag and drop) raster image content directly from Photoshop or a Web browser. You can instantly supersize an InDesign file by doing this. If you open a JPEG from your 10-megapixel camera in Photoshop, copy the whole thing with the selection tool, and paste the pixels into InDesign, that document immediately swells by 32 MB, which won’t disappear even if you delete the picture!
One file we worked with was 95 MB large, due to five images that had been pasted in from Photoshop (Figure 1). Deleting the images didn’t make a difference, but when we recreated the file, importing the images using File > Place instead of copy/paste, the INDD file size was only 2.2MB!
Figure 1: How can this empty one-page document possibly take up 95 MB on disk (left)? The answer: cruft! After a Save As, it’s down to a manageable size (right).

Fortunately, text doesn’t get trapped in the same way that image data does. When you delete text, it’s gone for good, unless Track Changes is on. Likewise, increasing the size of pages or the pasteboard does not increase the file size.
Decant, Decruft
The easiest way to de-cruft an InDesign document is to use the Save As command. By choosing File > Save As you can create a duplicate of your document that is cleansed of most of the accumulated cruft. Hidden, leftover data from deleted images is not included in the new file. Not only will you save disk space, you’ll save time too, with faster file transfers and peppier performance overall.
Technically, the Save As trick creates a new file. If you use the same name, it deletes the bloated oldie, replacing it with this new slim one.
There are other methods for reducing unwanted build-up, but at this point you need to ask how badly you want smaller, more efficient files. If you have a legitimate need to squeeze every last kilobyte of extraneous data out of your files, there’s a lot you can do to trim the fat. But if you have ample disk space, you’re not hampered by slow files, and you don’t suffer from OCDD (Obsessive Compulsive Decrufting Disorder) it’s probably not worth the time and effort to go beyond the occasional Save As.
That said, here are some steps you can take to reduce InDesign file size, in descending order of impact.
Resize Graphics. Because InDesign generally creates 72 ppi previews of your placed images, at 100% size, it behooves you to properly size those images before you place them into your layout. For example, say you have a little 1350 × 900 pixel photograph that you want to be 4″ × 6″ in a print layout. If you leave the image set to 72 ppi when you place it, then resize it in InDesign, your document will become about 600K larger. If, instead, you resize it to 4″ × 6″ in Photoshop’s Image Size dialog box—with the Resample checkbox disabled, so that it’s increasing the resolution, but not adding or removing pixels—then place it in InDesign, your file will only grow by about 360K (Figure 2).
Figure 2: This 72 ppi image from a digital camera is almost 15 MB (top) and could fatten your InDesign file unnecessarily. Reduce the pixel dimensions to just the amount you need, and increase the resolution before placing it in InDesign (bottom).

These two documents will produce identical output, but one is 240k larger because the previews InDesign creates match the document size specified in Photoshop. So InDesign creates a preview that’s 18.75″ × 12.5″ for the 72 ppi image, but only a small 6″ × 4″ preview for the 225 ppi image.
In fact, placing images at 72 ppi has the same net effect as embedding them, since the embedded preview is the same size and resolution as the image itself!
The moral of the story is to properly size images before placing them into InDesign. Sizing images after placing them has no effect, since the previews have already been added to the document.
If you’re creating interactive documents, your images rarely need to be more than 150 ppi. For most print usage, using 225 ppi resolution images will produce excellent results while saving a significant amount of file size. (The old rule of 300 ppi is wasteful and inefficient. For example, a 4″ × 6″ raster image at 600 ppi is 24.7 MB. Downsample that to 300 ppi and the file size drops to almost 7 MB. Not bad, but 225 ppi is only 3.5 MB, with rarely a drop in image quality in most cases.)
Export as IDML. When you export as IDML (or INX, if you’re still using version CS3), InDesign creates an XML-based representation of your InDesign document, like dehydrating a slab of juicy meat into jerky. (That’s a vast oversimplification, but it’ll do.) You can then open that IDML file and InDesign reconstitutes it—literally rebuilding a new document that looks exactly like the old one. This not only removes garden-variety cruft, it also strips missing plug-in data and other ickyness that may have crept in along the document’s history. The IDML “roundtrip” process makes your file even sleeker and less prone to be sluggish and buggish.
You might know that if you open an INX or IDML file when you don’t have access to the graphics that were placed in the original InDesign file you see gray boxes instead of previews of the graphics. This is because image previews (or proxies) are not included in the INX or IDML. InDesign generates fresh previews when it creates a new file. But did you know you can use this phenomenon to your advantage? If you’re sending a file to someone else to work on and that person does not need to see the image previews, you can send them an INX or IDML and not the graphics. A document with a long history and lots of placed high-res graphics can consume many megabytes of disk space. But you can ditch up to 99% of that file size via IDML export, making it easily small enough to attach to an email or IM. Then when you don’t mind the increased file size, just make the art available to InDesign and update the links.
Disable Image Previews. Every time you save a file in InDesign, the program generates one or more page previews, so that you can see what the file looks like in Bridge. However, including image previews has the same effect as embedding graphics in your document—it can balloon the file size, especially if you chose to include large previews of all pages! But what if you don’t use the Preview feature in Bridge? You can trim a little off the sides by opening the Preferences dialog box in InDesign, choosing the File Handling pane, and disabling the option called Always Save Image Previews with Documents (Figure 3). Alternatively, leave that on, but reduce the number of pages and/or preview size settings. Note that changing the preference won’t have an immediate effect on existing documents; page preview bloat can only be fully eliminated with the Save As command.
Figure 3: Be conservative when telling InDesign to save image previews unless you really make use of them in Bridge.

Delete Unused Document Stuff. Part of being trim is actually losing weight; another part is dressing trim! So just as you wouldn’t wear wide horizontal striped outfits, you want to remove the appearance of cruft: extra styles, extra frames, etc. You look neater, so you feel neater, and people see you as neater and more efficient.
In the case of InDesign, “dressing trim,” means trimming out anything that is unused in the document. Get rid of all extraneous styles (paragraph and character styles, TOC styles, table and cell styles, and object styles), delete unused swatches, master pages, empty document pages, pasteboard junk, unused layers, XML tags and elements not attached to the layout, unused text variables, text conditions, hyperlinks, cross-references, notes, tracked changes, and InCopy assignments. In short, toss everything that isn’t bolted down.

1 2 Next

David Blatner is the co-founder of the Creative Publishing Network, InDesign Magazine, and the author or co-author of 15 books, including Real World InDesign. His InDesign videos at LinkedIn Learning (Lynda.com) are among the most watched InDesign training in the world. You can find more about David at 63p.com.
Editor in Chief of CreativePro and InDesign Magazine. Instructor at LinkedIn Learning with courses on InDesign, Illustrator, GIMP, Inkscape, and Affinity Publisher.
  • Anonymous says:

    At Adobe, we most strongly recommend use of PDF/X-4 as opposed to PDF/X-3 as recommended in this article.


    PDF/X-4 preserves live transparency which retains device independence. PDF/X-3 requires transparency flattening which by definition is device dependent since you must flatten at device resolution to avoid imaging artifacts (and which, by the way won’t avoid display artifacts). Furthermore, such flattening can seriously bloat the size of a PDF file if any significant amount of explicit or implicit transparency occurs in the original InDesign document. And that bloat usually tremendously exceeds any gain achieved by not including ICC color profiles as you show for your suggested PDF/X-3 settings. Not including ICC profiles certainly does not lend itself to reliable PDF print publishing workflows.

    – Dov Isaacs

  • Anonymous says:

    This is one of the best articles you’ve posted! Excellent content, and other than a few mentions of a handy plug-in that will do certain operations, all the info required to do this ‘in the comfort of your own studio’ without having to buy anything else. Bravo!

  • Anonymous says:

    Great article with all kinds of tidbits of useful information I can apply to my daily InDesign use. Thanks!

  • Anonymous says:

    Thanks for the article. I was hoping it would help me figure out why, when I create a new letter sized document, it takes what seems a very long time to open. When I create a document that is, for example 9 x 10, it opens immediately. My mystery remains unsolved.

  • Terri Stone says:

    A mystery indeed! I’ve never heard of such a thing.

    Terri Stone
    Editor in Chief, CreativePro.com

  • kavu says:

    lol, awesome, i’m going to try it

  • Anonymous says:

    In “Reducing Exports” / “Reducing PDF FIle Size”, this article recommends “changing all the ‘pixels per inch’ fields to 150.”

    It is a little dangerous to do this for both the “downsample to” fields and the “for images above” fields.

    For instance, if you start out with a 151dpi JPEG for some reason, and you force it to downsample to 150dpi, you are quite plausibly going to get nasty artifacts from the resampling. For the benefit of…1 dpi.

    So think carefully about whether it’s worth changing the “for images above” option.

    – John Hawkinson

  • Anonymous says:

    I’m currently working on an interactive InDesign catalog that I want to be emailable. This article has really helped my understanding of how indd files are saved. I didn’t know that it bloated like this.

    The strange thing is that I tried this out on a 24mb file and it bloated to 28mb after I deleted all of these elements by doing the save as, then removing unused elements. I had 10 unused masters. When I export to a idml, save as an indd, then remove unused elements, I get the results I’m looking for. It went from a 24mb file to a 6mb file.

    Before doing this, I got my pdf from 110mb file to 16mb. I’m still working on it, but hopefully these techniques will knock another 10mb off.

  • Anonymous says:


    This thread explains how to delete the XMP data that is making your PDFs huge. If you have a file that has been worked on over a long period of time and been saved many times, all of this will be embedded in the PDF. Follow the instructions to create a script for Bridge using Extendscript Toolkit (it leaves out the simple step of saving the script into the folder with a descriptive name). It works.

    100 DPI proof PDF before deleting XMP: 4.9MB
    100 DPI proof PDF after deleting XMP: 106KB

  • Arken78 says:

    Wow! I was on the verge of buying a bigger archive drive as some of my INDD files were 140mb+ (hundreds of them!). By simply doing the ‘save as’ trick it’s pushed most of them down to sub-3mb! A magazine template folder that used to be more than 600mb is now 104mb. Brilliant advice, thanks David.

  • Guest says:

    A great article.. I only wished I had time in the day to read stuff like this (always looking for a quick fix!).


  • Karen Jean Armstrong says:

    Thank you so much! Your article gave me the info I needed to downsize my InDesign file. You saved me a lot of time and headache! 

    I will also be doing an aquatics guide in a month and I will use what I learned from your article. I will be more manageable this time around–hooray!!! 

  • Davex says:

    The trick of exporting to idml and reporting/ saving as indd worked perfectly. 1.5 gb down to 78 mb. 

    The save as trick dropped it from 2.5 gb to 1.5. This was not enough. 


  • Miguel Agawin says:

    Has anyone analysed cruft in dps exports for iOS? Thanks!

  • Greg Thomas says:

    Do these steps reduce cruft in epub exports? Thanks! My epubs with lots of images are huge.

  • Sammi says:

    This article just saved my design life!!! THANK YOU SOOOO MUCH!!!

  • Richard says:

    Linked psd files into indesigns sometimes causes large pdf exports for no reasons. Its a bug within photoshop. If you delete all you layers in photoshop file and save it, then undo what you did, and resave it. It will reduce the files size of the indesign export.

  • Jenn Cowan says:

    Can you clarify, “with the Resample checkbox disabled, so that it’s increasing the resolution, but not adding or removing pixels” because Figure 2 reflects the Resample checkbox enabled.

    • David Blatner says:

      Jenn: Good eye! You are correct that the illustration does not entirely reflect the text above it. Sorry about that. You want to enable the Resample checkbox if you need to downsample to a reasonable size and resolution, or disable it if the image is already the correct pixel dimensions (amount of data) but is incorrectly set to 72 ppi.

  • >