7457 results found

1. unexpected window scaling

   InDesign prerelease 21.1 on MacOs 15.6.1 MacBookPro 16” M2pro (with connected 4K screen, or not).
   After lanching InDesign and opening a file, this one fits to full internal screen. If you open a second doc on the same window in a new tab, it resizes the window to full internal screen (even if you resized it to a less size) but window is a little higher. If you move the window to the external 4K screen and open a new doc, there is no bug : the window don't resize.

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  UI/UI Scaling  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. FlexObject Items Invisible in Preview Mode (possible culprit: IDML Roundtrip)

   Bug Report: FlexObject Items Invisible in Preview Mode (probably bugged after IDML Roundtrip)

   Product: Adobe InDesign 2025 (v20.x)
   Feature: Flex Layout / FlexObject (new in InDesign 2025)
   Severity: Major — affects preview mode of the new flex objects
   Date: February 20, 2026

   ---

   Summary

   FlexObject containers and their child items become invisible in Preview screen mode (but remain visible in Normal mode and Overprint Preview) after a document has undergone an IDML export/import roundtrip. The issue also propagates to any copies made from affected objects — even copies placed outside the FlexObject container.

   The root cause was identified as a missing registration of these page items in the internal spread-level page item collection. Items exist in page.allPageItems but are absent from spread.allPageItems, which Preview mode apparently relies on for rendering.

   ---

   Suspected Trigger

   The affected document had previously undergone an IDML roundtrip (export as .idml, then reopen). The document contains FlexObject containers (the new Flex Layout feature introduced in InDesign 2025). The hypothesis is that the IDML reconstruction does not fully re-register FlexObject items in the spread's internal page item hierarchy. Since FlexObjects are a very new feature, it is plausible that the IDML serialization/deserialization path does not yet handle them with full fidelity.

   ---

   Steps to Reproduce

   1. Create a new InDesign document.
   2. Add a Flex Layout container (FlexObject) with several child items (e.g., image frames with the object style "Album in REZI KURZ").
   3. Save and export the document as IDML (.idml).
   4. Close the document and reopen the exported .idml file.
   5. Save as .indd.
   6. Switch from Normal screen mode to Preview screen mode (View → Screen Mode → Preview, or press W).

   Expected: All items remain visible.
   Actual: The FlexObject and all its children disappear entirely.

   Additional observation: Copying an affected item out of the FlexObject and pasting it elsewhere on the page does not fix the issue — the copy inherits the "unregistered" state. Even extracting just the placed image (graphic content) from a frame and pasting it into the document independently produces a new frame that is also invisible in Preview mode.

   ---

   Systematic Exclusion of Common Causes

   The following properties were checked programmatically (via ExtendScript) on all affected objects and confirmed to be not the cause:

   | Property / Setting | Value Found | Would Cause Invisibility? |
   |---|---|---|
   | item.nonprinting | false on all items | No — correctly set |
   | item.visible | true on all items | No — correctly set |
   | item.itemLayer.visible | true | No — layer is visible |
   | item.itemLayer.printable | true | No — layer is set to print |
   | item.transparencySettings.blendingSettings.opacity | 100 on all items | No — fully opaque |
   | Object Style .nonprinting | false on all relevant styles | No — styles do not suppress printing |
   | item.fillColor | "None" (frames are graphic frames) | Not relevant |
   | Geometric bounds vs. page bounds | All items within page boundaries | No — not on pasteboard |
   | Link status of placed images | NORMAL on all images | No — links are intact |
   | Content type of frames | GRAPHIC_TYPE | Correct |

   Key distinction: Items are visible in Overprint Preview (View → Overprint Preview) but invisible in Preview screen mode (the mode that hides guides and pasteboard). This rules out any rendering/transparency issue and points to a metadata/registration problem specific to Preview mode's rendering path.

   ---

   Diagnostic Finding: Missing Spread Registration

   Using ExtendScript, the following discrepancy was discovered:

   // On an affected document:
   spread.allPageItems.length;  // → 0  (WRONG — should contain items)
   page.allPageItems.length;    // → 21 (correct — all items present)
   
   // After creating a NEW rectangle via script on the same page:
   spread.allPageItems.length;  // → 1  (new item registers correctly)
   page.allPageItems.length;    // → 22
   

   All 21 page items (1 FlexObject + 9 Rectangles inside it + 10 Images + 2 loose Rectangle copies) were found via page.allPageItems but none appeared in spread.allPageItems.

   A freshly created Rectangle (via page.rectangles.add()) registered in spread.allPageItems immediately, confirming that the spread collection mechanism itself works — it is specifically the IDML-reconstructed FlexObject items that fail to register.

   This strongly suggests that Preview mode uses the spread.allPageItems collection (or an equivalent internal list) to determine which items to render, while Normal mode and Overprint Preview use a different rendering path that includes all items regardless of spread registration.

   ---

   Workaround

   A manual workaround was discovered and automated via ExtendScript:

   1. Cut the affected top-level item.
   2. Create a temporary Rectangle on the page.
   3. Paste Into the temporary Rectangle (Edit → Paste Into).
   4. Select the pasted item inside the container and Cut it back out.
   5. Remove the temporary Rectangle.
   6. Paste the item back onto the page.
   7. Restore the original geometric bounds.

   This paste-into/cut-out cycle forces InDesign to re-register the item in the spread's internal collection. After this procedure, the item (including FlexObjects with all their children) appears correctly in Preview mode.

   An automated repair script was developed that:
   - Detects all top-level items present in page.allPageItems but absent from spread.allPageItems
   - Applies the paste-into workaround to each affected item
   - Verifies successful re-registration afterward
   - Groups the entire operation under a single Undo step

   ---

   Impact

   • Print production: Items invisible in Preview mode may also be missing from PDF export or print output (not yet verified but likely given the correlation between Preview mode and print rendering).
   • User confusion: Designers may not notice the issue until final proofing, as items appear normal in the default working view.
   • Propagation: The issue spreads to any copies made from affected objects, making it difficult to isolate without programmatic diagnosis.
   • Magazine production affected: The issue was discovered during production of a print magazine (folker magazine, issue 25-4), where FlexObject layouts are used for album review image grids.

   ---

   Requested Fix

   1. Ensure that IDML import fully registers all reconstructed page items — including FlexObject containers and their children — in the spread's internal page item collection.
   2. Consider adding a document integrity check that detects and repairs unregistered page items on document open or IDML import.
   3. Verify that other new object types introduced alongside Flex Layout are also correctly handled during IDML roundtrips.

   ---

   Environment

   • InDesign version: 2025 (v20.x, latest available as of February 2026)
   • OS: Windows
   • Flex Layout feature: Enabled, actively used
   • Document history: Created in InDesign → exported as IDML → reopened → saved as .indd
   • Diagnosis performed with: ExtendScript via JSX execution (InDesign DOM scripting)

   Bug Report: FlexObject Items Invisible in Preview Mode (probably bugged after IDML Roundtrip)

   Product: Adobe InDesign 2025 (v20.x)
   Feature: Flex Layout / FlexObject (new in InDesign 2025)
   Severity: Major — affects preview mode of the new flex objects
   Date: February 20, 2026

   ---

   Summary

   FlexObject containers and their child items become invisible in Preview screen mode (but remain visible in Normal mode and Overprint Preview) after a document has undergone an IDML export/import roundtrip. The issue also propagates to any copies made from affected objects — even copies placed outside the FlexObject container.

   The root cause was identified as a missing… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  IDML Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Need More Info  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   Please send the following information to sharewithID@adobe.com :

   • Reproducible Steps – What were you doing when the issue occurred?
   • Video recording of the issue
   • Is(Are) the issue related to a specific document(s)/asset(s)? If yes, could you provide us with the document(s)/asset(s)? Please package the entire document (To package the document, choose File → Package…)

   Also provide answers to follow queries

   1. During IDML workflow , are you opening the indd containing flex in version 20.0-20.5 or you are opening the IDML in version 21.0 onwards?

   2. What type of objects / images you are using?

   3. are you grouping the items or creating nested flex frames?

   4. You are only using object style to flex items or through any other menu?

