Skip to main content
Known Participant
November 14, 2025
Question

indesign could not package the document cannot copy necessary linked files

  • November 14, 2025
  • 4 replies
  • 348 views

After updating to both Tahoe 26.1 and ID 2026, I can no longer package files located on my Synology NAS.  I'm getting the "indesign could not package the document cannot copy necessary linked files" error. I can package if all of the files are on my local drive. This is fine, except I have thousands of files on the NAS that my studio works from. 

 

Anyone have a solution for this? I'm going nuts. 

 

My phone call with Adobe support was "if you resaave all of the linked files with new names in new locations, they will re-link up" This is a nightmare for a studio, so its a non-starter. 

 

Affinity works fine, and would be a PITA to move to, but I'd prefer for now to stick with ID. 

4 replies

Participating Frequently
February 5, 2026

I’ve had exactly the same problem. ID 21.1 with Tahoe 26.2: the problem didn’t exist before the OS update. The solution lies in reconnecting to the Synology server via AFP, rather than SMB. 

In DiskStation Control Panel, go to File Services > AFP and enable AFP service.

This should fix it.

Ginny5C7C
Participant
February 4, 2026

I’m using InDesign 21.1 with Tahoe 26.2. My files are not packaging, same message as above. I am packaging on my hard drive, the file name is super simple with no characters. It’s just been continuous issues with InDesign 2026. Not a fan. 

leo.r
Community Expert
Community Expert
February 4, 2026

I’m using InDesign 21.1 with Tahoe 26.2.

 

First, make sure to update to InDesign 21.2 (even though I doubt this will affect this particular issue).

 

I am packaging on my hard drive

 

Does it mean that your links are located on your local drive, NOT on a server? Up until now, this problem was only reported for network-based links.

 

leo.r
Community Expert
Community Expert
February 6, 2026

@Ginny5C7C Yes, it’s long overdue to fix this critical issue regardless of who’s responsible for this problem (Apple, Adobe, or both).

 

I also recall that someone reported that removing extended attributes from your linked files can solve the issue, don’t know if it’s true.

 

You’ll need to use Terminal, here’s one explanation of how to do so:

https://apple.stackexchange.com/questions/416592/how-to-remove-extended-attributes-from-all-files-in-a-folder-on-mac

 

Abhishek Rao
Community Manager
Community Manager
November 14, 2025

Hi @atracksler,

 

Adding to what expert suggested, please try testing the behavior in Safe Mode to rule out any third-party interference during the packaging process (Ref: https://adobe.ly/4r1ueU4). You can also check this similar community thread where other users encountered the same issue: https://adobe.ly/4p9Xp5s.

As noted there, the problem seems tied to how InDesign interacts with NAS volumes connected over SMB on macOS 26 (Tahoe). The team suggested trying an AFP connection instead of SMB, as this often resolves the issue. Please give this a shot and let me know if it helps.

 

Looking forward to your update.

Abhishek

BobLevine
Community Expert
Community Expert
November 14, 2025

Sounds like a permissions issue. Apple keeps locking things down.

 

Can you package to your local hard drive? If so, I would be looking at system preferences to find any permission flags.