WordPress 7.1 Beta 1 introduces a Media Editor modal that brings cropping, rotation, and metadata editing together. A privacy test should trace a synthetic image with known EXIF GPS markers through the original upload, browser processing, edited file, generated sub-sizes, attachment metadata, CDN, image optimization, backup, export, and deletion paths.
Use this for newsrooms, healthcare and legal teams, schools, real estate sites, agencies, field-service businesses, and anyone publishing images where camera location or device metadata could reveal sensitive information.
Quick answer
WordPress 7.1 Media Editor EXIF Location Privacy Test should be handled with a narrow evidence-first workflow: build a synthetic exif fixture, exercise every edit path, inspect every derivative, then verify the result before making broader changes.
What to check first
- Create a synthetic image with a clearly documented test GPS coordinate, camera make, capture time, orientation, caption, credit, and no real person's data.
- Upload it in each supported test browser, then crop, rotate, edit metadata, replace the file, and record whether client-side or server-side processing handled each action.
- Download and inspect the original, edited file, every generated size, WebP or AVIF derivative, optimizer output, CDN object, social preview, and backup copy.
- Compare EXIF and attachment fields before and after edit, regenerate thumbnails, clear edge cache, and verify the public URL rather than only the Media Library screen.
- Run export and deletion workflows and document which historical copies remain under the site's backup and retention policy.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Build a synthetic EXIF fixture | Create a synthetic image with a clearly documented test GPS coordinate, camera make, capture time, orientation, caption, credit, and no real person's data. | Every downloaded public image has a recorded hash, dimensions, format, processor, and EXIF result. |
| Exercise every edit path | Upload it in each supported test browser, then crop, rotate, edit metadata, replace the file, and record whether client-side or server-side processing handled each action. | Synthetic GPS data is absent from all public derivatives unless the approved policy explicitly keeps it. |
| Inspect every derivative | Download and inspect the original, edited file, every generated size, WebP or AVIF derivative, optimizer output, CDN object, social preview, and backup copy. | Attachment fields, file metadata, CDN objects, optimizer copies, and social previews are not confused with one another. |
| Purge and refetch public copies | Compare EXIF and attachment fields before and after edit, regenerate thumbnails, clear edge cache, and verify the public URL rather than only the Media Library screen. | Deletion and backup retention have an owner, duration, and tested restore or erasure boundary. |
Why this usually happens
- The original file and generated derivatives can follow different metadata policies.
- A browser-side edit may not update an older CDN or optimizer copy.
- Attachment fields in WordPress are separate from EXIF embedded inside the image file.
- Backups and social caches can keep a location-bearing historical copy after the current URL changes.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
# Download each controlled output before inspection.
exiftool test-original.jpg
exiftool test-cropped.jpg
exiftool test-rotated.webp
# Record hashes so an old CDN object is easy to spot.
shasum -a 256 test-original.jpg test-cropped.jpg test-rotated.webp
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Build a synthetic EXIF fixture
- Exercise every edit path
- Inspect every derivative
- Purge and refetch public copies
- Document retention
Decision rule
Approve the media workflow only when the organization knows which metadata is intentionally retained, sensitive GPS markers are absent from every public derivative, current CDN objects match inspected files, and historical backup retention is documented.
What to tell the client or owner
Provide the WordPress build, browser, source fixture hash, synthetic EXIF fields, edit sequence, processor path, derivative URLs and hashes, optimizer and CDN settings, inspection output, cache result, and retention policy.
Production verification checklist
- Every downloaded public image has a recorded hash, dimensions, format, processor, and EXIF result.
- Synthetic GPS data is absent from all public derivatives unless the approved policy explicitly keeps it.
- Attachment fields, file metadata, CDN objects, optimizer copies, and social previews are not confused with one another.
- Deletion and backup retention have an owner, duration, and tested restore or erasure boundary.
Mistakes to avoid
- Do not upload a real sensitive photograph as the fixture.
- Do not conclude EXIF is removed because the WordPress attachment screen does not display it.
- Do not inspect only the original while the public page serves a derivative.
- Do not purge CDN objects before recording their hashes and metadata evidence.
Questions teams ask during testing
Does WordPress always remove GPS metadata?
Do not assume it. The result can vary by file, processor, edit path, plugin, generated size, and delivery layer. Test the exact production stack with synthetic metadata.
Is changing attachment metadata the same as changing EXIF?
No. WordPress title, caption, description, and alt text are database fields. EXIF is embedded in the image file. Inspect both surfaces independently.
When HandL WP should help
HandL WP should help when a public image may expose location metadata or edited files do not match the CDN copy. We can trace the original and every derivative, then verify cache and retention behavior without using personal photographs.
If this is active on a production site, audit WordPress image metadata privacy.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references