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 ~
7504 results found
-
InDesign – open dialog – file types selection – INDD, PDF
I am used to InDeign allowing me to open ONLY native files. I always keep InDesign files with pdf-s (named exactly the same) in one folder. Since InDesign is able to open / convert pdf files I often open pdf instead of indesign file, which makes my job much harder and more frustrating, than it needs to be.
Problem is that in file types section of the dialog I cannot select only indd files (which should be default option). Please, fix it! Thanks!!!
1 vote -
Critical workflow break: period in filename makes Save As unusable after Tahoe upgrade — no workaround
Area: macOS 26 Tahoe – Save / Export Dialog with Indesign
Summary:
In macOS 26 Tahoe, the Save As filename field does not pre-populate when opening a Save As or Export dialog in Adobe InDesign. When manually retyping the filename, if the name contains a period followed by a space, the entire field is cleared the moment the space is typed. This does not happen with filenames that contain no period. No known workaround resolves this.Steps to reproduce:
1. Open a document in Adobe InDesign whose filename contains a period (e.g. "April 12.26Quarter Page HorSN.indd")
2. Go to File > Export or File > Save As
3. Observe that the Save As field is blank — the filename is not pre-populated
4. Begin manually retyping the filename, including a period (e.g. type "April 12.26")
5. Type a space after the period
6. The entire contents of the Save As field are immediately erasedAdditional reproduction path (no workaround exists):
Even when clicking directly on the original InDesign file in the Save As dialog to repopulate the filename field, the bug persists. As soon as any character is typed at the end of the pre-filled name (e.g. typing "" to append "Proof"), the entire filename is instantly wiped. Because every file in our workflow contains a period (we date all files using a month.year format, e.g. "4.26"), there is no way to avoid triggering this bug. Every save attempt is affected.Expected behavior:
- The Save As field should pre-populate with the current document filename
- A period followed by any character should be valid input in a filename field
- Appending characters to a pre-filled filename should not clear the field
- This worked correctly on macOS 15 Sequoia and earlierActual behavior:
- Save As field opens blank regardless of the current document name
- Typing a period followed by a space clears the entire field
- Clicking the file to repopulate the field and then typing any character also clears the field
- This only occurs when the filename contains a period — filenames without a period are unaffectedAdditional observation:
The bug appears to be isolated to filenames containing a period. This suggests macOS may be misinterpreting the period as a file extension delimiter and rejecting any character that follows as invalid, causing it to reset the entire field.Impact:
This is a critical workflow disruption. All of our work files use a month.year date format (e.g. "4.26") in the filename, meaning 100% of saves are affected with no viable workaround. Tasks that previously took minutes are now taking three times longer. This issue began immediately after updating to macOS Tahoe two days ago and has been unresolvable since.Comparative note:
Colleagues who received new Macs with Tahoe pre-installed are not experiencing this issue. It appears to affect Macs that were upgraded to Tahoe from a prior macOS version, suggesting the bug may be tied to the upgrade path rather than Tahoe itself.Environment:
- macOS: 26 Tahoe (upgraded from macOS 15 Sequoia)
- Hardware: MacBook Pro M3 Pro
- App affected: Adobe InDesign 2026 (also reported in Illustrator and Acrobat)Notes:
This has been widely reported in Adobe's community forums since Tahoe's release in September 2025 and remains unresolved as of April 2026. Because the issue occurs across multiple Adobe apps, it appears to be a macOS-level bug in the system Save dialog rather than an app-specific issue.I've included a screen recording of this example being exported. Note that I am NOT hitting the "delete" button. I'm hitting the space bar and then in the second attempt I'm trying to type an underscore to save another version of the file in the folder.
Area: macOS 26 Tahoe – Save / Export Dialog with Indesign
Summary:
In macOS 26 Tahoe, the Save As filename field does not pre-populate when opening a Save As or Export dialog in Adobe InDesign. When manually retyping the filename, if the name contains a period followed by a space, the entire field is cleared the moment the space is typed. This does not happen with filenames that contain no period. No known workaround resolves this.Steps to reproduce:
1. Open a document in Adobe InDesign whose filename contains a period (e.g. "April 12.26Quarter Page HorSN.indd")
2. Go…1 vote -
Bloqueo congelamiento.
Indesing es una porquería de app, se para colgando, no permite que se grabe y cuando se reinicia se han borrado todos los trabajos. Aprendan a hacer bien un programa ¡Inútiles!
1 vote -
**Title:** Grayscale TIFF colorization exports low-resolution unless transparency is forced (InDesign 21.3 / macOS 26.4) **Environment:*
Grayscale TIFF colorization exports as low-resolution unless transparency is forced (InDesign 21.3 / macOS 26.4)
Environment:
- InDesign version: 21.3
- macOS version: 26.4 (build 25E246)
- Hardware: Mac (Apple Silicon, exact model available on request)
- PDF export presets tested: High Quality Print, custom (no compression), PDF 1.3–1.8
- GPU on/off tested
Description of the issue:
Grayscale TIFF images placed in InDesign and colorized using the InDesign color tools export as visibly pixelated (low-resolution) in PDF.
- The source images are high-resolution and correctly linked
- The display in InDesign (high quality preview) is perfectly sharp
- The issue appears only after PDF export
- RGB/JPEG images do not show this problem
Key observation:
The issue disappears when transparency is introduced in the layout.
In my case, applying a white rectangle over the page with blending mode set to “Multiply” forces correct rendering of all affected images.
This suggests that:
- When no transparency is present → InDesign uses a rendering path that rasterizes colorized grayscale images at low resolution
- When transparency is present → a different rendering pipeline is used, producing correct high-resolution output
Conclusion:
This behavior strongly indicates a bug in the non-transparency rendering pipeline, specifically affecting:
- grayscale TIFF images
- colorized in InDesign
Additional issue (performance / thermal behavior):
Since recent versions of InDesign (including 21.3), the application systematically triggers high CPU usage, causing:
- constant activation of cooling fans
- noticeable system heat, even on relatively simple documents
This behavior appears abnormal compared to previous versions and may indicate a performance regression.
Expected behavior:
- Consistent high-resolution output regardless of transparency presence
- No need for artificial transparency to obtain correct rendering
- Stable CPU usage during standard layout and export operations
Workaround:
- Forcing transparency globally (e.g. overlay with Multiply blending mode) resolves the issue
- However, this is not a viable long-term production workflow, especially for complex layered documents
Request:
Please investigate:
- The rendering difference between transparency and non-transparency pipelines
- The rasterization behavior of colorized grayscale images
- The recent increase in CPU usage and thermal load
I can provide sample files if needed.
Grayscale TIFF colorization exports as low-resolution unless transparency is forced (InDesign 21.3 / macOS 26.4)
Environment:
- InDesign version: 21.3
- macOS version: 26.4 (build 25E246)
- Hardware: Mac (Apple Silicon, exact model available on request)
- PDF export presets tested: High Quality Print, custom (no compression), PDF 1.3–1.8
- GPU on/off tested
Description of the issue:
Grayscale TIFF images placed in InDesign and colorized using the InDesign color tools export as visibly pixelated (low-resolution) in PDF.
- The source images are high-resolution and correctly linked
- The display in InDesign (high quality preview) is perfectly sharp
- The issue appears only after PDF export
- RGB/JPEG images do…
1 vote -
In InDesign 2025 (version 20.5.2) and InDesign 2026 (version 21.3), when packaging a document, composite fonts and Japanese-language fonts a
OS: macOS 15.7.4
Version: InDesign 2025 (20.5.2) and InDesign 2026 (21.3)In all versions up to and including InDesign 2024, only Latin (Western) fonts were subject to collection during packaging. However, from InDesign 2025 onwards through the current version, Japanese-language fonts and composite fonts are also being collected during the packaging process. This requires us to manually remove the relevant files from the package folder each time, resulting in a significant and recurring burden on our workflow.
Furthermore, because composite fonts are being collected as font files, an alert indicating that the fonts cannot be found is displayed every time the packaged document is opened, further degrading operational efficiency.
This issue is not merely a matter of human error; it carries potential legal implications concerning font licensing rights, and we strongly urge that it be addressed as a matter of urgency.
If this represents an intentional change in product behavior, it was implemented without any prior notice or communication to users. Combined with recent incidents — including the unauthorized modification of the hosts file and the repositioning of the Save/Don't Save button — this pattern of changes reflects what we can only describe as a disregard for the user experience, and we cannot overlook it.OS: macOS 15.7.4
Version: InDesign 2025 (20.5.2) and InDesign 2026 (21.3)In all versions up to and including InDesign 2024, only Latin (Western) fonts were subject to collection during packaging. However, from InDesign 2025 onwards through the current version, Japanese-language fonts and composite fonts are also being collected during the packaging process. This requires us to manually remove the relevant files from the package folder each time, resulting in a significant and recurring burden on our workflow.
Furthermore, because composite fonts are being collected as font files, an alert indicating that the fonts cannot be found is displayed every time…1 vote -
CC Library window appears distorted and stretched
I noticed that the CC Library window is sometimes stretched or distorted up to a point where it's not readable. Especially when combined with other tools or re-arranged in own workspace this happens.
1 vote -
paragraph shading where inline table is used #2
As a way to attract focus to a bug-story that is almost 6 year old and unsolved but to me and a few other professionals very important bug.
I added some screenshots there
1 vote -
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.
1 vote -
Linked Illustrator Files Not Displaying Correctly in InDesign
We are experiencing an issue where Illustrator (.ai) files with linked assets are not displayed correctly when placed in InDesign.
InDesign does not properly render or recognize the linked content inside the Illustrator file, which affects preview and output accuracy. Currently, the only workaround is to embed all links in Illustrator before placing the file, which increases file size and slows down the workflow.
Please advise if there is a fix or recommended workflow for handling linked assets between Illustrator and InDesign.
1 vote -
In v 21.3, shift and control shift don't work with arrow keys to nudge in larger or smaller increments
In InDesign v 21.3, my arrow keys work to nudge elements in 1 px increments, but I'm not able to nudge in larger or smaller increments. When I hold the shift key and press the arrow to nudge 10px, nothing happens. When I hold the shift and control keys and press the arrows to nudge .01 px, nothing happens. This feature works fine in InDesign v 20 and Illustrator v 30.3. I'm surrently running v 20 to avoid this issue.
1 vote -
[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.1 voteClosed: 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
-
links
In InDesign 2026 21.2, when opening an .indd document in a package folder, the links cannot be found in the Links folder, even though it is in the correct location.
Opening the .idml file in InDesign 2026 21.2 works.
Opening the .idml file in InDesign 2025 20.5.2 works normaly, and saving the document as .indd from InDesign 2025 and then opening it in InDesign 2026 works again.
This is therefore a serious bug in InDesign 2026.1 vote -
Multiframe – incorrect resizing when view is rotated
Create frame: 20 × 20 mm.
Use “Step and Repeat” to duplicate them 5 times horizontally.
Rotate the view by 90 degrees.
Select all frames (in rotate view: width: 20 mm, height: 100 mm)
Try to change their width to 30 mm
3. Expected width: 30 mm, height: 100 mm
4. Result: width: 20 mm, height: 30 mm1 vote -
In Indesign v. 21.3 bug in the Flex Layout feature are cut letters with overhanging elements
In InDesign v. 21.3, there's a bug in the Flex Layout feature. Letters with overhanging elements are cut off when printed and in the preview
1 vote -
Unresponsive Panel Icons & Graphical Overlap when Importing Illustrator Files
- Panel UI Issue:
Issue: Double-clicking icons in the collapsed right panel does not activate them. Shortcuts also fail to open the panels.
Current Workaround: Panels only open when clicking the small '<<' (Expand) icon at the top of the dock.
- Illustrator Import/Update Issue:
Issue: When importing or updating an .ai file, InDesign occasionally displays a "ghost" image where the previous version and the updated version overlap.
Current Workaround: I have to delete the link and re-import the file from scratch to fix the display.
Environment:
OS: Windows 11 (또는 사용 중인 OS)
1 vote -
Find Change
Find and change no longer offers just to find and change something within a story (text box) - if shows either Search: Document or Search: All Documents, whereas previously it would additionally show Search: Selected text, and Search: Story.
This is a major problem.1 vote -
colore del testo
il nuovo testo che si inserisce non è in colore nero ma in colore registro
1 vote -
FRONTE E RETRO
IN FASE DI STAMPA FRONTE E RETRO IL RETRO LO CAPOVOLGE
1 vote -
Inconsistent metadata display for Photoshop EPS vs TIFF in Links panel
When placing raster images exported from Photoshop into InDesign, there is inconsistent metadata shown in the Links panel between TIFF and Photoshop EPS formats.
Using the same source image exported as both TIFF and EPS (CMYK), InDesign displays full image metadata for the TIFF (including Actual PPI, Effective PPI, dimensions, ICC profile, and transparency), while the EPS only shows basic file information and omits all image-specific data.
Since the EPS in this case is a raster image generated by Photoshop as supported natively by InDesign, it should be interpreted similarly to TIFF and expose the same metadata. I remember this being the case many years ago in older versions of Adobe InDesign.
This inconsistency makes it difficult to verify image quality (e.g. resolution) and creates confusion in print workflows.
When placing raster images exported from Photoshop into InDesign, there is inconsistent metadata shown in the Links panel between TIFF and Photoshop EPS formats.
Using the same source image exported as both TIFF and EPS (CMYK), InDesign displays full image metadata for the TIFF (including Actual PPI, Effective PPI, dimensions, ICC profile, and transparency), while the EPS only shows basic file information and omits all image-specific data.
Since the EPS in this case is a raster image generated by Photoshop as supported natively by InDesign, it should be interpreted similarly to TIFF and expose the same metadata. I remember this…
1 vote -
Myriad VF has a taller Ascent Baseline than Myriad Pro
Myriad VF is supposed to be a variable version of Myriad Pro, so I was trying to use it in tandem/to replace Myriad Pro in the document I am working on. The huge problem is, for some reason the Ascent Baseline on Myriad VF is much taller than it should be, which then when I try to replace the font, it completely messes up everything.
I also have Myriad Variable Concept on my computer, (which is apparently supposed to only show up in Illustrator, or something? But it shows up in InDesign for me.) And it properly matches the Ascent baseline of Myriad Pro.
All 3 of them match on every baseline except Ascent too, so I’m thinking this is a bug. It only seems to effect things in InDesign, I’m not getting any misalignment in Photoshop or Illustrator, but I’m also not seeing all the same text box options in those programs that InDesign gives.
Myriad VF is supposed to be a variable version of Myriad Pro, so I was trying to use it in tandem/to replace Myriad Pro in the document I am working on. The huge problem is, for some reason the Ascent Baseline on Myriad VF is much taller than it should be, which then when I try to replace the font, it completely messes up everything.
I also have Myriad Variable Concept on my computer, (which is apparently supposed to only show up in Illustrator, or something? But it shows up in InDesign for me.) And it properly matches the Ascent…
1 vote
- Don't see your idea?