Remove Metadata From a Photo Before It Becomes Your LinkedIn Profile Picture

A LinkedIn profile photo is a different object from a headshot you attach once to a job application. The application file lands in one inbox or one applicant-tracking system. The profile photo is the picture that sits on a public professional identity until you change it. People save it. Recruiter tools copy it. Search engines index the page it lives on. If the JPEG still carries GPS from a phone shot in a spare bedroom, that pin is not a one-time leak. It is a standing, ongoing exposure attached to a file that is easy to download for years.

That is the reason this page exists next to a separate guide on wiping photos before a job application. The ATS case is a submission. The profile case is a public asset. MetadataWipe rebuilds a JPEG or PNG in your browser so typical GPS, timestamps, and camera tags are not copied into the copy you set as the LinkedIn photo. Processing stays on this device.

Why a profile photo carries more persistent risk than a one-off application photo

Duration is the first difference. An employer may delete application materials after a hiring cycle. LinkedIn does not retire your headshot when a role closes. The same file remains the default image on posts, comments, connection requests, and search previews. Anyone who saved it in 2024 still has the bytes in 2026 unless you replaced the photo and they did not keep a copy.

Audience is the second. A job application is addressed. A LinkedIn profile is designed to be found. Open profiles are crawled. Even restricted profiles are still shown to people in your network and to tools those people use. A GPS tag that would have been seen by one HR coordinator on an application PDF can, on a profile photo, be sitting in a file that recruiters, clients, and strangers can save without asking.

Reuse is the third. The JPEG you set as a LinkedIn photo is often the same file you later drop into a speaker kit, an about-page, a conference badge preview, or a resume. If you never wiped it, every reuse republishes the same header. Wiping before the first public placement is cheaper than hunting copies later. For photos that also describe an office, a lab, or a client site, see photo metadata and workplace confidentiality. For the one-employer attachment workflow, see remove metadata from a photo for a job application.

What a phone-shot LinkedIn headshot typically still contains

Start with GPS. Phones write latitude and longitude when Location Services is enabled for Camera. A “professional” headshot taken against a blank wall at home is still a geotagged file. Remote workers and freelancers do this constantly: good window light, a laptop as a stand, no studio. The pixels show a face. The header can show the apartment. Combined with a public city line on the profile, that is more locating than the byline you intended.

Timestamps are next. DateTimeOriginal can show that the “new headshot” was taken on a Sunday night, or that a series of profile updates were shot in the same room over a weekend. That is rarely a secret worth leaking, and it is never required for LinkedIn to display a face.

Device tags — Make, Model, and sometimes serial-adjacent MakerNotes — fingerprint the phone. They do not make the photo look more professional. They do help someone who already has another photo from the same device join the two files. Software tags from Portrait mode or a retouching app add another breadcrumb. A full wipe is simpler than trying to keep “just the copyright line” and hoping GPS is gone.

MetadataWipe does not change pixels. A street number in a window, a child’s art on the fridge, or a badge lanyard in the mirror are still in the picture. Crop those first, then strip tags so the editor does not write a fresh Software field onto an otherwise-clean file.

How to strip a profile photo in MetadataWipe before you set it on LinkedIn

1. Export a JPEG or PNG you will actually use. iPhone HEIC must be saved as JPEG first. Studio files that are still RAW or DNG are not what this tool opens. Export the version you would crop in LinkedIn.
2. Open the MetadataWipe tool. Drop the file. Confirm GPS, DateTimeOriginal, and Make/Model in the panel before you strip, so you know the wipe did something afterward.
3. Strip locally. The canvas rewrite does not copy typical EXIF, IPTC, or XMP into the new file. Your original stays on disk.
4. Download the cleaned file (the name includes -metadatawipe). Re-open that download in the same panel. GPS and camera tags should be gone.
5. Set only the cleaned file as the LinkedIn profile photo. Do not pick the original from Recents because it “looks sharper.” Recents still holds the geotagged master. Repeat the same wipe for the banner image if that file was also a phone photo of a room or a street.

Turning off Location Services for Camera helps future shots. It does not rewrite the headshot you already took. Wipe the file you have.

A standing exposure: the remote-worker headshot that geotagged home

A freelancer whose only “studio” is the spare room. They shoot a headshot on a phone, crop it in Photos, and set it as the LinkedIn photo the same afternoon. Clients, collaborators, and strangers can save that image. If GPS survived, the file is a map pin of the home office — the same address they would not print on a public invoice. This is not a one-time job-application risk. The photo stays up while they take new contracts. Strip it before it becomes the profile picture, not after someone emails a screenshot of the EXIF panel.

A remote employee who updates the photo after a rebrand. They reuse last year’s living-room JPEG because the lighting was good. LinkedIn is a new placement of an old header. Wipe on reuse. A crop for LinkedIn’s circle does not delete DateTimeOriginal.

A consultant whose headshot was taken at a client site “because the lobby looked professional.” The GPS is the client’s building. That can be an NDA problem as well as a home-address problem. Workplace-confidentiality tags and client-site pins are covered in more depth on the confidentiality page linked above. The profile-photo point is the same: the file will be public until you change it.

The same JPEG in a speaker kit and on LinkedIn. Event organizers often ask for a “hi-res headshot.” If you send the camera original in a zip and also set it on LinkedIn, you have published the header twice. Wipe once, then send that copy everywhere.

The mistake of assuming LinkedIn will strip metadata for you

Treating LinkedIn like Instagram. Some social platforms re-encode uploads and, as a side effect, drop a lot of EXIF. That is not a contract, and it is not the same for every product surface. Profile photos, page logos, and feed images can take different pipelines. You cannot open LinkedIn’s output in an EXIF viewer and call that a policy. You can control the file you submit.

Overstating the platform risk in the other direction. It is honest to say you should not rely on LinkedIn. It is not honest to claim, without documentation, that LinkedIn always preserves GPS on every profile photo. Platforms change compression. The safe habit does not depend on guessing the current pipeline: strip first, then upload the cleaned copy.

Wiping the profile photo and leaving a geotagged banner, or a geotagged image in Featured. Each file has its own header. Process every photo that will live on the public profile.

Editing in LinkedIn’s cropper and assuming the header died. Cropping pixels is not a metadata wipe. Verify the file you kept on disk, and prefer setting a file you already cleaned.

Using the same uncleaned JPEG in an application portal “because LinkedIn already has it.” The ATS copy is a separate submission. Wipe that copy too, using the job-application workflow if that is the actual destination.

Related guides

See also:

• Photo metadata and workplace confidentiality
• Remove metadata from a photo for a job application