Does a public records request cover a photo's metadata, too?

One note before anything else: this page quotes the federal Freedom of Information Act, 5 U.S.C. 552, because its wording is public and stable enough to quote directly. State and local public-records or "sunshine" laws use different language, different exemptions, and sometimes a different word entirely for the same idea. This is general information about how the federal statute is written, not legal advice for a specific request, agency, or jurisdiction.

Why this is a different problem from the rest of the site

Every other legal-angle page here reasons about a private party: a club, a school, a litigant, a person being sued or doing the suing. This page is about an agency that is legally required to hand records to the public on request, and that has to decide, file by file, what in that record it is allowed to keep back. That duty runs in a direction most of this site never touches: not "how do I protect myself," and not "what must I preserve for a case," but "what am I obligated to release, and what am I obligated to withhold, in the same file, at the same time."

A photo responsive to a public-records request is not one decision. It is at least two: is anything in the visible image exempt — a face, a license plate, a document in the background — and is anything in the embedded metadata exempt — a GPS coordinate, a device owner field, a case-handler's name typed into an Author tag. Agencies have redaction habits for the first kind, built around blacking out or blurring pixels. Far fewer have a habit of opening a photo's tag layer at all, because nothing about looking at a photo on screen tells you the tags are there.

What the statute actually says

The privacy exemptions are written around "files" and "records," not file formats. 5 U.S.C. 552(b)(6) exempts "personnel and medical files and similar files the disclosure of which would constitute a clearly unwarranted invasion of personal privacy." 5 U.S.C. 552(b)(7)(C) exempts law-enforcement records to the extent disclosure "could reasonably be expected to constitute an unwarranted invasion of personal privacy." Neither clause says anything about JPEGs, EXIF, or tags, and neither needed to: the test is about what disclosure of a record would reveal about a person, not about which layer of a file the revealing fact sits in. A home address is not less exempt for being stored as GPSLatitude and GPSLongitude instead of a street name typed in a letter.

The segregability rule is the load-bearing sentence for this whole page. The statute states: "Any reasonably segregable portion of a record shall be provided to any person requesting such record after deletion of the portions which are exempt under this subsection." It adds that "the amount of information deleted, and the exemption under which the deletion is made, shall be indicated on the released portion of the record," unless that indication itself would cause the harm the exemption protects against, and that where technically feasible, the indication should appear at the place in the record where the deletion was made. Read plainly, this is a rule against withholding more than necessary. A photo where the only exempt content is one embedded field is the textbook case it describes: release the image, remove the field, and — where feasible — note that something was removed and why.

Metadata is already treated as part of a record elsewhere in federal practice. This statute does not use the word "metadata," but federal records-management guidance does. A National Archives records bulletin on transferring permanent electronic records defines metadata elements as the administrative, descriptive, and technical information that "describe the structure and content of electronic records" and provide the contextual "who, what, where, when, and why" of a record. That is a records-management rule, not a FOIA case, and it does not settle how any particular exemption applies — but it shows that the idea of metadata as part of a record's substance, not an attachment bolted onto it, already has official footing in how the federal government documents its own files.

The duty cuts both ways — and both failure directions look identical from the outside

A released photo with no visible problem and a released photo that fully complies with the exemption and segregability rules can look exactly the same to a requester who never opens a metadata reader. That is what makes this job easy to get wrong in either direction without anyone noticing until much later.

1. Under-redaction: the pixels were cleared, the tags were not. An officer blurs a confidential informant's face or crops a license plate out of frame, satisfies the exemption for what a viewer can see, and releases the original file unchanged at the byte level — GPS coordinates pointing at a safehouse, an Author or Owner field naming an internal case handler, a device serial that ties the image back to a specific agency phone or camera, all still intact in the tag layer nobody opened. The visible redaction answered a question the embedded fields were never asked.
2. Over-withholding: the whole file was pulled because of one field. The opposite mistake is treating any embedded exempt fact as a reason to withhold the entire photo, or an entire batch, rather than removing just the offending field and releasing everything else. The statute's own segregability language does not support that shortcut — it requires removing the exempt portion, not the record.

Both mistakes come from the same root cause: reviewing the picture and reviewing the file are treated as one step when they are two, and only one of them has an established habit behind it.