3. InDesign 21.1 x64 on PC: panels not expanding when clicking on the icon

   Panels sometimes do not expand when clicking on an icon in the right-hand column of panels. It seems random. Sometimes the panel you choose expands when you click on the icon (as it should), but sometimes you have to click the two little chevrons pointing leftward at the top of the column of icons, which makes them all expand and it's a mess to work with. Only the one you click on should expand, but sometimes it doesn't.

   This isn't a new bug. There were previous submissions about this and the issue was supposedly resolved, but it is NOT. The comments are closed, so I couldn't comment on there that the issue is not resolved. This has been happening ever since the first upgrade at the beginning of the year. I'm on the latest update and still having this issue.

   Panels sometimes do not expand when clicking on an icon in the right-hand column of panels. It seems random. Sometimes the panel you choose expands when you click on the icon (as it should), but sometimes you have to click the two little chevrons pointing leftward at the top of the column of icons, which makes them all expand and it's a mess to work with. Only the one you click on should expand, but sometimes it doesn't.

   This isn't a new bug. There were previous submissions about this and the issue was supposedly resolved, but it is NOT. The… more

   •  

   •  

   •  

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UI/UI Scaling  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. [ID-4274715] Missing anchoredObjectSettings for FlexObject in DOM

   The anchoredObjectSettings for FlexObject is missing in DOM.
   So it’s impossible to manipulate the anchor properties of a Flex Layout inside a text frame.

   Please, fix it and expose the anchoredObjectSettings of a flex layout object.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  0 comments  ·  Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Create Alternate Layout is buggy

   I wanted to create one alternative Layout so that I can export my DIN A3 file also as DIN A4 sized file.

   I created an alternate Layout as usual.
   I expected having all 12 pages twice in 2 different Sizes, (one in A3 and one in A4)
   What InDesign did was it created 4 different Alternate Layouts and distributed the 12 pages among the 4 layouts.
   Meaning I have 2 Layout I did not create and I cannot move the pages back to the original layout.
   Also it did not resize the design, styles and texts as usual, instead they are cut off.

   Since the "Undo / Redo" functionality is currently also deactivated or broken I cannot undo that step and my file is toast now.

   Indesign Version 21.2., Mac OS, English

   I wanted to create one alternative Layout so that I can export my DIN A3 file also as DIN A4 sized file.

   I created an alternate Layout as usual.
   I expected having all 12 pages twice in 2 different Sizes, (one in A3 and one in A4)
   What InDesign did was it created 4 different Alternate Layouts and distributed the 12 pages among the 4 layouts.
   Meaning I have 2 Layout I did not create and I cannot move the pages back to the original layout.
   Also it did not resize the design, styles and texts as usual, instead they… more

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Adjust Layout  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Show Import Options no longer stays checked

   The "show import options" box will not stay checked in the "Place" window. Sometimes it does stay checked for one or two items but if you are importing more than that it will not stay checked.

   Previously it stayed checked until the next time that inDesign was restarted. This may seem minor but is an extreme inconvenience and severely hindering workflow.

   Version: 20.5

   Steps to reproduce:
   1. While working in document, Control+D (or "File>Place")
   2. Sees "Show Import Options" is unchecked, check box
   3. Place object
   4. Control+D to place new object
   5. Sees "Show Import Options" is unchecked AGAIN, re-check box
   6. Place new object
   7. Repeat ad nauseam

   Expected result: When "Show Import Options" is checked after first use, it will stay checked until the program is shut down and re-opened.

   Actual result: Not that.

   The "show import options" box will not stay checked in the "Place" window. Sometimes it does stay checked for one or two items but if you are importing more than that it will not stay checked.

   Previously it stayed checked until the next time that inDesign was restarted. This may seem minor but is an extreme inconvenience and severely hindering workflow.

   Version: 20.5

   Steps to reproduce:
   1. While working in document, Control+D (or "File>Place")
   2. Sees "Show Import Options" is unchecked, check box
   3. Place object
   4. Control+D to place new object
   5. Sees "Show Import Options" is unchecked AGAIN,… more

   •  

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Usability  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Opens in old version after the latest automatic upgrade

   When I double click on an InDesign file in a folder, why are my files trying to open in an older version of InDesign (2025), when I have the latest version installed? It wasn't happening before the latest version of InDesign 2026 was updated today, and I can't work out how to stop it happening in future, so that any file I click on opens in the latest version of InDesign, not an old one. I have specified that any *.indd file should open in the latest version, but that doesn't resolve the problem.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Document/Pages  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Share for Review fails to update - InDesign 2026

   InDesign 2026 v21.0 (the latest update)

   Creating a new Share for Review link works without issue. However, updating an existing review link consistently triggers the error: “There was an error updating the artifact.” When this happens, the review document does not update. The only way to refresh the content is by generating a new review link, which unfortunately removes all previously added comments.

   This is not a new problem, it’s a recurring issue that has resurfaced for many users, seemingly starting again around late October. It’s extremely frustrating, especially since Share for Review has become an essential part of how we proof documents with our team and clients. Across our team of four, using slightly different setups, we all experience the same problem. At this point, the feature is practically unusable.

   Is there a plan to fix this and restore full functionality to Share for Review?

   InDesign 2026 v21.0 (the latest update)

   Creating a new Share for Review link works without issue. However, updating an existing review link consistently triggers the error: “There was an error updating the artifact.” When this happens, the review document does not update. The only way to refresh the content is by generating a new review link, which unfortunately removes all previously added comments.

   This is not a new problem, it’s a recurring issue that has resurfaced for many users, seemingly starting again around late October. It’s extremely frustrating, especially since Share for Review has become an essential part of how… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Share for Review  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. AI-generated Alt Text for images should NOT be on by default

   Gross decision to have this "feature" on by default. Good thing I didn't miss the popup on startup, I NEVER want any AI features at all ever, let alone to have to OPT OUT? Madness. Also ridiculous is the option to turn off the the "AI generated content" tag on this "feature" at all. Why would you allow that? I guess it's in line with all of the untagged AI on Adobe Stock lol.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Others  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. pdf error

    trying to pdf a document and generates this error, have removed the images one by one and it still throws the same error

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. OR Operator with Anchors Behaves Incorrectly

    InDesign GREP Bug Report: OR Operator with Anchors Behaves Incorrectly

    Summary
    InDesign's GREP engine does not handle the OR operator (|) correctly when used with anchors (^ and $). This behavior differs significantly from standard regex engines and produces unexpected, inconsistent results.

    Problem Description
    When using the OR operator with anchors in InDesign GREP, the anchors are interpreted with incorrect precedence, causing the pattern to behave differently than expected. This issue has been confirmed as a bug by Peter Kahrel, author of "GREP in InDesign."

    Test Cases and Results

    Test Case 1: ^ab|c
    Text: ab ac bc Expected (standard regex): Matches "ab" at line start AND "c" anywhere Actual InDesign result: Only matches "ab" at line start Issue: InDesign interprets as ^(ab|c) instead of (^ab)|c

    Test Case 2: ^a|bc
    Text: ab ac bc Expected (standard regex): Matches "a" at line start AND "bc" anywhere Actual InDesign result: Only matches "a" at line start Issue: Same precedence problem as Test Case 1

    Test Case 3: (^a)|bc
    Text: ab ac bc Expected (standard regex): Matches "a" at line start AND "bc" anywhere Actual InDesign result: Still only matches "a" at line start Issue: Even explicit grouping doesn't resolve the problem

    Test Case 4: (a$)|bc
    Text: ab ac bca Expected (standard regex): Matches "a" at line end AND "bc" anywhere Actual InDesign result: Only matches "bc" ($ anchor completely ignored) Issue: End-of-line anchor is ignored entirely

    Test Case 5: bc|(a$)
    Text: ab ac bca Expected (standard regex): Matches "bc" anywhere AND "a" at line end Actual InDesign result: Only matches "bc" ($ anchor ignored) Issue: End-of-line anchor ignored regardless of position

    Test Case 6: bc|a$
    Text: ab ac bca ac ab bc a Expected (standard regex): Matches "bc" anywhere AND "a" at line end Actual InDesign result: No matches at all Issue: Pattern completely fails when $ anchor is second in OR expression

    Impact
    * Users cannot rely on standard regex behavior for OR operations with anchors
    * Complex workarounds are required for simple pattern matching
    * Documentation doesn't warn users about this non-standard behavior
    * Patterns that work in other regex engines fail unexpectedly in InDesign

    Technical Details
    * InDesign Version: 20.3.1 x64

    Requested Fix
    Please fix the OR operator precedence to match standard regex behavior:
    1. ^ab|c should match "ab" at line start OR "c" anywhere
    2. (a$)|bc should match "a" at line end OR "bc" anywhere
    3. Explicit grouping should work as expected
    4. End-of-line anchors should not be ignored in OR expressions

    InDesign GREP Bug Report: OR Operator with Anchors Behaves Incorrectly

    Summary
    InDesign's GREP engine does not handle the OR operator (|) correctly when used with anchors (^ and $). This behavior differs significantly from standard regex engines and produces unexpected, inconsistent results.

    Problem Description
    When using the OR operator with anchors in InDesign GREP, the anchors are interpreted with incorrect precedence, causing the pattern to behave differently than expected. This issue has been confirmed as a bug by Peter Kahrel, author of "GREP in InDesign."

    Test Cases and Results

    Test Case 1: ^ab|c
    Text: ab ac bc Expected (standard regex):… more

    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Others  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Object Menu, Arrange for Text blocks not working

    InDesign version 21.0.2 x64

    I have used Adobe InDesign since 1997 (first introduced to me at school while I was learning Quark), more full-time since 2002 (worked at a newspaper). I have always been able to use the Object menu to either move objects in front of or in back of others. This still seems to work in 2025 with actual objects, i.e., rectangles, ovals, etc. It no longer works as of today with text blocks. In my remote conversation with Manoj, the only workaround is to either type my text into a color block and reposition it, or perhaps shorten my other color block and add text on top of it. This happened after a recent Windows 11 update, but, the program worked as expected until this morning. That leads me to believe this was a deliberate change by Adobe. That's ridiculous, in my opinion. WHY would Adobe remove a key feature from InDesign's page layout function? Please return this function - it's important for those who spend much of their time doing page layouts for clients. Thank you.

    InDesign version 21.0.2 x64

    I have used Adobe InDesign since 1997 (first introduced to me at school while I was learning Quark), more full-time since 2002 (worked at a newspaper). I have always been able to use the Object menu to either move objects in front of or in back of others. This still seems to work in 2025 with actual objects, i.e., rectangles, ovals, etc. It no longer works as of today with text blocks. In my remote conversation with Manoj, the only workaround is to either type my text into a color block and reposition it, or perhaps… more

    •  

    • 

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Adjust Layout  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Ongoing performance issues with large InDesign files

    We’re running into frequent slowdowns and crashes when working with large InDesign documents (lots of pages, linked assets, complex styles, long text flows). It’s happening across multiple machines, not just one setup.
    At Tech Formation, we support teams that depend on InDesign for real production work, and these issues are starting to affect delivery timelines and workflows.
    It would be great to know whether this is a known issue and whether there’s any workaround or logging we can enable to help diagnose it.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Accessibility  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Clicking icons (sometimes) does not open the palette

    Version: Indesign 21.0
    Expected result: clicking the icon opens the palette
    Actual result: the palette does not open, even though the icon has a "clicked" appearance
    Steps to reproduce: I haven't figured out, it seems to happen randomly... but restarting the program fixes it

    Note:
    The problem affects the entire column of icons shown in the screenshot, not just the clicked one.

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  UI/UI Scaling  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. ID2026 Export Issues

    Exporting PDFs and IDML files in ID2026 is taking far longer than it does to do the same export in 2025, and I'm losing almost all of the hyperlinks on parent pages when exporting to IDML.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Performance/Usability  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Need More Info  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Please send the following information to sharewithID@adobe.com :

    • Reproducible Steps – What were you doing when the issue occurred?
    • Video recording of the issue
    • Is(Are) the issue related to a specific document(s)/asset(s)? If yes, could you provide us with the document(s)/asset(s)? Please package the entire document (To package the document, choose File → Package…)

    —

    Adobe InDesign Team

