Package an InDesign Treatment So Another Designer Can Actually Open It

The Package command in InDesign does most of what people expect from it, and less than they need. It gathers the document and its links, writes a report, and puts the whole set into a folder. It cannot decide which of those things should travel, notice that a link points at a drive the recipient will never mount, or tell you whether the folder you just made is one the next designer can actually open and edit on their machine.

So the job is three moves, in order. Gather the native document and the dependencies you're allowed to pass on. Make the exclusions explicit, in the file and in writing. Then open the result somewhere the original paths don't exist and watch what resolves.

This is a same-workflow handoff: both designers work in InDesign, and the recipient is meant to edit the treatment, not just look at it. If they only need to read it, you're making a PDF, and that's a different job with a different set of failure modes.

Start with what the recipient has to edit

Before you touch File > Package, answer one question in a sentence. What is the next designer going to do to this file?

"Take it over" is not an answer. "Re-crop the hero on page 4, rewrite its caption, and keep the deck consistent with the v4 copy" is. The difference matters because it tells you which dependencies are load-bearing right now and which ones merely exist. It also tells you what to check at the end, when you're deciding whether the handoff worked.

Two versions of the file come out of this thinking.

The first is the original, and it stays where it is, untouched. Everything the studio might need later — archived rounds, superseded price points, the layer someone will ask about in three months — stays in that file, on your machine, in your folders. The original is your record.

The second is the handoff copy, and it is a different document with a different job. It carries only what the recipient needs. It gets its own name, so nobody edits the wrong one: Ridgeline_Spring_Treatment_v4_handoff.indd next to the original Ridgeline_Spring_Treatment_v4.indd. The version number lives in the file name and in the note you send with it, because file names get truncated in email and people attach the wrong thing.

Keep the two purposes separate and most of the rest of this gets easier. An editable source is not a reading copy. A reading copy is not evidence that the source is clean. And a package folder is not a synonym for either one.

Inspect the dependencies before you collect them

The walkthrough below uses an invented treatment document. Nothing in it was built, packaged, or opened on a machine for this article; no package was created and no recipient test was run. Treat it as a decision script rather than a transcript. The order of the decisions is the useful part, and the dialog labels are worth checking against your own version of InDesign.

The fixture is a twelve-page pitch treatment for a fictional outdoor brand. It has three dependencies worth caring about.

The first is the required image: hero_summit_ridge.psd, placed on page 4 and again on page 9. It resolves. Packaging will copy it, and the recipient will have it.

The second is a missing one: route_map_v3.ai on page 7. The link points at a studio share that was retired when the pitch sprint ended. That's the state of the world, not a crisis. The map is required for the finished deck, but it isn't required for the round the recipient is being handed, and the client's asset library now holds a newer revision of it anyway. Delivering the old copy forward would be the wrong fix.

The third is the one people miss: q3_clearance_banner_old.psd, sitting on a layer called Archive-2024 on page 6. The layer is hidden and set to nonprinting. The asset was licensed for a retail campaign two years ago, and the layer also holds superseded price points that have no business confusing a new reader.

Now look at what the Links panel says. It lists all three files. It doesn't care whether you can see the thing it's listing. That's your first useful tool, and it's why "inspect the links" means reading the panel rather than eyeballing the pages.

Here's the discipline that separates a handoff from a copy: a missing-link warning tells you that something is unresolved, not what the consequence is. The consequence here is real but small — page 7 won't render its map until someone relinks it — and the correct response is to name it. Restore the file if you can do that legitimately. If you can't, say so in writing and say where the authorized version lives. What you don't do is drop in a different image to make the warning go away. That trades a visible, harmless alert for an invisible, harmful one: a page that looks complete in a file that is quietly wrong.

The archive layer gets the same treatment in reverse. It isn't broken, it isn't flagged, and it will not appear in the PDF you export — hidden and nonprinting content has no reason to be in that export. Which is exactly why the PDF cannot be your inventory. Page 6 looks finished in the exported file. It's finished in the exported file. The InDesign document is a different object, and the difference lives in a panel you have to open on purpose.

Package the copy you actually mean to send

Clean the handoff copy before you package it, not during.

Open ..._v4_handoff.indd, go to page 6, and delete the Archive-2024 layer along with everything on it. Confirm it's gone from the Layers panel and that q3_clearance_banner_old.psd no longer appears in the Links panel. The asset still exists on your disk, in the original, where it belongs.

Doing this first matters because the packaging options are collection settings, not approval settings. There's an option that pulls in fonts and links used by hidden and nonprinting content. If you enable it, you'll be carrying the archive banner into the folder you hand over — even though nothing on any page shows it and nothing in the exported PDF hints that it's there. An option that collects hidden content is a decision about copying. It is not a decision about whether the content should be in the handoff at all, and no checkbox in that dialog will make it one for you.

So delete it, then package. Adobe's help page on packaging files for output describes what the options do; read it beside your own dialog, since labels move between releases.

The summary step before the options is the last cheap moment to notice a problem, and it's worth actually reading. It tells you how many links the document has and how many of them are unresolved, and it lists the fonts in use. If the missing-link count is one, that matches the map on page 7 and you know where you stand. If it's four, you have a different afternoon.

Then the choices, reason by reason:

Copy linked graphics — yes, for the assets that are authorized to travel. In the fixture, that's the hero.

Update graphic links in package — yes. This is what makes the copies inside the folder point at each other instead of pointing back at wherever they used to live on your machine. Skip it and you can hand over a folder that still fails on a machine that has never seen your drives.

Include fonts and links from hidden and nonprinting content — no, and see above for why.

