https://bugs.kde.org/show_bug.cgi?id=510629
--- Comment #2 from 人力脑机 <[email protected]> --- (In reply to Lenzoid from comment #1) > Can confirm this. Did a quick comparison: Windows 11 didn't save this > information either when doing a fullscreen screenshot with Snipping Tool > (Win+Shift+s). MacOS did correctly save it. For example > > exiftool '-*resolution*' Example-fullscreen-Screenshot-macos.png > X Resolution : 144 > Y Resolution : 144 > Resolution Unit : inches > > I believe these are the pertinent values for the retina screen they were > taken on. Can you give a more specific example of a workflow when this can > become a problem for you? Personally, when including a screenshot in a > document, for example including an image inline in an email in Thunderbird, > I'm so used to it being included in the totally wrong dimensions, so I'm > used to resizing every single screenshot by hand. ;) Thanks for your reply! The reason it’s important to include the resolution (DPI) information in the image metadata is that different devices have different DPI values. For example, if I take a screenshot on a 24-inch 4K display (around 184 DPI) and then view the same image on a 24-inch 1080p display (around 92 DPI), the screenshot appears much larger on the lower-resolution screen. If the screenshot file contains the correct DPI metadata, image viewers and document editors can display it at the correct physical size, matching what was originally shown on the source display. Without this information, the viewer software has no way to know the actual intended print or display size, so it defaults to assuming 72 DPI or 96 DPI, which causes inconsistent visual scaling between devices. This becomes a real problem when sharing screenshots for UI design reviews, documentation, or printed materials, where maintaining accurate physical size or proportions is important. -- You are receiving this mail because: You are watching all bug changes.
