Many image files carry more than what shows up on screen. Cameras, phones, and editing software can embed extra information into the file itself, and it comes in three overlapping flavors that most people never have a reason to think about.<\/p>\n\n\n\n
EXIF<\/strong> (Exchangeable Image File Format) is the one most people have actually heard of, since your camera writes it automatically. It can store shutter speed, ISO, GPS coordinates, the shot date, and other camera information, and it technically has an Artist field and a Copyright field too, though almost nobody ever fills those in.<\/p>\n\n\n\n IPTC<\/strong> (International Press Telecommunications Council) is the one that matters most here. It was built decades ago for photojournalism, it’s commonly added by photographers, agencies, and publishing software, and it’s where fields such as Creator and Copyright Notice live, the closest thing an image has to a signature.<\/p>\n\n\n\n Then there’s XMP<\/strong> (Extensible Metadata Platform), Adobe’s metadata format, widely used by tools such as Lightroom and Photoshop. It mirrors and extends both of the older standards, so in practice, a lot of what people casually call “EXIF data” is really a blend of all three.<\/p>\n\n\n\n None of it decides who legally owns the image, though. Copyright ownership is a separate question from metadata, one this article gets into a bit later. What metadata gives you, in the meantime, is a way for software and other people to identify the creator or rights holder associated with the image without having to ask you directly.<\/p>\n\n\n\n None of this information changes how an image looks. A Copyright Notice field doesn’t add a single visible pixel, but it does add file size, and file size is exactly what compression is trying to cut.<\/p>\n\n\n\n That’s the logic behind metadata stripping during image optimization, ShortPixel included<\/a>. Metadata that doesn’t affect the rendered image often gets removed during that same optimization pass, to shave off extra file size. It’s technically a separate step from the pixel-level compression, though optimization tools often handle both together, since dropping data that costs nothing visually is easy savings.<\/p>\n\n\n\n For one photo, that might be a few kilobytes or considerably more, depending on what’s embedded; ShortPixel has documented cases where metadata alone took up over a megabyte on a single image. Multiply that across a media library with thousands of files<\/a>, and it adds up to a meaningful amount of storage and load-time savings.<\/p>\n\n\n\n By default, yes, and it takes more than just EXIF with it. ShortPixel treats EXIF, comments, IPTC, and XMP as one bundle: whichever way you set the Remove EXIF<\/strong> option under Settings > ShortPixel > Image Optimization<\/strong>, all four get removed or kept together.<\/p>\n\n\n\n ShortPixel’s own knowledge base has the full technical breakdown<\/a> of exactly what each setting keeps or removes, in case you want to double-check anything here.<\/p>\n\n\n\n The ICC color profile is preserved regardless of this setting, since removing it could affect how the image’s colors actually display.<\/p>\n\n\n\n Running bulk jobs from the command line instead? The shortpixel-optimize.sh script uses the same logic through a KEEP_EXIF variable in its .env file, set to 0 by default.<\/p>\n\n\n\n If you’re a photographer, an agency, or anyone whose business depends on images carrying your name, this is one setting to check before running a bulk optimization. The performance-first default makes sense for most sites. It’s just not the right call for every one.<\/p>\n\n\n\n Worried you’ve already optimized without it?<\/strong> If ShortPixel’s backup option was on, you can restore your originals, flip the setting, and re-optimize with the metadata preserved. Backup is enabled by default, but it can be turned off, so it’s worth checking your settings first.<\/p>\n\n\n\n It’s worth separating two different things: your legal right to an image, and the file’s ability to announce that right on its own.<\/p>\n\n\n\n In most countries, copyright protection generally exists automatically the moment you create an original, eligible work. It doesn’t depend on having copyright information embedded in the image’s metadata. That protection doesn’t disappear because a compression tool stripped a metadata field. What you lose is a convenient, automated way of identifying and communicating ownership or attribution, and that matters more than it sounds like it should. Google Images can use image metadata and structured data<\/a> to show creator, credit, and licensing details, and that information can make an image eligible for a “Licensable” badge in search results.<\/p>\n\n\n\n There’s also a legal wrinkle here, even though it doesn’t apply to routine optimization. In the U.S., Section 1202 of the Digital Millennium Copyright Act (DMCA) addresses certain cases of intentionally removing or altering copyright management information, though the law includes specific knowledge and infringement-related requirements.<\/p>\n\n\n\n Simply optimizing your own images for site speed is a very different situation. It’s more a reminder that copyright metadata exists for a reason beyond convenience, and stripping someone else’s is not the same thing as optimizing your own. (This is general information, not legal advice for a specific situation.)<\/p>\n\n\n\n Metadata is convenient, but it shouldn’t be the only layer of protection you rely on. It can be lost when an image is re-exported, uploaded to another platform, screenshotted, or reshared, often without anyone intending to remove it.<\/p>\n\n\n\n A few other things help alongside keeping your metadata intact:<\/p>\n\n\n\n Not by itself. Resizing changes pixel dimensions, not metadata. But if you’re resizing and compressing in the same tool, both can happen in the same step, so check each setting separately to be sure.<\/p>\n\n<\/div>\n<\/div>\n Keeping metadata increases file size compared with stripping it, though the difference varies from image to image. You still get the benefits of pixel-level compression either way; the metadata is a separate, usually much smaller, add-on.<\/p>\n\n<\/div>\n<\/div>\n It depends on the tool doing the converting and how much metadata the target format supports in the first place, since not every format handles metadata the same way<\/a>. Check after any format conversion, not just after compression.<\/p>\n\n<\/div>\n<\/div>\n Yes, using a metadata editor like Adobe Lightroom, Bridge, or ExifTool to write the fields back in manually. Automated recovery isn’t something compression tools handle, since the original data is gone once it’s removed.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n Easily optimize your pictures and generate WebP\/AVIF in bulk using ShortPixel Image Optimizer.<\/p>\n\n\n\nWhy compression tools strip metadata<\/strong><\/h2>\n\n\n\n
Does ShortPixel remove copyright info?<\/strong><\/h2>\n\n\n\n
\n
![\"\"](\"https:\/\/shortpixel.com/blog\/wp-content\/uploads\/2026\/08\/image-1024x190.png\" "\\"\\"")
<\/a><\/figure>\n\n\n\nLosing your metadata doesn’t mean losing your copyright<\/strong><\/h2>\n\n\n\n
How to keep your copyright info intact<\/strong><\/h2>\n\n\n\n
\n
Beyond metadata: other ways to protect your images<\/strong><\/h2>\n\n\n\n
\n
FAQs<\/strong><\/h2>\n\n\n
Does resizing an image also remove its copyright metadata?<\/strong><\/h3>\n
Will keeping EXIF data make my website slower?<\/strong><\/h3>\n
Does converting a JPEG to WebP or AVIF keep the copyright metadata?<\/strong><\/h3>\n
Can I add copyright metadata back after it’s been stripped?<\/strong><\/h3>\n
Try ShortPixel on WordPress for free!<\/strong><\/h3>\n\n\n\n