Skip to main content
Participant
December 28, 2025
Question

Opening, let alone saving, an .INDDL locally is sluggish and problematic

  • December 28, 2025
  • 2 replies
  • 283 views

I’m having a tough time with a "Share for Edit" (i.e., "InCopy for the web") document. It is sluggish to open from InDesign (MacOS, 21.1), and I see the "spinning beach ball" far too often, and for far too long even when trying to do simple things, like scroll. The document isn't particularly challenging—text only, no graphics, maybe 100 pages. 

 

While I can "see” the document through the browser, opening it in InDesign seems to be a nonstarter. As if there is some sort of handshake or timeout problem with the server. Force Quit, try again. Repeat. Sometimes I can get the document to open, but thus far, after several dozen tries, no luck saving it locally (i.e., back as .INDD) so I can actually use the document.

 

Adobe doesn't seem to give us any option for directly downloading the .INDDL. My editor spent a lot of time updating that document (despite all the hassles of "InCopy for the web"), and I would hate to lose all the changes she made.

 

Does anyone have any other tips?

2 replies

Mike Witherell
Community Expert
Community Expert
December 29, 2025

Paul,

Do you have any sense of your upload/download internet speed at the time this is loading so slowly?

Mike Witherell
Participant
December 29, 2025

No, I didn't. But as I have fiber, it is rarely a problem—up or download. But thanks for asking.

Participant
December 29, 2025

As an added note: Using the InCopy Web's "duplicate" function, and waiting a while for the server to catch up, did allow opening the duplicated file just fine. 

Curiously, the file (text-only, about 120 pages) was about 5 MB. But according to the file browser in Id, it was 3.2 GB. Now I wonder what all Adobe is "saving" inside those .INDDL files—every one showed clear signs of bloat. 

 

And if the "live editing" feature of Id was having to rescan 3.2 GB of content every time I moved the cursor, that would explain the sluggish behavior. 

Anubhav M
Community Manager
Community Manager
December 29, 2025

Hello @Paul Nylander,

I'm sorry to hear about your experience. Could you share a link to a sample file here or via DM along with a small screen recording of the problem, so we can check it with the team?

Looking forward to hearing from you.

Anubhav