66 results found

1. InDesign crashes when trying to cut, and/or copy, a table from the paragraph level

   Different versions of InDesign have this problem including 2023, 2024, and 2025 - on Mac Monteray.

   If I attempt to highlight tables from the paragraph level and copy or cut, either with menus or key commands, InDesign will either immediately crash, or beach ball a bit and then crash.

   Upon reopening InDesign, the menus will not appear. I have to use the keyboard commands to quit InDesign again. Upon reopening, it will work properly again... that is unless I attempt to copy or cut another table.

   Please fix! I'm constantly working with complicated tables and the only way to get them to remain consistant is to copy and paste them!!

   In the attached screenshot you can see how I am highlighting the tables.

   NOTE: These tables include form fields. I noticed I am able to copy/cut tables that do not include them - so maybe that's an issue?

   NOTE 2: Also, I'm able to delete (without cutting) so clipboard issue??

   Also, a friend working on a PC was able to copy/cut - so looks like a Mac problem.

   EDIT: Form fields are the problem - deleting them solves it. I need the form fields - anything you can do to help?

   Different versions of InDesign have this problem including 2023, 2024, and 2025 - on Mac Monteray.

   If I attempt to highlight tables from the paragraph level and copy or cut, either with menus or key commands, InDesign will either immediately crash, or beach ball a bit and then crash.

   Upon reopening InDesign, the menus will not appear. I have to use the keyboard commands to quit InDesign again. Upon reopening, it will work properly again... that is unless I attempt to copy or cut another table.

   Please fix! I'm constantly working with complicated tables and the only way to get… more

   •  

   1 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  ·  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

2. [ID-4256546]Bug when setting an even number as the start page number in a new document.

   Bug when setting an even number for the start page number when creating a new document

   1. Version of Adobe InDesign
      CC2025 (ver. 20.0) JP

   2. Steps to reproduce the issues
      Set any even number for the start page number on the Create New Document screen.

   3. Expected result
      An even page number will be displayed in Current Page Number as set.

   4. Actual resul
      The value set in the New Document screen will not be reflected, and “Current Page Number” will display “1”.

   As shown in the attached figure, when “Current Page Number” is inserted into a new document with the starting page number set to an even number, the document starts with “1”.
   (As long as the number set in the new document creation screen is an even number, any value will not be reflected and will become “1”).

   This phenomenon can be recovered by temporarily setting a different value in “Number & Section Option”.
   However, for users who are not aware of this behavior, it is sure to cause great confusion.
   It can also cause significant time loss in finding a solution.
   We have not been able to verify whether this bug is specific to the Japanese version, but we recognize that it is a very serious bug.
   We sincerely hope that the development team will fix it as soon as possible.

   <Japanese Comment>
   新規ドキュメント作成で開始ページ番号に偶数番号を設定すると発生する不具合

   InDesignのバージョン
   CC2025 (ver.20.0) JP

   問題の再現手順
   新規ドキュメント作成画面で、開始ページ番号に任意の偶数を設定する。

   予想される結果
   「現在のページ番号」に、設定通りの偶数ページ番号が表示される。

   実際の結果
   新規ドキュメント画面で設定した値は反映されず、「現在のページ番号」に「1」が表示される。

   添付画像のように、開始ページ番号を偶数番号に設定した新規ドキュメントに、「現在のページ番号」を挿入すると「1」から開始されます。
   （新規ドキュメント作成画面で設定した番号が偶数である限り、いかなる値であっても反映されず「1」となる）

   この現象は「ページ番号とセクションの設定」で、一時的に別の値を設定すれば回復します。
   しかしこの挙動を認識していないユーザーにとって、大きな混乱を招く原因となることは間違いありません。
   また、解決策を見つけるために大きな時間のロスを生む可能性があります。
   この不具合は日本語版固有の問題なのかは検証できていませんが、非常に深刻なバグであると認識しています。
   開発チームには早急に改善していただくよう切に希望します。

   Bug when setting an even number for the start page number when creating a new document

   1. Version of Adobe InDesign
      CC2025 (ver. 20.0) JP

   2. Steps to reproduce the issues
      Set any even number for the start page number on the Create New Document screen.

   3. Expected result
      An even page number will be displayed in Current Page Number as set.

   4. Actual resul
      The value set in the New Document screen will not be reflected, and “Current Page Number” will display “1”.

   As shown in the attached figure, when “Current Page Number” is inserted into a new document with the starting… more

   •  

   •  

   •  

   •  

   • 

   20 votes

   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  ·  Document/Pages  ·  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
   Available in Prerelease Builds  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix for this issue is available in the InDesign PreRelease build(v20.1.0.028) and above.

   Please check if the issue is now resolved.

   Download/Update the latest InDesign PreRelease build in Creative Cloud under the “Prerelease” category(Refer to “Prerelease_CreativeCloud.png” for reference)

   Please apply to the InDesign PreRelease in case you don’t have access to the InDesign PreRelease build – https://www.adobeprerelease.com/beta/C6DFA254-C40C-4EEB-8F6D-F4AEDA2E6171

   If you still encounter any issues, please drop a mail to sharewithID@adobe.com.

   —

   Adobe InDesign team

