Skip to content

Adobe InDesign: Bugs

When filing a new bug, please provide:

  1. Version of Adobe InDesign, InCopy or InDesign Server
  2. Steps to reproduce the issues
  3. Expected result
  4. Actual result
  5. Test file, screenshot, video or GIF capturing the issue (optional)
If you are facing a crash in InDesign, please submit the crash report as well. How to Submit Crash Report
Join the InDesign Prerelease Program to try out the new features and the bug fixes that are available in beta builds.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

221 results found

  1. [ID-4236366]Scripts using BridgeTalk do not work on M1 Macs (regardless of CC version)

    ID version: InDesign CC 2021 (16.3.2)
    OS: macOS Big Sur 11.5.2
    Processor: Apple M1

    When I try to run a script that uses BridgeTalk and works with Photoshop, it does not work.
    Also, a simple script using BridgeTalk will not work as well.
    Those scripts do work in CC 2021 on Intel Mac and macOS Big Sur 11.5.2.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Scripting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. [ID-4250752][MAC]Page numbers cut-off in Page panel when viewing in Horizontal mode

    Currently on Mac OS Big Sur using inDesign 16.1

    When viewing the pages panel in horizontal view and the page count exceeds what the panel can hold the scroll bars appear but then the last row of pages seem to have their page numbers hidden behind the UI and are not visible no matter how much you move the scroll bars down.

    I have seen this behavior since inDesign 15 on Mac OS Catalina.

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Crash while export to JPG

    indesign 16.2 (mac version) crashes every time exports jpg and it tries to overwrite existent jpg

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. WorldReady settings go missing in [Basic Paragraph] style

    Adobe InDesign (ME) 2021, 2020, CC 2019, ..., CS6
    macOS and Windows

    InDesign's WorldReady settings (Paragraph Direction, Kashidas, etc.) are being stripped from a document's [No Paragraph Style] style when opened on a machine with a missing 3rd-party plug-in (like Em Software's InCatalog). This appears to happen with any 3rd-party plug-in that adds a text attribute with a prefix that's lower than the WorldReady plug-in's prefix. While the following steps use the Middle Eastern app (English Arabic), where there's a UI to see the style's empty/blank WorldReady entries, we've confirmed that this problem affects all app variants (including English (Roman)).

    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Find/Change Text dialog does not show all Search options.

    after making a selection, the Find/Change text dialog sometimes does not offer Selection in the Search dropdown. It will be present under GREP and Object, but not Text and Glyph. Closing/reopening Find/Change does not fix it. Restarting InDesign usually fixes it...until it goes missing again.

    40 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. [ID-4261011] In Find/Change, search for font style (eg "Book") incorrectly selects "Regular" style text, even if "Book" style isn't present

    In InDesign 2021 (the latest version both on Mac and Windows), I add a text frame and fill it with placeholder text which is set, by default, to Minion Pro - Regular.
    Then I go to the find-change dialog box and set 'find format > basic character format > font style' to Book.
    And guess what happens when I hit the ‘find next’ button? It selects all the ‘regular text. (The document has no text with the 'book' font style applied!)
    Selecting another style — e.g. Bold, Italic, etc. — results, as expected, in the 'cannot find match' alert.
    Looks…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Serious GREP style bug: ampersands

    Hi, InDesign team.

    I've run into a serious bug with GREP styles. Any GREP expression containing an ampersand character that is entered as a GREP style in a paragraph style will suddenly acquire additional ampersands whenever I scroll through the list of GREP styles.

    STEPS TO REPRODUCE:

    Create a simple GREP style as part of a paragraph style.
    The entire GREP expression should consist of the single character &. (Though this also happens when the & is part of longer expressions.)
    Make enough other GREP styles that you need to scroll in the window to see them all.
    Close the…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Styles  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. [ID-4224415]Accessibility Tags order to match in InDesign and PDF

    Accessibility tag tree is not matching as per InDesign XML tag structure. We are doing more manual work to re-arrange the tag tree as per PDF view in Acrobat. We need to fix this bug in InDesign and match the tag tree as per InDesign tag structure for the accessibility PDF.

    Attached sample file and screen shot FYR....

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  PDF Export  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review the issue shortly

    -InDesign Team

  9. [ID-4261147] Hyperlinks with alt text added in the accessibility section, the alt text disappears when you save the file as an .idml

    Hyperlinks with alt text added in the accessibility section get lost when saving to .idml.

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IDML Export  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. GREP search failed to match all text in a story

    We use to be able to search all text in a story by using this (?s).+ code. It’s working fine in CS6. But in CC2019, 2020, and 2021 on both Mac and Windows it will fail to select all text in the story if there is more than ~ 50000 character. Only the first ~ 50000 will be selected.

    This might be related to an old bug that was introduced in 14.0.2 that was fixed in 14.0.3.

    Steps to Reproduce:
    1. Create a document with one story containing more than 50000 characters
    2. Do a GREP Find using (?s).+

    A…

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. [ID-4206781]Text wrapping has changed to before 2019 use textFrame based indent

    To place a graphicItem with text wrap, it is not an object-based indent like 2020, but a text frame-based indent before 2019.

    1 Version
    16.0.1(macOS10.14/10.15.6)

    2 Steps to reproduce the issues
    1. Make TextFrame. To places graphicItem above the textFrame and set text wrap.
    2. The indent set in the textFrame does not take effect for the object for which wrap text is set like before 2019.

    3 Expected result
    Indent set in the textFrame does take effect for the object for which wrap text is set like 2020.
    Please refer below Community article.
    https://community.adobe.com/t5/indesignフォーラム/indesign2020ではできていた回り込み時のインデント設定の維持が2021ではなくなっている/m-p/11677071

    4 Actual result
    The indent…

    95 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Text formatting can break backlinking endnote texts to endnote refs when exported to PDF (Print)

    Hi together,
    to explain the issue:

    Sometimes backling from endnote text to endnote reference number will not work.

    To make it work at all I found the following minimum requirements for PDF export:

    PDF Export (Print)

    Compatibility: Acrobat 5 (PDF 1.4)

    [x] Create Tagged PDF

    [x] Hyperlinks enabled

    Even with that sometimes only linking from the endnote reference number to the endnote text will work, but not backlinking from the endnote number in the endnote text to the reference in the main text.

    What I found:

    If you want linking back from the endnote number at the start of the…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  PDF Export  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. [ID-4260994]The filter in the review panel is automatically changing to "resolved"

    This happens very frequently.

    I will be going through user comments given online in the Indesign Review tab. As I do them I resolve them. This works fine.

    But then suddenly and randomly it will just decide to change my filter to show all resolved! Then all the old issues magically appear in the tab again until I go back to filter and unselect the Resolved button.

    Then it happens again. And again. It happens only when I go to change something in the document but it doesn't seem to matter what type of issue i'm doing. Replacing text. Deleting,…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Endnotes are tagged incorrectly when exporting to Accessible PDF from InDesign 2021

    In InDesign 2021, endnotes are not nested inside of a <Note> tag like they should be. Now only the Endnote number is in a <Note> tag and everything else is in a <P> tag. Normal behavior is to put each Endnote in its entirety within a <Note> tag. In addition, for several versions Endnotes and Footnotes are in a <Note> tag but then there's a <P> tag within the <Note> tag. The <P> tag is unnecessary and causes an error when trying to validate Accessible PDF. Please remove the <P> tag within <Note> tags when exporting to tagged PDF.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PDF Export  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Translation bug : Spread -> Grossi instead of Planche (in french)

    1. Click on publish online button Single Page is well translated as "Un(e) seul(e)" (page) Spread is wrongly translated as "Grossi" Grossi means bigger (or what we had with trapping : spreading inks, so making ink marks bigger) Planche which has been the accepted term in inDesign for ages.

    (also known as 09/01/2017 #ID-4199114)

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting this issue. We will review it

    -InDesign Team

  16. BUG (since CS6!): Nonbreaking Space (^S) Issue with World-Ready-Composer

    Issue:
    When using the ›World-Ready Composer‹, the character ›Nonbreaking Space‹ (^S) behaves exactly like the character ›Nonbreaking Space (Fixed Width)‹ (^s); i.e.: in justified paragraphs, its width does not adjust (like regular spaces do), but it is fixed and unchanging.
    This only occurs with the ›Adobe World-Ready Composer‹ (both ›Paragraph‹ and ›Single-line‹) and not with the regular ›Adobe Composer‹ (neither ›Paragraph‹ nor ›Single-line‹).
    It is not related to the font used, it has been tested with many different fonts.

    1. Versions with this bug, tested and confirmed by myself or colleagues:
      InDesign (Standard Version) CS6, CC2015.0
      InDesign (Middle Eastern Version) CC2020…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Drop shadow in exported PDF is a different size

    Certain drop shadows have a different size when they appear in an exported PDF.

    In the attached example, the black shapes each have a drop shadow effect in yellow. When exported, the shadows appear shorter and narrower. The difference is approximately 20 pt narrower and 1 pt shorter. (Note the difference in proportion of the yellow drop shadow and black shape in the screenshots.) I've also included the drop shadow effect attributes.

    This occurs with multiple PDF export settings including the default [High Quality Print]. I am able to reproduce this behavior in both InDesign versions 15.1.2 and 16.0.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PDF Export  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting. We will review the issue shortly.

    -InDesign Team

  18. Translation typo

    Your missing a capital on the "commentaires" option in the French translation of window menu

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. GREP position marker "^" = Beginning of Paragraph (not beginning of a new line after a forced line break)

    Dear Support,

    with the GREP position marker "^" for "Beginning of Paragraph", the GREP-search should consider the position of the beginning of a paragraph.
    But this marker does not only recognize the beginning of a paragraph, but also the beginning of a new line after a forced line break (SHIFT-RETURN).

    This is not correct: A forced new line is not the beginning of a paragraph.
    The only correct way would be to consider the beginning of a paragraph (RETURN).

    Sometimes you can use "(?=\r)\w+" to look for a word behind a Return instead of "^\w+" to find only the hits…

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We will review it shortly

    -InDesign Team

  20. [ID-4261000]Hebrew Text with Vowel Points Reorders Incorrectly When Pasted from InDesign to Word

    When keying (or importing) Hebrew text, InDesign often misplaces vowel points when two or more vowel points are attached to a single base character unless the base character and vowel points are keyed in a specific order. I don't totally understand it, but it has something to do with Unicode normalization. Microsoft Word gets around this problem, but I can't say how. It would be nice, however, if InDesign could get around it, too.

    One Hebrew font, SBL Hebrew, has written Unicode features (?) to prevent the normalization problem, but most fonts cannot do this on their own in InDesign.…

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base