Cannot place this file. Invalid PNG file
In 15.0.3, my publication was print ready
I updated to 15.1 as I normally would.
In 15.1, particular .png files were missing. I tried to place the missing images as usual but got the error - Cannot place this file. Invalid PNG file'.
I rolled back to 15.0.3 and am now able to place the self same files.
The fix is now publicly available in the latest InDesign update, 15.1.1
Please update to this latest version to get the fix.
Adobe InDesign team
Jon r commented
Seeing this issue in V18.0 I have hundreds of PDFs, so will be a pain to fix since it doesn't say which PNG file is the problem.
Lene Olsen commented
I have the newest version 17.4 of InDesign and have this bug - which is very frustration as it does block for production of the file. Please do something Adobe
Rebecca Frates commented
Still a problem in version 17.4 on 9/4/2022. Was fine until I updated to a new computer.
Incredibly frustrating! Some I can relink, and some won't. Either way, it is ridiculous to have to relink everything. That is the purpose of linking in the first place.
This bug is still present as of Sept. 1, 2022. Version 17.4
Uwe Laubender commented
The bug is back with InDesign 2022.
Don't know if this is exactly the same bug that was fixed with 15.1.1, but I can see the same error message "Cannot place this file. Invalid PNG file" AGAIN in InDesign 2022 version 17.3.0.
Not with my InDesign 2021 version 16.4.2 which is running side-by-side on the same Windows 10 machine.
Test files, PNG files from Fireworks, can be downloaded from this post here:
Two videos showing the issue and a possible cause for this, not flattened PNGs from Fireworks, can be downloaded here:
See also my post in the same discussion where I tested with the PNG files from user TidbitsofSoCo:
The only workaround I see is to open the PNG files with PhotoShop and save them again with the Legacy Save to Web dialog. The meta data from Fireworks will be removed in the process. And again: No issue with that workflow with my German InDesign 2021 16.4.2 on Windows 10.
( Adobe Community Professional )
Hillary Hellesto commented
This bug is still present - 1/11/2021, can't export an interactive pdf that had one small edit
Enas Satir commented
I solved my problem by relinking all the files in my links panel... I guess one of them was corrupted (but link them from a different location, not from the packaged links folder from the packaged inDesign file, if that makes sense).
I don't know why inDesign always has so many issues.
I am using InDesign version 16.2.1 on Windows 10 Enterprise V 19.09
I have never experienced this problem before. I have to update ALL the art in the file to .tiff to export as PDF, too. This does not happen on my Mac
Looking at all these peoples' comments, I am wondering if Admin has abandoned the issue. If this is being addressed or if there is another discussion, can Admin please provide that link? I will have to use my Mac laptop at work as a workaround. This is very irresponsible of Adobe.
awab work commented
is this ever going to be solved?
CC 2021 16.2.1
Phil Kjelland commented
i think i've found the issue, for me at least. when i open the png in photoshop, the 'raw data' in the file info section claims that it 'cannot display raw metadata,contents too large'.
i found a script that removes all metadata & retains layers. i can't remember where i got it, but it worked. essentially the metadata is corrupt.
Phil Kjelland commented
i'm on 16.2.1 and having this issue
I am experiencing the same frustrating bug and cannot export the file. can someone help?
I have the same issue as well :/ and I was on V 15.1.1 and now V16
Im on v16.0 and this still hasnt been fixed!
I am encountering the same problem and I can't export my file to pdf because of this error. Please help!
Hello! I have the latest update and this issue keeps happening!
Hello everyone! I'm still seeing the issue even after update to 15.1.1. Is there a new fix for that? Thanks in advance!
Indeed! Bug is still present even after update to 15.1.1.
Pirabu Chandran commented
No, we still have the same bug even after 15.1.1