Skip to main content
Ale_Rossi
Participant
February 9, 2026
解決済み

Acrobat on macOS 26.2 (Tahoe) reports ALL PNG/JPEG images as corrupted in Fill & Sign

  • February 9, 2026
  • 返信数 2.
  • 139 ビュー

Hello,

I would like to report a reproducible issue with Adobe Acrobat Reader (last version 2025.001.21184) on macOS 26.2 (Tahoe), using a Mac Mini M4.

 

Problem

When using Fill & Sign → Add Signature → Image, Acrobat reports that the selected PNG image file is corrupted.

 

This happens with:

  • PNG files

  • JPEG files

  • Brand new screenshots created directly on macOS 26.2

  • Images converted with Preview

  • Images converted with ImageMagick

  • Images converted with XnConvert

  • Images with sRGB IEC61966-2.1 profile

  • Images with no embedded color profile

All of them produce the same error: image corrupted.

 

Important observations

  • The exact same files work correctly on another Mac running macOS Sequoia with the same Acrobat Reader version.

  • Typed or drawn signatures inside Acrobat work normally.

  • GPU acceleration was disabled via:

defaults write com.adobe.Acrobat.Pro DCEnableGPUAcceleration -bool false
defaults write com.adobe.Acrobat.Pro EnableHardwareAcceleration -bool false

 

 

This suggests a possible incompatibility between Acrobat’s image import module and macOS 26.2 image decoding APIs.

 

Can anyone on macOS 26.2 confirm this behavior?

 

Thank you.

Alessandro

    解決に役立った回答 AnandSri

    HI ​@Ale_Rossi 

     

    I hope you are doing well, and thanks for your cooperation and patience on this.

    The issue has been addressed with the latest build of Acrobat and Reader version 25.001.21265. Planned update, Mar 02, 2026. Check for any pending updates by navigating to Menu > Help> Check for Updates. Install the updates, restart the app and the machine, and try again.

     

    Let us know if you experience any issues.

    Regards,

    Anand Sri.

    返信数 2

    AnandSri
    AnandSri解決!
    Legend
    March 3, 2026

    HI ​@Ale_Rossi 

     

    I hope you are doing well, and thanks for your cooperation and patience on this.

    The issue has been addressed with the latest build of Acrobat and Reader version 25.001.21265. Planned update, Mar 02, 2026. Check for any pending updates by navigating to Menu > Help> Check for Updates. Install the updates, restart the app and the machine, and try again.

     

    Let us know if you experience any issues.

    Regards,

    Anand Sri.

    Ale_Rossi
    Ale_Rossi作成者
    Participant
    March 3, 2026

    Hi Anand,

    that’s a great news !

    Anyway now I’m using version 25.001.21223 and it’s already working fine.

    Thank you so much for all your effort, very appreciated.

    Best regards

    Alessandro

     

     

     

    AnandSri
    Legend
    March 4, 2026

    Hello ​@Ale_Rossi 

     

    I am glad that the issue is fixed. If you want, you can download the latest security build for the latest security updates and features.

     

    Please let us know if you need any assistance.

    Thanks for your cooperation on this.

     

    Regards,

    Anand Sri.

    Amal.
    Legend
    February 10, 2026

    Hi ​@Ale_Rossi 

     

    Hope you are doing well, sorry for the trouble and thanks for sharing such a detailed observation.

     

    Would you mind sharing a small video recording of the steps you are taking and the issue as it occurs so we can get this checked further by our engineering team?

     

    ~Amal

     

     

    Ale_Rossi
    Ale_Rossi作成者
    Participant
    February 11, 2026

    Hi Amal,

    sure, in attach a quick video of what happens with any image file (even simple screenshots done on macOS Tahoe). As said, with macOS Sequoia no issues at all.

    In both cases I’m using Adobe Acrobat Reader (last version 2025.001.21184)

     

    Let’s keep in touch if you get any news from your technical team !

     

    Thanks a lot

    Alessandro

    AnandSri
    Legend
    February 11, 2026

    Hello ​@Ale_Rossi 

     

    I hope you are doing well, and thank you for sharing all the details.

     

    We have reported the issue to the product team, and they are working on a fix for the problem. We will update the thread once the fix is available with the public release.

    Thanks for your patience and cooperation on this.

     

    Regards,

    Anand Sri.