3. Export to Adobe Express

   Export to Adobe Express errors out with "workflow cannot be completed..." – Id v2025.

   •  

   1 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  ·  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

4. Before tag and after untag frame with different behavior

   If you tag a frame object (XML), this object does not behave the same after untagging as before tagging. In other words: tagging is not fully reversible. You can see a difference in the layer panel and in the exported PDF tag structure (Tagged PDF)

   How can this behavior be reproduced?

   1. Create a new InDesign document.
   2. Draw a placeholder (empty) graphic frame
   3. Assign any XML tag to the frame
   4. Remove the XML tag
   5. Export a tagged PDF
      

   What is the difference between the object before tagging and after untagging?

   The layer panel shows a different status.

   The frame before tagging is not assigned a tag in the tag structure of the PDF during PDF export. A tag is assigned to the object in the PDF structure after tagging and untagging. (see attached screenshots)

   What should be the correct behavior?

   Both states of the frames - i.e. without tagging and after untagging - should result in the same result in the layer panel and in the tag export for PDF.

   Why is this relevant?

   This causes a problem if these objects appear in the tag structure of the exported PDF. They are (empty) graphic frames, but InDesign assigns a Figure tag to them and they also have no alternative text. When checking the PDF for accessibility, an error is reported.

   These two states of the same object cannot be distinguished via ExtendScript. If an InDesign document is saved using IDML, these objects are converted back into “normal” graphic frames.

   InDesign, Platform

   InDesign 2024, 2025
   macOS Monteray

   Discussion

   https://community.adobe.com/t5/indesign-discussions/rectangle-vs-graphic-frame/td-p/15039102

   If you tag a frame object (XML), this object does not behave the same after untagging as before tagging. In other words: tagging is not fully reversible. You can see a difference in the layer panel and in the exported PDF tag structure (Tagged PDF)

   How can this behavior be reproduced?

   1. Create a new InDesign document.
   2. Draw a placeholder (empty) graphic frame
   3. Assign any XML tag to the frame
   4. Remove the XML tag
   5. Export a tagged PDF
      

   What is the difference between the object before tagging and after untagging?

   The layer panel shows a different status.

   The frame before tagging… more

   •  

   •  

   •  

   •  

   1 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

5. [ID-4256174]InDesign crashes while searching any font/word, etc., which is in overset text.

   We have simple scripts that operate on script labels to Find and Replace Text, adjust Text Size, things like that. We've been using them for three years with no problems prior to v2025. They crash and bring up the option to send an error report. We're rolling back to 2024 now, we can't operate efficiently without these scripts.

   2 votes

   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  ·  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
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2025(v20.0.1.032). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

