[ID-4273319] InDesign 2026 shows Damaged document when opening previous version documents from Synology NAS
InDesign 2026 says that my documents are damaged.
All documents that are on my Synology NAS. Connected via SMB3.
(InDesign 2025 works fine.)
If I quit and restart InDesign 2026 - I can open one file once. Alla files after that is "damaged".
New file created with InDesign 2026 and saved on NAS works.
Looks like the issue is with documents from previous version that opens as "converted".
Only happens on NAS. Not on local files.
Workaround: Copy indd file to your local drive, open, save and upload back to its original location
Indesign 2026
Mac OS Tahoe.
MacBook Pro M1 Max.
Andreas Norén
shared this idea
Hi,
Thank you for reporting the issue. It is currently under investigation.
—
Adobe InDesign Team
-
Timon Royer
commented
This bug is CRITICAL and completely halts our small business workflow.
IMPACT ON OUR BUSINESS:
Project Blocked: Current client materials (InDesign docs with linked assets) on Synology NAS (DSM 7.2, SMB3) now show as "damaged" or fail to package/export in InDesign 21.2 under macOS Tahoe 26.2.
Files Were Fine: These exact files opened/packaged perfectly until late 2025 (InDesign 20.x + macOS 25.x).
No Workaround Viable: Local copies defeat NAS collaboration; AFP deprecated; Synology Drive Client doesn't fix packaging errors. We're losing days of production time daily.
Adobe Support (Grp-idfile) confirmed files "irreparable" but ignored SMB root cause. This affects every NAS user in creative workflows!
Please prioritize a fix in 21.3 – our revenue depends on it!
-
Cwj
commented
Have there been any updates on this? It is causing a host of issues and greatly affecting the ability to collaborate between team members.
-
David Jeffrey commented
Any updates on this @Adobe, it's affecting all our designers using Synology Drive too.
Copying locally and back again each time is not amazing. Many, many designers are working remotely so using systems like Synology Drive or OneDrive to sync with the office.
Is there a patch expected soon?
-
RatFink
commented
This error also occurs if the folder you're using happens to be backed up via OneDrive. The solution - move the files to a folder not backed up by OneDrive fixes the issue. Temporarily turning off OneDrive syncing didn't work for me. I had to move it to a completely different folder.
-
Peter Pp commented
Workaround: Pause syncing while your file is open in InDesign. Finish work, save file, resume syncing.
-
Betsy Rubinstein
commented
I've reverted back to 2025 after 2026 bungled multiple pdfs. Really frustrating -- I've used InDesign since it first replaced pagemaker -- so 25 years? -- and never had problems with pdfs before.
-
Filip Blazek
commented
The files are actually not damaged. The workaround for this pathetic bug is to copy indd file to your local drive, open, save and upload back to its original location. Then you can open it again directly from the server. Older files created in older versions (CS6 for instance) are not affected by this extremely annoying bug.
-
William Vogels
commented
Since the update to InDesign 2026 some files seem to be corrupted. When opening from our NAS server a dialog opens with the choice to restore the damaged file, but this never works.