Before moving a design project to another Mac, collect its linked images and other external files with the design app’s packaging or collection feature, then open the collected copy from its new location and check for missing links. Finder can copy or zip folders, but it cannot determine which external files a design document depends on. This guide covers the Mac handoff task: make a portable copy for transfer or storage while keeping the original project intact.

What needs to travel with a design file?

A design document may point to images, placed graphics, video, or other files stored elsewhere. Those links can break when the project moves because the document references a file path. For instance, InDesign’s Links panel lists placed files and flags missing or modified links; Adobe says missing links can affect output. Links panel overview

Fonts are a separate dependency. A package can include font files when the application supports it, but font licensing may limit copying or sharing them. Adobe says Adobe Fonts files cannot be copied or moved; collaborators may need their own access to fonts, or a suitable PDF for viewing or print output. Adobe Fonts: Package font files

Collect assets in the design app first

Save the document before collecting anything. Then use the app’s own dependency view or package command; the available feature and what it includes vary by application and version.

  • InDesign: Choose File > Package. Review the preflight summary and resolve missing links or fonts before proceeding. Select options such as Copy Linked Graphics and, if appropriate, Update Graphic Links In Package. The package can also include fonts, a report, and optional IDML or print PDF files. Adobe’s InDesign packaging guide

  • Illustrator: Choose File > Package, set the destination and folder name, and enable Copy Links. You can collect links into a separate folder and relink the packaged document to them. The app can create a report; its font copying option excludes CJK fonts, and Adobe advises checking font licenses. Adobe’s Illustrator packaging guide

  • Photoshop: Save the document, then choose File > Package and select a destination. Photoshop copies the document and linked Smart Object source files into a folder; Adobe notes that the document must be saved at least once before packaging. Adobe’s Photoshop guide to packaging linked Smart Objects

  • Affinity Publisher: Open Document > Resource Manager and review resource status. Its Collect feature gathers selected linked image and document resources into a folder. Affinity says the collection does not include fonts or .afpub files, so handle those separately. Affinity Publisher Resource Manager

If your app has no package or collect function, inspect its resource or links panel, locate each external file, and copy them into a new project folder while preserving the document’s folder structure where possible. Do not assume a generic Finder copy has identified every dependency. Keep the untouched source folder until the copied project has been checked.

Make a portable copy in Finder

Choose a destination on your Mac or connected storage, then create a clearly named folder for the collected project. Keep the native design document and its collected assets together. If the app created an output folder, use that folder as the project copy rather than manually rearranging its contents. Finder’s list view can help you review names and sizes; Apple documents list view as a way to see file details. Organize files in Finder

For a transfer, Control-click the completed project folder in Finder and choose Compress to create a ZIP file. Apple documents Finder’s built-in compress and expand controls; compression combines the folder into one archive but does not collect missing project assets. Zip and unzip files and folders on Mac

Verify the moved copy before removing the original

Open the design document from the destination folder, not from its old location. Check the app’s links or resource panel for missing files, then inspect key placed graphics and any fonts called out by preflight or a report. If a link is missing, use the app’s relink or locate control to point to the collected file, then save the copy. Repeat the check after extracting a ZIP at its destination if that is how the project was transferred.

Remember the boundaries: packaging generally collects dependencies the application knows about, not every item related to the project. External library assets, plugins, linked content inside nested documents, fonts, and app-specific resources may require separate access or handling. A PDF can preserve a viewing or print reference, but it is not a substitute for a fully editable project. Keep the original until the moved copy opens and the resources needed for the recipient’s task are available.

Sources