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 ~
7722 results found
-
PDF export bug – Unicode character "ł" (U+0142) corrupts text encoding of the entire PDF
I have found a reproducible issue in Adobe InDesign affecting PDF export.
Environment
Adobe InDesign 2026
Mac OS Tahoe 26.1
Font: Univers Next Pro Condensed (locally installed, licensed version)Description
When exporting a PDF from InDesign, the presence of a single Polish lowercase letter ł (Unicode U+0142) causes the text encoding of the entire PDF to become corrupted.The document displays and prints correctly, but copying text from the exported PDF no longer works correctly:
accented characters such as é, è, à, ê, ç, etc. are copied as periods (".") or incorrect characters;
the problem affects the entire PDF, not only the word containing ł.Steps to reproduce
Create a new InDesign document.
Use Univers Next Pro Condensed.
Type the following text:
Libellułe
aeiéàè
Export the document as a PDF using the standard PDF export settings.
Open the PDF in Adobe Acrobat Reader.
Copy and paste the text into a text editor.Expected result
The copied text should exactly match the original text, including all accented characters and the Polish character ł.Actual result
The presence of the single character ł causes the PDF text encoding to become corrupted. Accented characters throughout the PDF are no longer copied correctly and are replaced by periods or incorrect characters.I have found a reproducible issue in Adobe InDesign affecting PDF export.
Environment
Adobe InDesign 2026
Mac OS Tahoe 26.1
Font: Univers Next Pro Condensed (locally installed, licensed version)Description
When exporting a PDF from InDesign, the presence of a single Polish lowercase letter ł (Unicode U+0142) causes the text encoding of the entire PDF to become corrupted.The document displays and prints correctly, but copying text from the exported PDF no longer works correctly:
accented characters such as é, è, à, ê, ç, etc. are copied as periods (".") or incorrect characters;
the problem affects the entire PDF, not…1 vote -
Microsoft Surface Laptop vergrößert alle Bedienelemente von InDesign weil InDesign denkt, es wäre ein Tablet (wegen dem Touch Panel)
Ich benutze ein Microsoft Surface Laptop 7 mit Qualcomm Plus ARM-Prozessor und die BETA-Version von InDesign. Beim Starten geht InDesign sofort in eine Touch-Oberfläche, weil es das Surface Laptop, das auch ein Touch-Display hat, fälschlicherweise als Tablet interpretiert. Dadurch sind alle Elemente um den Faktor ca. 500 vergrößert, so dass man keine Bedienelemente mehr erreichen kann und das lässt sich auch nicht abschalten. Ich habe eine KI gefragt, wie man das lösen könnte, aber alle Versuche scheiterten leider. Aus diesem Grund kann ich InDesign auf meinem neuen Surface Laptop nicht nutzen, obwohl ich es mir genau dafür für unterwegs gekauft hatte.
Könnten Sie bitte die Beta-Version von Indesign auch an das Surface Laptop von Microsoft anpassen, so dass es damit als ganz normales Laptop per Maus nutzbar ist?
Am besten wäre noch, wenn aus der Beta-version eine richtige Version für ARM-Prozessoren werden könnte.Vielen Dank und viele Grüße
Ich benutze ein Microsoft Surface Laptop 7 mit Qualcomm Plus ARM-Prozessor und die BETA-Version von InDesign. Beim Starten geht InDesign sofort in eine Touch-Oberfläche, weil es das Surface Laptop, das auch ein Touch-Display hat, fälschlicherweise als Tablet interpretiert. Dadurch sind alle Elemente um den Faktor ca. 500 vergrößert, so dass man keine Bedienelemente mehr erreichen kann und das lässt sich auch nicht abschalten. Ich habe eine KI gefragt, wie man das lösen könnte, aber alle Versuche scheiterten leider. Aus diesem Grund kann ich InDesign auf meinem neuen Surface Laptop nicht nutzen, obwohl ich es mir genau dafür für unterwegs gekauft…
1 vote -
Problème d'assemblage de polices : police National 2 + Monotype Connect
Problème d'assemblage sous Windows 11 : police National 2 + Monotype Connect
Configuration informatique (système et logiciels) :- InDesign 2026 v21.4.1
- Windows 11 24h2 Entreprise
- Monotype Connect 28.1.4
Reproduction du problème :
1 fichier InDesign utilisant des polices de la collection National 2 activées avec Monotype Connect, sous Windows.
Pas de problème sous macOS.Description du problème :
Quand on lance un assemblage en demandant la copie des polices, InDesign signale que les polices National 2 sont "incomplètes" et ne les regroupe pas dans l'assemblage final.
Le problème ne se produit que dans ces conditions :
- Pour l'assemblage InDesign uniquement. Sinon il n'y a aucun problème avec les autres fonctions d'InDesign (imprimer, générer un PDF ou exporter en général).
- Activation de la police National 2 avec Monotype Connect.
- Sous Windows uniquement.
Notes :
Si les polices sont activées sans Monotype Connect - installées sur le système ou placées dans un dossier "Document fonts" dans le même dossier que le fichier InDesign - aucun problème à l'assemblage.
Illustrator rencontre le même problème.
J'ai longuement dialogué avec le support Monotype. Nous avons fait plusieurs tests. Comme le problème ne concerne que l'assemblage d'InDesign et qu'il ne se produit que sous Windows, pour eux le problème ne vient pas de Connect mais de la version Windows d'InDesign.Je joins un fichier InDesign mais je ne peux déposer des fichiers zip ou des polices.
Problème d'assemblage sous Windows 11 : police National 2 + Monotype Connect
Configuration informatique (système et logiciels) :- InDesign 2026 v21.4.1
- Windows 11 24h2 Entreprise
- Monotype Connect 28.1.4
Reproduction du problème :
1 fichier InDesign utilisant des polices de la collection National 2 activées avec Monotype Connect, sous Windows.
Pas de problème sous macOS.Description du problème :
Quand on lance un assemblage en demandant la copie des polices, InDesign signale que les polices National 2 sont "incomplètes" et ne les regroupe pas dans l'assemblage final.
Le problème ne se produit que dans ces conditions :
- Pour l'assemblage InDesign uniquement.…
1 vote -
Export to interactive pdf option to view pdf greyed out in mac
I noticed yesterday 7/8/26 that the menu for export to interactive pdf has "view pdf after export" greyed out. It does work when I switch to the print pdf menu, so it's not a problem with acrobat or my Finder trying to use preview instead of acrobat.
1 vote -
Bug: Shift + 1 = bold paragraph instead of an exclamation point. So there is no way to type an exclaimation point right now in InDesign
I have InDesign 21.3 x64. Currently, there is no way to type an exclamation point. When you use the Shift key + the number 1, it will bold the paragraph instead of giving you an exclamation point.
1 vote -
‘Rows and Columns’ function still not included under ‘Cell styles’
Why is the ‘Rows and Columns’ function still not included under ‘Cell styles’? You cannot set the cell height and have to enter it manually for each individual cell.
1 vote -
Linear B
Character “Linear B Syllable B008 A” (Unicode U+10000) doesn’t display properly, no matter which font is used.
I have tried using Noto Sans Linear B, Code 2001, and a few of the Kurinto fonts. Either nothing is displayed, or there is a rectangle meaning the glyph is not available. However, the glyph displays properly in the font list, but not in a text box.
Attached are two screenshots, one from InDesign where the glyph doesn’t display properly, and one from Illustrator where it does work fine.
I do realize I’m probably the only person using these glyphs! LOL!
1 vote -
Pasteboard color
Since the last update 2026, all documents with custom preview pasteboard colour (I prefer a dark gray) revert to the standard light gray pasteboard colour.
Also: when changing the custom pasteboard colour I get a long list of standard colors with the custom colour on the bottom of the list, why such a long list and why not put custom on top in pop-up menu?
1 vote -
Data Merge randomly exports identical vector document 10x larger (Content Streams duplicated)
I believe I have found a reproducible bug in the InDesign PDF export engine.
Environment
InDesign 21.4.1
PDF Compatibility: Acrobat 5 (PDF 1.4)
Data Merge document
Approximately 200 records (400 pages)Expected behaviour
Exporting the same document repeatedly should always generate a PDF of approximately the same size.
Actual behaviour
The same document, exported multiple times using exactly the same PDF preset, randomly produces either:
a normal PDF (around 3–5 MB), or
a much larger PDF (30–50 MB).No document changes are made between exports.
Important observations
Both PDFs are fully vector.
No images are rasterized.
Acrobat PDF Optimizer reports that almost all additional size comes from Content Streams.
Fonts contribute almost nothing.
Images contribute almost nothing.
Metadata is negligible.Already tested
Linked Illustrator artwork replaced with linked PDF.
Artwork simplified.
No transparency.
No text stroke.
No appearance effects.
Saved as IDML and rebuilt.
New document created from IDML.
Same Data Merge source.
Same PDF preset.The behaviour remains random.
Additional information
I have other Data Merge jobs with 1000 records that consistently export to 3–5 MB.
This specific job, with only 200 records, randomly exports between 5 MB and 47 MB.
I can provide:
INDD
IDML
source artwork
good PDF
bad PDFgenerated from the same document.
I believe I have found a reproducible bug in the InDesign PDF export engine.
Environment
InDesign 21.4.1
PDF Compatibility: Acrobat 5 (PDF 1.4)
Data Merge document
Approximately 200 records (400 pages)Expected behaviour
Exporting the same document repeatedly should always generate a PDF of approximately the same size.
Actual behaviour
The same document, exported multiple times using exactly the same PDF preset, randomly produces either:
a normal PDF (around 3–5 MB), or
a much larger PDF (30–50 MB).No document changes are made between exports.
Important observations
Both PDFs are fully vector.
No images are rasterized.
Acrobat PDF Optimizer reports…1 vote -
Flex Layout structure in anchored object lost on IDML/ICML round-trip
Version
Adobe InDesign 21.4.1, macOS 26.5.1Steps to reproduce
Create a Flex Layout in InDesign.
Anchor the Flex Layout to text as an anchored object.
Save the document as IDML, or export the story containing the Flex Layout as ICML.
Either reopen the saved IDML file, place the exported ICML file into a new InDesign document, or edit the ICML file in InCopy and refresh the link in InDesign.Expected result
The Flex Layout should appear identical to the original document.Actual result
The Flex Layout structure is lost entirely. The contents of text frames that were part of the Flex Layout is merged and appended at the end of the text.
Version
Adobe InDesign 21.4.1, macOS 26.5.1Steps to reproduce
Create a Flex Layout in InDesign.
Anchor the Flex Layout to text as an anchored object.
Save the document as IDML, or export the story containing the Flex Layout as ICML.
Either reopen the saved IDML file, place the exported ICML file into a new InDesign document, or edit the ICML file in InCopy and refresh the link in InDesign.Expected result
The Flex Layout should appear identical to the original document.Actual result
The Flex Layout structure is lost entirely. The contents of text frames that were part of the…
1 vote -
Big size linked pictures
The new versions of InDesign (21.3–21.4.1) cannot export files if a linked image is large (more than 1 GB). When exporting to PDF, only a gray square appears, and the JPG export is empty. The last working version is 21.2.
1 vote -
Big size pictures
The new versions of InDesign (21.3–21.4.1) cannot export files if a linked image is large (more than 1 GB). When exporting to PDF, only a gray square appears, and the JPG export is empty. The last working version is 21.2.
1 vote -
Severe image rendering corruption in InDesign on MacBook Pro M4 after macOS update
Description:
I am experiencing intermittent but repeatable image rendering corruption in Adobe InDesign on a brand-new 14-inch MacBook Pro (M4).
Symptoms:
Linked raster images (JPEG/PNG/PSD) initially display correctly.
After a short period of working, the images become corrupted on screen.
The corruption appears as vertical coloured lines, stretched pixels and black areas replacing the image content.
Vector objects and text remain unaffected.
The corruption affects multiple placed images within the document.
Relinking the affected image restores it temporarily, but the corruption returns.
The issue occurs across multiple InDesign documents.Additional observations:
Photoshop has also displayed occasional graphical glitches.
The issue started after installing the latest macOS update.
GPU Performance has been disabled in InDesign with no improvement.
Adobe Creative Cloud, InDesign and Photoshop are fully up to date.
Files are stored on the internal SSD (not an external drive or cloud storage).
Projects are packaged with local linked assets.
Exported PDFs appear normalHardware:
MacBook Pro 14-inch M4
Apple silicon
Latest version of macOSDiagnostics already completed:
Apple Mac Resource Inspector — Passed
Apple Display Anomalies — Passed
No hardware faults detected.Request:
Could you advise whether this is a known compatibility issue between the latest version of macOS and InDesign, or if there are additional graphics-related settings or patches I should apply?Description:
I am experiencing intermittent but repeatable image rendering corruption in Adobe InDesign on a brand-new 14-inch MacBook Pro (M4).
Symptoms:
Linked raster images (JPEG/PNG/PSD) initially display correctly.
After a short period of working, the images become corrupted on screen.
The corruption appears as vertical coloured lines, stretched pixels and black areas replacing the image content.
Vector objects and text remain unaffected.
The corruption affects multiple placed images within the document.
Relinking the affected image restores it temporarily, but the corruption returns.
The issue occurs across multiple InDesign documents.Additional observations:
Photoshop has also displayed occasional graphical glitches.
The issue…1 vote -
Large Hourglass and frozen file:
I used Gemini to generate an image using a separate device, then imported it to InDesign then Indesign reacted weird. The new Alt Text recognized the image was Gemini and there was a weird link icon and then an Alt Design icon and a 1" hourglass appeared and I could not do anything. Now my whole file is gone and wont open.
1 vote -
Reading order of tagged PDF elements is unstable and resets when new elements are added
Description:
SummaryWhen creating an accessible tagged PDF from InDesign, the reading order of elements in the exported PDF becomes unstable and incorrect whenever new elements are added to an existing document. The only reliable workaround is to rebuild the document from scratch with elements placed in the correct reading order from the beginning.
Steps to reproduce
- Create an InDesign document with interactive form fields (text inputs and checkboxes).
- Set the reading order using the Articles panel ("Use for PDF tagging order").
- Export to tagged PDF and verify reading order with a screen reader — order is correct.
- Add new elements (e.g. additional checkboxes or text frames) to the existing document.
- Export again and test with a screen reader.
Expected behavior
The reading order should remain consistent and follow the Articles panel order, even after new elements are added.
Actual behaviorInDesign appears to apply a mix of element creation order, Articles panel order, and Tab order (keyboard navigation), producing an unpredictable result in the exported PDF. In our case, the screen reader jumped from form fields to the logo and protocol number before returning to the correct sequence.
Workaround
Create a new blank InDesign document and paste all elements in the correct reading order. This produces a correct result, but the fix must be reapplied every time structural changes are made to the document.
EnvironmentVersion Adobe InDesign: 2026
Verified with: screen reader testing conducted with a blind user using JAWS and NVDA; also verified via Adobe Acrobat accessibility checker and keyboard navigation (Tab key).Impact
This issue significantly affects accessible PDF production workflows. Any document update requires a full rebuild of element order, which is not sustainable for documents that undergo frequent revisions.
Description:
SummaryWhen creating an accessible tagged PDF from InDesign, the reading order of elements in the exported PDF becomes unstable and incorrect whenever new elements are added to an existing document. The only reliable workaround is to rebuild the document from scratch with elements placed in the correct reading order from the beginning.
Steps to reproduce
- Create an InDesign document with interactive form fields (text inputs and checkboxes).
- Set the reading order using the Articles panel ("Use for PDF tagging order").
- Export to tagged PDF and verify reading order with a screen reader — order is correct.
- Add new…
1 vote -
Onderwerp: Bug-/bruikbaarheidsrapport: Adobe Fonts veroorzaken conflicten met lokale systeemlettertypen in InDesign
Onderwerp: Bug-/bruikbaarheidsrapport: Adobe Fonts veroorzaken conflicten met lokale systeemlettertypen in InDesign
Aan het Adobe InDesign Product Team,
Ik wil een probleem melden met betrekking tot de manier waarop Adobe InDesign en Creative Cloud omgaan met standaard Windows-systeemlettertypen, zoals Roboto.
Het probleem
Wanneer een InDesign-document wordt geopend dat is gemaakt op een ander systeem, uit een pakketbestand komt of een andere versie van hetzelfde lettertype gebruikt, meldt InDesign regelmatig dat Roboto ontbreekt, terwijl de lokale Windows-versie gewoon is geïnstalleerd en actief is.
Creative Cloud probeert vervolgens automatisch een Adobe Fonts-versie van hetzelfde lettertype te synchroniseren. Hoewel de naam identiek is, betreft dit vaak een andere fontbron of een ander bestandsformaat (bijvoorbeeld OpenType in plaats van TrueType of een andere leverancier).
Het gevolg
Deze automatische synchronisatie veroorzaakt direct een lettertypeconflict. Creative Cloud meldt dat een lettertype met dezelfde naam al op het systeem aanwezig is, terwijl InDesign het lokale lettertype toch als "ontbrekend" blijft beschouwen.
Dit leidt tot:
• onterechte meldingen over ontbrekende lettertypen;
• conflicten tussen lokale en Adobe Fonts-versies;
• onnodige lettertypevervanging;
• verbroken stijlkoppelingen;
• inconsistente typografie binnen bestaande documenten.
Gewenste oplossing
InDesign zou eerst de lokaal geïnstalleerde systeemlettertypen moeten controleren voordat Adobe Fonts automatisch wordt geactiveerd.
Wanneer een lokaal lettertype dezelfde familie- en stijlnamen bezit als het gevraagde lettertype, zou InDesign deze automatisch moeten koppelen in plaats van een cloudversie te downloaden.
Met andere woorden:
• geef lokale systeemlettertypen prioriteit boven Adobe Fonts;
• verbeter de font-matching zodat identieke families van verschillende leveranciers als compatibel worden herkend wanneer de metrische eigenschappen overeenkomen;
• voorkom automatische synchronisatie wanneer al een geschikte lokale versie beschikbaar is.
Hiermee worden onterechte meldingen over ontbrekende lettertypen voorkomen en blijven bestaande documenten stabiel en consistent.
Hartelijk dank voor uw aandacht. Ik hoop dat dit probleem in een toekomstige update van InDesign wordt opgelost.Onderwerp: Bug-/bruikbaarheidsrapport: Adobe Fonts veroorzaken conflicten met lokale systeemlettertypen in InDesign
Aan het Adobe InDesign Product Team,
Ik wil een probleem melden met betrekking tot de manier waarop Adobe InDesign en Creative Cloud omgaan met standaard Windows-systeemlettertypen, zoals Roboto.
Het probleem
Wanneer een InDesign-document wordt geopend dat is gemaakt op een ander systeem, uit een pakketbestand komt of een andere versie van hetzelfde lettertype gebruikt, meldt InDesign regelmatig dat Roboto ontbreekt, terwijl de lokale Windows-versie gewoon is geïnstalleerd en actief is.
Creative Cloud probeert vervolgens automatisch een Adobe Fonts-versie van hetzelfde lettertype te synchroniseren. Hoewel de naam identiek is, betreft…1 vote -
When I import PDF comments into a document, the application slows dow
I am writing to report a recurring performance issue in Adobe InDesign.
Issue description:
When I import PDF comments into a document, the application slows down significantly, making it almost impossible to work. As soon as I delete the imported comments, InDesign immediately returns to its normal, smooth performance.This exact bug occurred in the past, but it was fixed in one of the subsequent updates. Unfortunately, the issue has reappeared in the latest version, making this functionality completely unusable for me at the moment.
1 vote -
PNG ICC Profile export
InDesign 21.2 PNG export does not embed RGB ICC profile
Version:
Adobe InDesign 2026 (21.2)Operating System:
macOS Sequoia 15.3.1Steps to reproduce:
- Create a new RGB document.
- Assign Adobe RGB (1998) as the document RGB profile.
- Set Transparency Blend Space to Document RGB.
- Place RGB images or use RGB fills.
- Export using File > Export > PNG.
- Open the PNG in Adobe Photoshop.
Expected result:
The exported PNG should contain an embedded RGB ICC profile (or provide an option to embed one), consistent with the document profile.
Actual result:
The exported PNG contains no embedded RGB profile. Photoshop displays a “Missing Profile” dialog when opening the PNG.
The same document exported as JPEG with “Embed Colour Profile” enabled correctly embeds the Adobe RGB profile and opens in Photoshop without a Missing Profile warning.
Additional information:
- RGB document
- Adobe RGB (1998) working space
- Adobe RGB assigned profile
- Transparency Blend Space = Document RGB
- All linked assets are RGB
- Behaviour is reproducible with multiple documents.
InDesign 21.2 PNG export does not embed RGB ICC profile
Version:
Adobe InDesign 2026 (21.2)Operating System:
macOS Sequoia 15.3.1Steps to reproduce:
- Create a new RGB document.
- Assign Adobe RGB (1998) as the document RGB profile.
- Set Transparency Blend Space to Document RGB.
- Place RGB images or use RGB fills.
- Export using File > Export > PNG.
- Open the PNG in Adobe Photoshop.
Expected result:
The exported PNG should contain an embedded RGB ICC profile (or provide an option to embed one), consistent with the document profile.
Actual result:
The exported PNG contains no embedded RGB profile. Photoshop displays…
1 vote -
macOS system fonts in older documents
When opening documents in 21.4.1.4 that were created in a version < 21.4 and that use macOS system fonts, those system fonts show as
<Font Status="NotAvailable"/>in IDML exported from 21.4., and asFontStatus.NOT_AVAILABLEfrom the ExtendScript interface. They look installed and normal in Find/Replace Font.... Doing things to try to trigger a refresh, likeapp.updateFonts(), or typing inside a range of text in the document that uses the font, does not fix it; round-tripping IDML does.This affects some of our automated workflows.
I'm not sure if this happens with every macOS system font, but I have seen it with more than one. The attached document, saved in 21.3, uses Avenir.
I would suspect that this problem was introduced by the fix for [ID-4272938] After installing a Windows 11 update, InDesign is unable to find the Times New Roman and Calibri fonts
When opening documents in 21.4.1.4 that were created in a version < 21.4 and that use macOS system fonts, those system fonts show as
<Font Status="NotAvailable"/>in IDML exported from 21.4., and asFontStatus.NOT_AVAILABLEfrom the ExtendScript interface. They look installed and normal in Find/Replace Font.... Doing things to try to trigger a refresh, likeapp.updateFonts(), or typing inside a range of text in the document that uses the font, does not fix it; round-tripping IDML does.This affects some of our automated workflows.
I'm not sure if this happens with every macOS system font, but I have…
1 vote -
Report Offensive Symbols
Reporting the font Baloo 2. When scrolling through the symbols to replace a bullet point, I noticed an offensive and antisemitic symbol at the bottom of the list that needs to be addressed! I was using InDesign when I discovered this, but because it looks like it's built into the font family, this is a font issue. Please address this immediately as it's incredibly offensive, harmful and creates an unsafe environment. Please investigate other fonts as well to ensure the symbol doesn't apply in other fonts. I am not comfortable posting a photo as it is harmful content. If this is not the right area to report this, please provide me the correct link or email and I will send it there. Thank you!
Reporting the font Baloo 2. When scrolling through the symbols to replace a bullet point, I noticed an offensive and antisemitic symbol at the bottom of the list that needs to be addressed! I was using InDesign when I discovered this, but because it looks like it's built into the font family, this is a font issue. Please address this immediately as it's incredibly offensive, harmful and creates an unsafe environment. Please investigate other fonts as well to ensure the symbol doesn't apply in other fonts. I am not comfortable posting a photo as it is harmful content. If this…
1 vote
- Don't see your idea?