Copy fonts — no. More on that below.

Create report — yes. The report inventories the document's links and fonts alongside the packaged files. It's a record of what the dialog saw, which is useful precisely because it doesn't know what you know.

After the packaging finishes, the before-and-after record looks like this:

You can rename the outer folder. Leave the structure inside it alone — moving or renaming the links folder breaks the paths you just fixed.

Write down what the package cannot carry

The package copies files. It does not transfer permission, and the gap between those two things is where handoffs get people into trouble.

Fonts are the clearest case. The wrong fix is easy and tempting: zip the font folder and send it along. Don't. A font-file option in the packaging dialog is a copying mechanism, not a license, and having a font on your machine says nothing about whether the next designer is covered for it. Fonts that arrive through a subscription are handled differently — each designer activates them through their own account rather than receiving a file from you. If the treatment uses a face that came to you as a client-supplied file, that's a dependency you cannot carry, and the honest move is to name it in the note and let the client authorize a second seat or approve a substitute. The fixture sidesteps this on purpose: both designers can reach the same subscription faces, so no font file ever needs to leave anyone's machine.

The missing map is the second gap. It isn't on your disk, it isn't in the package, and it isn't a failure — it's a listed open item. Say which file, which page, which version the library currently holds, and who to ask. That's the difference between a package that's complete and a package that's honest, and the honest one is more useful.

Two smaller things belong in the same list. A placed asset can have dependencies of its own if someone else assembled it, and the InDesign package follows the InDesign document's links, not the relationships inside a linked file — check any asset you didn't build yourself rather than assuming. And if you also export an interchange file as a fallback, treat it as something a person has to open and verify, not as a promise that the layout arrives intact somewhere else.

The handoff note is short and boring on purpose:

• Document name, version, and what it is — editable source, not a reading copy
• The reading PDF, named, so nobody opens the wrong file to look at the deck
• What's included, where each asset came from, and who authorized its use
• What's excluded and why
• What's still unresolved, with the authorized route to get it
• The edit that's been agreed, and the date

Test it from the other side

A package folder proves that the dialog ran. It does not prove that the recipient can open the file, and the only way to find out is to stop being the sender.

The real test happens on a machine that has never had your asset paths — a colleague's laptop, a different user account, a spare machine with the original share unmounted. Copy the folder over, open the handoff document, and check four things.

Do the required links resolve? The hero on pages 4 and 9 should render from inside the package, with no missing-link badge.

Can the recipient do the agreed edit? In the fixture, that's re-cropping the hero on page 4 and rewriting its caption. Here's the check that separates "the link looks fine" from "the link belongs to this folder": select the placed hero in the Links panel and use Edit Original. It should open the copy inside the package folder — not a file on your machine. A link that resolves to your drive will keep working for you and fail for everyone else, and it looks identical until you test it this way.

Is the excluded asset actually absent? Open the Layers panel and the Links panel, not the pages. Page 6 will look correct either way; that's the whole point of the archive layer being hidden.

Does the package tell the truth about what's open? Page 7 should still report a missing link, and that should match the note. A handoff with one documented gap is in better shape than one with zero gaps and a silent substitution.

If you don't have a second machine, there's a cheap approximation: rename the original asset folder on your own disk, then open the package. Anything that still resolves is resolving from inside the package. It's worth doing, and it's worth knowing what it doesn't cover — fonts, app version, and operating-system differences all stay untested, and a real machine in someone else's hands is the only thing that settles those.

Then write down what you found. Including the part where page 7 is still waiting on the library.

What done looks like

The handoff is finished when the next designer can perform the edit you agreed on, and knows exactly what is still missing and where to get it — not when a folder exists with the word "Package" in it.

The package report is a record of what a dialog collected. The handoff note is a record of what you decided. Keep both, and keep the original untouched, so that when someone asks in three months why the map wasn't included, the answer is already written down.

Frequently asked questions

Should I package the original InDesign file or make a separate handoff copy?

Make a separate handoff copy. The original stays untouched as your record, with archived rounds and superseded material. The handoff copy carries only what the recipient needs and gets its own name, such as _handoff, so nobody edits the wrong file.

What should I do about a missing link like route_map_v3.ai?

Name it in writing, restore the file if you can do that legitimately, and say where the authorized version lives. Do not drop in a different image just to make the warning go away; that trades a visible, harmless alert for an invisible, harmful one.

Why delete a hidden archive layer before packaging instead of relying on the package options?

Packaging options are collection settings, not approval settings. An option that pulls in fonts and links used by hidden and nonprinting content will carry the archive asset into the handoff folder, even though nothing shows it and nothing in the PDF hints it is there.

Which package choices does this workflow call for?

Copy linked graphics for authorized assets. Update graphic links in package so copies point at each other. Do not include fonts and links from hidden and nonprinting content. Do not copy fonts. Create the report, because it inventories what the dialog saw.

How can I test whether the package actually works for the recipient?

Open it somewhere the original paths do not exist and check four things: required links resolve, the agreed edit can be done, excluded assets are absent from the Layers and Links panels, and any missing link matches the note. Use Edit Original to confirm the link opens the copy inside the package. Renaming your original asset folder is a cheap approximation, but fonts, app version, and operating-system differences stay untested.

Further reading

• Build an InDesign Preflight Profile for a Treatment Handoff — Read this when you want a named, repeatable check for broken links, overset text and missing fonts before packaging, plus what it does not inspect.
• Check the Actual Treatment File You Intend to Send — Read this once the package exists but before you send it, to compare the file against the approved document and record what you checked and left alone.