Christoph I just meant the overlay with filename and exif-/IPTC-informations.
I think I got the idea, but what are you asking? Do you want me to provide some CSS code that simply disabled the caption in the popup? That would not be a problem.
Christoph P.S: You can load the image into ExifTool (Online-Version: https://exif.tools/), which is highly recommended for testing images EXIF-Metadata. And it shows 0 errors.
It's not about errors. Errors can easily be avoided, just like they already are in Files gallery. Problem is, there are some PHP-specific issues from reading the massive amount of EXIF that has been embedded into that image from your Photolab app. I'm sure there are ways to avoid this, also in PHP, but it would require much more application logic to parse this image's massive EXIF output without stumbling on the ones not needed. Besides, I don't quite see why this EXIF app should be injecting 50kb worth of EXIF info into the image that nobody is supposed to see? It's kinda pointless, and no camera's will ever create EXIF like this ...
Christoph I thinks it's the way Samsung-NX-Cameras write EXIF-Information and not "currupted" (https://exiv2.org/tags-samsung.html). As I said - the images have just been developed with DxO-Photolab and been exported from there. You can see that the ExposureTime-Field is correct. And then some Samsung-Specific-Makernotes. But never mind - for me it's no big problem ;-)!
It's definitely not the Samsung-NX that is creating all the EXIF "junk", it's definitely DxO-Photolab. I already tested other images from Samsung-NX, and they output nicely. Cameras will never create strange excessive EXIF data like in your images.
Here is a sample from from Samsung-NX:
It produces a clean minimal EXIF output with all data in tact:
FILE.SectionsFound: ANY_TAG, IFD0, EXIF
COMPUTED.html: width="1200" height="800"
EXIF.DateTimeOriginal: 2014:01:20 10:35:25
EXIF.DateTimeDigitized: 2014:01:20 10:35:25