16. pannels

    sometimes panels like Links, Layer are not opening by command or clicking in Window menu, then I got a solution for this issue i.e. change the workspace to another and comeback to your old one, it will help you. But it'll be an issue for everyone else. So please solve this issue in next update.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  UI/UI Scaling  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. collapsed panels on the right side won't open

    version 21.0 ME
    collapsed panels on the right side don't always open when clicked on, it may work for a while but then stops until I reset my workspace, then it works for a while and then stops again.
    I tried creating a new workspace but still happens.
    The same thing happens to my coworker.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Text/Story/Table  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Need More Info  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

    Please send the following information to sharewithID@adobe.com :

    • Reproducible Steps – What were you doing when the issue occurred?
    • Video recording of the issue

    —

    Adobe InDesign Team

18. [ID-4257175]Pages Panel: Buttons are hidden behind page number text when window is thin

    When the pages panel is as thin as possible, the buttons such as delete page are behind the text that says the number of pages. It is therefore not possible to click on the buttons. I always use this panel in a thin band, and it is now less practical.

    Version: InDesign 20.0.0

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    •  

    33 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    14 comments  ·  UI/UI Scaling  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

    Fix for this issue is now available in the latest InDesign Release version 20.1 (Build 20.1.0.71), available via Creative Cloud Desktop application.

    Please update your InDesign application to this latest version to get the fix.

    --

    Adobe InDesign team

19. 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.
    Nechama

    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… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. 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:
    JavaScript

    target 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.… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Crash/Freeze/Hang  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating