Adobe InDesign: Bugs
When filing a new bug, please provide:
- Version of Adobe InDesign, InCopy or InDesign Server
- Steps to reproduce the issues
- Expected result
- Actual result
- Test file, screenshot, video or GIF capturing the issue (optional)
- or
No existing idea results
- ~ No ideas found ~
7605 results found
-
PDF export freezing on 99%
Continual problems with PDF exports freezing on 99% and not completing. InDesign is getting worse and worse. Unreliable, unstable, just garbage.
2 votes -
Pages panel not scrolling to allow all pages to be accessible
InDesign v21.3 (Updated last week, no issues until today. Daily use)
This morning when I opened InDesign, I discovered I was unable to scroll and select the last page of the document. The top half of the last page is visible through the bottom bar of the panel where the number of pages is displayed but unclickable. This prevents a change of parent page style, addition of pages in the correct parent style or the selection to override the parent page style.
I have tried resetting my workspace, restarting Indesign and changing panel views. The bottom row remains elusive.
2 votes -
outer glow moved
Objects with outer glow or drop shadow display the effect in the wrong location.
You can see the expected out come and then the glow effects in the completely wrong locations in the other image.
Indesign 21.3 x64.
2 votes -
[ID-4279268][Support Ending for Intel Based Apps] Rosetta 2 is planned to be mostly discontinued by late 2027
Mac OS gives error alert on launch Indesign, also Photoshop
Reported bug to Apple:
Adobe 2026 InDesign & Photoshop2026 are both Universal’ apps. (per Get Info window on each app). When I launch either of these, I get a Notification saying it will no longer be supported on a future OS release. Please get your act together.2 votesClosed: Different Product ·
AdminSanyam Talwar
(Senior Lead Software Engineer, Adobe InDesign)
responded
[Support Ending for Intel Based Apps] Rosetta 2 is planned to be mostly discontinued by late 2027
Users will not be able to launch InDesign via Rosette. Apple has started to notify customers. Reference link: https://support.apple.com/en-in/102527
-
Losing the ability to use 'undo' [Command-Z] function.
I'm frequently losing the ability to use 'undo' [Command-Z] function. It's not all the time, but when it happens I can't undo anything. I have to quit InDesign and re open it to fix it. A few hours later it strikes again. There doesn't seem to be anything obvious triggering this. It's not crashing, it's just not functioning.
2 votes -
Cropped content inside frames becomes visible on older mobile PDF viewers.
I found a rendering issue in InDesign 2021 (and potentially newer versions). When an image or PDF is placed inside a frame (cropped), the content outside the frame boundaries is still being rendered on older mobile devices' PDF viewers.
Steps to reproduce:
- Place a large PDF/Image inside a smaller InDesign frame.
- Export as a standard PDF (Interactive or Print - High Quality).
- View the PDF on an older smartphone (e.g., older Android/iOS built-in viewers).
- The "hidden" parts outside the frame are visible.
The content outside the frame should be completely clipped or removed from the render stream to ensure privacy and visual consistency across all devices.
Exporting as PDF/X-1a:2001 solves the issue because it flattens the transparency/layers.
I found a rendering issue in InDesign 2021 (and potentially newer versions). When an image or PDF is placed inside a frame (cropped), the content outside the frame boundaries is still being rendered on older mobile devices' PDF viewers.
Steps to reproduce:
- Place a large PDF/Image inside a smaller InDesign frame.
- Export as a standard PDF (Interactive or Print - High Quality).
- View the PDF on an older smartphone (e.g., older Android/iOS built-in viewers).
- The "hidden" parts outside the frame are visible.
The content outside the frame should be completely clipped or removed from the render stream to ensure privacy…
2 votes -
InDesign refuses to run if it can't verify our license ONE TIME, wasting a full day of work.
First off, you're missing a bug category: LICENSING
Now the real defect: InDesign refuses to launch if it can't contact the license server ONCE. So... if you're on a long-distance flight and have a bunch of work to do, YOU CAN'T. There is no excuse for this. Any competent software will run temporarily in that instance.
Furthermore, we have a fully-paid license. There is no reason for the software to check its license any more frequently than the billing cycle. At every check, the server should report to the software what the end of the currently-paid period is and the software will run without connection until then. And even then, the software should function for AT LEAST A DAY if it is offline.
This should NEVER happen to a paying customer.
First off, you're missing a bug category: LICENSING
Now the real defect: InDesign refuses to launch if it can't contact the license server ONCE. So... if you're on a long-distance flight and have a bunch of work to do, YOU CAN'T. There is no excuse for this. Any competent software will run temporarily in that instance.
Furthermore, we have a fully-paid license. There is no reason for the software to check its license any more frequently than the billing cycle. At every check, the server should report to the software what the end of the currently-paid period is and the…
2 votes -
Dotted lines are not exported correctly
Dotted lines are not exported correctly. Corners on a path is ignored. End parts of straight lines are ignored too.
2 votes -
InDesing 2026 - Document assembly issue
When I try to assemble my InDesign document, an error message appears stating that it is impossible to package the document or link the necessary files. However, no links are broken and the path to the company server is working. This is very problematic when I have a multi-page document…
2 votes -
Installing InDesign 20.5.2 caused the system to make it the default version, replacing 21.2.0 as the default app for opening InDesign files
When I double-click the file I have been working on, I get an error message that says it couldn't be opened because it was created by a newer version of InDesign. It calls out 21.2 as the offender. If I look at the recent updates for Creative Cloud, it looks like 21.2 was updated 19 days ago, and 20.5.2 was updated 13 days ago. It looks like the association for which app to open .indd files was changed with the 20.5.2 update, and it no longer opens the latest version of the product. I can open 21.2 manually, but I can't just click on the file and have it open correctly. Your right hand doesn't know what the left is doing! Please send another update for the 21.2 (or later dot number) to correct this.
When I double-click the file I have been working on, I get an error message that says it couldn't be opened because it was created by a newer version of InDesign. It calls out 21.2 as the offender. If I look at the recent updates for Creative Cloud, it looks like 21.2 was updated 19 days ago, and 20.5.2 was updated 13 days ago. It looks like the association for which app to open .indd files was changed with the 20.5.2 update, and it no longer opens the latest version of the product. I can open 21.2 manually, but I…
2 votesWorkaround1: Set Default Version to 21.2.0
- Right-click any .indd file
- Select Open with → Choose another app
- Click More apps
- Select Adobe InDesign 21.2.0
- Check “Always use this app to open .indd files”
- Click OK
Workaround2: Uninstall 21.2.0 and reinstall it to correct the default application.
—
Adobe InDesign Team
-
[ID-4277180]InDesign v21.2.0.030 crashes on quit in SubProcess
Version of Adobe InDesign, InCopy or InDesign Server
Adobe InDesign 2026, Version 21.2.0.30 (Build 21200)
Running on macOS 26.2 (25C56) on Apple Silicon (Mac14,2, 16 GB RAM)
Steps to reproduce the issue
1. Launch Adobe InDesign 2026.
2. Open any document (or create a new blank document).
3. Work normally for a while, or even do nothing.
4. Choose “InDesign > Quit InDesign” or press Cmd+Q.
5. Confirm quitting if prompted.
Expected result
InDesign quits cleanly without any error message and returns to the macOS desktop.
Actual result
• InDesign crashes on quit every time.
• macOS shows a crash dialog stating that “Adobe InDesign 2026 quit unexpectedly” (or similar wording).
• The macOS crash report shows:
• Exception Type: EXC_CRASH (SIGABRT)
• Termination Reason: Namespace SIGNAL, Code 6, “Abort trap: 6”
• Crash is triggered in Thread 10.
• This happens even after:
• Resetting InDesign preferences on launch.
• Deleting InDesign caches and preference folders in the user Library.
• Completely uninstalling and reinstalling InDesign via Creative Cloud.
• Testing in a brand-new macOS user account.
Additional context
• The same InDesign version (21.2.0.30) on my previous Mac and macOS version did not show this problem; the issue started only after migrating to the new Mac (same InDesign version, newer macOS).
• No third‑party plug‑ins are installed (or all third‑party plug‑ins have been removed for testing).
• The crash occurs regardless of which document is open; even a new, empty document triggers the crash on quit.Version of Adobe InDesign, InCopy or InDesign Server
Adobe InDesign 2026, Version 21.2.0.30 (Build 21200)
Running on macOS 26.2 (25C56) on Apple Silicon (Mac14,2, 16 GB RAM)
Steps to reproduce the issue
1. Launch Adobe InDesign 2026.
2. Open any document (or create a new blank document).
3. Work normally for a while, or even do nothing.
4. Choose “InDesign > Quit InDesign” or press Cmd+Q.
5. Confirm quitting if prompted.
Expected result
InDesign quits cleanly without any error message and returns to the macOS desktop.
Actual result
• InDesign crashes on quit every time.
• macOS shows a crash…2 votesHi,
Thank you for reporting the issue. It is currently under investigation.
—
Adobe InDesign Team
-
Linked image within illustrator file not appearing when placed in indesign
Using:
InDesign 21.1
Link created in Illustrator 30.2.1I have a map created in Illustrator with a background (flattened) tiff which displays fine in Illustrator. Once placed into InDD, the tiff won't appear (layer is ON and printing) and doesn't get included in exports (thus eliminating a rendering issue of any kind).
This has happened on 2 separate files but is fine in others with the same set-up.
On occasion the tiff will reappear...
This is a recent 'development' in past 2 weeks.2 votes -
won't place images mac os tahoe
Mac OS Tahoe, INDD version 21.2 and can't place a jpg. That simple. Seems silly report. Files open, anc can't be modified, error here, error trying to close. But main problem, can't place a jpg.
2 votes -
close
Freezes when I try to close the program. It will either not close at all, no matter how many force stops/close buttons I hit, or it will completely crash instead of closing safely.
2 votes -
Automatic page number chapters don't work
I have an issue that I believe is common, and looks like a bug in InDesign. But automatic page numbering over chapters in a book doesn't work. I've tried all tips and tricks, until I found out that it is already logged by more people as a bug in the program. I just wonder if Adobe can fix this problem on short notice, as it appears to be there already for quite a while.
What appears to be the problem is that the next document page numbering just looks at the page range of the previous one, and page ranges reflect only the number of pages in the chapters. They do not reflect any page numbering.I have an issue that I believe is common, and looks like a bug in InDesign. But automatic page numbering over chapters in a book doesn't work. I've tried all tips and tricks, until I found out that it is already logged by more people as a bug in the program. I just wonder if Adobe can fix this problem on short notice, as it appears to be there already for quite a while.
What appears to be the problem is that the next document page numbering just looks at the page range of the previous one, and page ranges…2 votes -
Text whites out and becomes invisible while writing
I have 2 issues. 1. Since the newest update the program takes an extra long time to load when opening, and 2. the whole body of text turns invisible while writing, frequently and repeatedly. It's very disruptive and frustrating, as there is no sure way to get the text to become visible again. It does return to visibility after either typing, or using the space bar a number of times, but it just turns invisible nearly right away if not right away again. It's not unusable, but it is very unpleasant to use.
2 votes -
Continuous issues with 21.1 on Windows 11 - Won't Open/Crashing
Since updating to 21.1 (2026), I have to repair the Visual C++ Redistributables, restart, and then reset preferences with Shift+Ctrl+Alt just to get InDesign to open. Error OXC0000142. I have done this numerous times, and each week, I have to do it again.
It also has crashed my (and others on our team) computers which makes them boot into the BIOS to a Support Repair screen.
21.1 is near unusable at this point.
2 votes -
Severe InDesign Performance Issues
I’m reporting severe and ongoing performance problems with InDesign that are significantly affecting day-to-day work.
The application has become consistently slow and laggy during normal use — including delays when clicking, saving, zooming, switching pages, placing assets, and general UI responsiveness. At times, even simple actions take several seconds and the software feels almost unusable.
While performance is worse when working from Dropbox-synced folders, the same lag and delays also occur when working with files stored fully locally. This suggests the issue is not limited to cloud storage and may be a broader performance problem within InDesign itself.
This behavior is happening across regular production files and is causing major productivity loss for our workflow.
Please investigate and prioritize improvements to overall performance and stability. InDesign is currently much slower than other Adobe applications and has become difficult to use efficiently.
Thank you for your assistance.
NechamaI’m reporting severe and ongoing performance problems with InDesign that are significantly affecting day-to-day work.
The application has become consistently slow and laggy during normal use — including delays when clicking, saving, zooming, switching pages, placing assets, and general UI responsiveness. At times, even simple actions take several seconds and the software feels almost unusable.
While performance is worse when working from Dropbox-synced folders, the same lag and delays also occur when working with files stored fully locally. This suggests the issue is not limited to cloud storage and may be a broader performance problem within InDesign itself.
This behavior…
2 votes -
Batch HTML Export Crashes InDesign 21.1
Here is a (Gemini 3-assisted) report of an HTML export problem that is crashing InDesign consistently. It's somewhat urgent because crashing InDesign is not good for the nerves. Reverting to 21.0.1 permits the script to run to completion.
Bug Report: Regression in HTML Export Automation (dvacore::xml / AXE8)
Subject: InDesign 21.1 (and Prerelease) crashes with EXCEPTIONACCESSVIOLATION in dvacore::xml during iterative HTML Export scripting.
Summary: Automated workflows that iterate through documents to export HTML (ExportFormat.HTML) fail consistently after processing 2–5 files. The crash occurs during the document closure or immediate post-processing phase of the export. This is a regression. The identical script logic functioning on the same hardware/OS was stable in previous InDesign builds (v21.0) but now crashes 100% of the time in v21.1.0.56.
Environment:
Application: InDesign 2026 (21.1.0.56) & Prerelease (21.2) Build
OS: Windows 11 Pro (Build 26200)
Hardware: Intel Core i7-12700K, NVIDIA GeForce RTX 3090 (Driver 32.0.15.8157)
RAM: 64GB
Crash Signature: The crash consistently occurs in the dvacore module, specifically involving the Expat XML parser used during HTML generation.
• Exception: 0xc0000005 (ACCESSVIOLATION)
• Faulting Module: dvacore.dll
• Key Stack Symbols:
dvacore::xml::GetParser
AXE8ExpatTerminate (in AXE8SharedExpat.dll)
WCrashHandler::operator=
Steps to Reproduce:
Create a folder containing 5+ simple .indd documents of two to four pages in length.
Run the following ExtendScript (.jsx) to batch export them to HTML:
JavaScripttarget indesign
var folder = Folder.selectDialog("Select folder");
var files = folder.getFiles("*.indd");for (var i = 0; i < files.length; i++) {
var doc = app.open(files[i]);// Valid HTML export destination var htmlFile = new File(files[i].parent + "/" + files[i].name + ".html"); // Export doc.exportFile(ExportFormat.HTML, htmlFile); // Close Document doc.close(SaveOptions.NO);}
Observed Behavior:
• File 1: Exports successfully.
• File 2-3: InDesign crashes silently or throws the error report immediately upon calling doc.close() or starting the next app.open().
• Attempted Workarounds (All Failed):
Forcing Garbage Collection ($.gc()) between iterations.
Purging Caches (app.purge(PurgeOptions.ALLCACHES)).
Adding $.sleep(3000) delays to allow file locks to release.
Running in UserInteractionLevels.NEVERINTERACT vs INTERACTWITHALL.
Analysis: The stack trace showing AXE8_ExpatTerminate strongly suggests a race condition or resource leak in the HTML/XML subsystem. It appears the XML parser instance created for the first export is not being correctly destroyed or released by the time the script initiates the second export cycle. When the application attempts to re-engage dvacore::xml::GetParser, it hits invalid memory.
Impact: Batch automation for HTML outputs is currently impossible in v21.1 without restarting the application instance for every single document.Here is a (Gemini 3-assisted) report of an HTML export problem that is crashing InDesign consistently. It's somewhat urgent because crashing InDesign is not good for the nerves. Reverting to 21.0.1 permits the script to run to completion.
Bug Report: Regression in HTML Export Automation (dvacore::xml / AXE8)
Subject: InDesign 21.1 (and Prerelease) crashes with EXCEPTIONACCESSVIOLATION in dvacore::xml during iterative HTML Export scripting.
Summary: Automated workflows that iterate through documents to export HTML (ExportFormat.HTML) fail consistently after processing 2–5 files. The crash occurs during the document closure or immediate post-processing phase of the export. This is a regression.…2 votes -
Interactive Button
Why not allow the “Create Button” option to navigate to a specific page and be exported as an interactive PDF?
2 votes
- Don't see your idea?