6. Dropshadow > Size is limited to 0-144 points within scripting but you can enter higher numbers manually 0-1000 points

   My understanding is indesign dropshadow effect needs to be updated for the option: size within the dropshadow panel to be able to accept 0 - 1000 points for scripts. You can input higher numbers within the size by doing it manually but not with scripts for whatever reason. It will only accepts 0-144 point or 2 inches within the code.

   1. Indesign CC 2025
   2. Run the attached script a 100 in height image and you'll get the error.
   3. On the dropshadow applied to have the distance 5.0 in and size 5.0
   4. Distance: 5.0 in and Size: 0.0694 in
   5. Script attached.

   I have a script to automatically apply dropshadows and we have a formula where we take the height of the image and multiply that by 5% which gets placed in the Distance and Size. This works for smaller images but when there are larger images the number it puts into the distance works but the size seems to be limited to 2 inches. But if I do it manually it can go up to 13.8889″
   for the size

   I get this error: ERROR in applyDropShadow: Error: Invalid value for set property ‘size’. Expected Unit (0 - 144 points), but received “5.0 in”. 13.8889 in = 1000 points

   //@target "indesign"
   //@targetengine "session"

   function isValidObject(obj) {
   try {
   return obj && obj.isValid;
   } catch (e) {
   return false;
   }
   }

   function applyDropShadowByHeightInInches(obj) {
   if (!isValidObject(obj)) return;

   var doc = app.activeDocument;
   var originalH = doc.viewPreferences.horizontalMeasurementUnits;
   var originalV = doc.viewPreferences.verticalMeasurementUnits;
   
   try {
       // Switch the document to inches.
       doc.viewPreferences.horizontalMeasurementUnits = MeasurementUnits.INCHES;
       doc.viewPreferences.verticalMeasurementUnits   = MeasurementUnits.INCHES;
   
       // geometricBounds => [y1, x1, y2, x2] in INCHES now.
       var bounds = obj.geometricBounds; 
       var heightInches = Math.abs(bounds[2] - bounds[0]); // bottom - top
   
       // 5% of height in inches
       var dropShadowInches = heightInches * 0.05;
   
       // Apply the drop shadow
       var ds = obj.transparencySettings.dropShadowSettings;
       ds.mode     = ShadowMode.DROP;
       ds.angle    = 120;                 // Static angle
       ds.distance = dropShadowInches;    // in inches
       ds.size     = dropShadowInches;    // same as distance
       ds.opacity  = 35;                  // example opacity
       ds.noise    = 2.5;                 // example noise %
       ds.xOffset  = 0;
       ds.yOffset  = 0;
       ds.spread   = 0;
   
   } catch (e) {
       $.writeln("Error applying shadow: " + e);
   } finally {
       // Restore original measurement units
       doc.viewPreferences.horizontalMeasurementUnits = originalH;
       doc.viewPreferences.verticalMeasurementUnits   = originalV;
   }
   

   }

   function main() {
   if (app.documents.length === 0) {
   alert("No open documents.");
   return;
   }

   var doc = app.activeDocument;
   if (!isValidObject(doc)) {
       alert("Active document not valid.");
       return;
   }
   if (app.selection.length === 0) {
       alert("No objects selected.");
       return;
   }
   
   var count = 0;
   for (var i = 0; i < app.selection.length; i++) {
       var obj = app.selection[i];
       if (isValidObject(obj)) {
           applyDropShadowByHeightInInches(obj);
           count++;
       }
   }
   alert("Drop shadow applied to " + count + " object(s).");
   

   }

   main();

   My understanding is indesign dropshadow effect needs to be updated for the option: size within the dropshadow panel to be able to accept 0 - 1000 points for scripts. You can input higher numbers within the size by doing it manually but not with scripts for whatever reason. It will only accepts 0-144 point or 2 inches within the code.

   1. Indesign CC 2025
   2. Run the attached script a 100 in height image and you'll get the error.
   3. On the dropshadow applied to have the distance 5.0 in and size 5.0
   4. Distance: 5.0 in and Size: 0.0694 in
   5. Script attached.

   I… more

   •  

   •  

   1 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  ·  Scripting  ·  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