A workflow for reviewing an image before it goes out under a records request

1. Treat the tag layer as a field of the record, not a detail of the format. Before any photo in a responsive set is marked ready to release, assume it carries an embedded tag layer and plan to look at it, the same way you would plan to read a document's text before releasing it.
2. Read the actual field values with a real metadata tool, not a presence check. You need to know what GPSLatitude says, not just that a GPS tag exists, and you need that before you can apply the exemption test field by field.
3. Decide per field, which fields are exempt and which are routine. A generic capture date or a camera make and model is rarely the kind of fact either privacy exemption is protecting. A coordinate, a personal device identifier, or a named individual in an Author or Comment field needs the same analysis you would give the same fact printed on a page.
4. Redact pixels and redact tags as two separate jobs, in that order. Cover or crop whatever needs to be visually redacted first. A tag-clearing step applied afterward does not retroactively protect anything that is still visible in the pixels, and a visual redaction does nothing to a tag.
5. Keep the untouched original in the case file. If a requester appeals the redaction, or a court reviews it, the agency needs the unredacted file to show what was withheld and justify why — the same preservation discipline this site's page on how courts use photo metadata as evidence describes for litigation, applied here for a records-appeal file instead of a trial exhibit.
6. Log what was removed and under which exemption, where feasible. The statute's "indicated on the released portion" language is a documentation duty, not a suggestion. A rebuild step that silently clears every tag at once gives you nothing to put in that log.
7. Do not let a convenience tool stand in for the determination. A browser-based cleaner can clear a field once you have decided it is exempt. It cannot tell you that it is.

Common mistakes and misconceptions

"We blurred the faces, so the privacy exemption is handled." That satisfies the exemption for the visible image. It says nothing about an embedded GPS tag, device owner field, or author name sitting in the same file, unopened.

"FOIA doesn't mention metadata, so it must not apply to it." The statute does not mention JPEGs or PDFs either. The exemption and segregability language is written around what a record reveals and what portion of it can be withheld, not around which layer of a file a fact is stored in.

"Running every photo through a metadata stripper before release makes us compliant." A blanket strip removes exempt fields, but it also removes anything that was not actually exempt and should have been released as part of the record, and it leaves no documentation of what was taken out or why — which the statute's own indication language calls for. Compliance is a field-by-field decision with a record of that decision, not a single irreversible pass.

"Our document redaction software already covers this." Most redaction tooling built for a FOIA office is built around blacking out visible text in PDFs and scanned documents. Whether it surfaces an image's embedded EXIF, IPTC, or XMP fields at all is a question worth asking the vendor directly rather than assuming.

"The requester only asked for the photo, not the metadata." A record is reviewed and produced in the form it exists. Embedded fields are part of that form unless they are separately exempt — a requester does not have to specifically ask for the tag layer any more than they have to specifically ask for the second paragraph of a letter.

Where this site's tool fits, and where it does not

MetadataWipe accepts image/jpeg and image/png only, one file at a time. It decodes the image, draws it to a canvas at the original pixel dimensions, and exports a new file from that canvas — a fresh lossy encode for JPEG, a fresh PNG otherwise — leaving the original file on your device untouched. All of that runs inside the page itself; nothing is sent anywhere, which is also why there is no server-side log of anything that was ever processed through it.

For an individual protecting their own privacy, that last point is the whole appeal of the tool. For an agency with a documentation duty, it is close to a disqualifying gap: there is no audit trail, no record of which field was removed or when, and no way to keep a releasable capture date while dropping only an exempt coordinate — the rebuild clears everything the canvas redraw touches, all at once. Its built-in check is a heuristic, not a determination: for a JPEG it looks near the start of the file for an APP1 segment carrying the Exif identifier and for the literal text GPS, and for a PNG it walks chunk types looking for eXIf, tEXt, iTXt, zTXt, tIME, and iCCP — useful as a quick "is there anything here" check, not as the field-level review a release decision requires. Use a full metadata reader to see actual values before deciding what is exempt, and keep whatever record-keeping process your office already uses for redactions; this tool is for clearing a file after that decision is made, not for making it.

Related guides

See also:

• Is photo metadata personal data under privacy law?
• How courts use photo metadata as evidence