WordPress 7.1 Beta 3 fixes image orientation behavior involving EXIF metadata. Orientation bugs are easy to miss because the browser, operating system, WordPress editor, image library, and CDN may each interpret or remove metadata differently. A useful regression test uses known fixtures for all relevant orientation flags and compares pixel dimensions, metadata, derivative files, responsive candidates, and actual front-end rendering.
Use this for photography, real estate, restaurant, ecommerce, and mobile-upload workflows where portrait images arrive directly from phones or cameras. Include any optimization, offload, CDN transformation, or WebP conversion layer used by the production site.
Quick answer
Create fixtures with visible corner labels and known EXIF orientation values, then upload each exactly once. Record the original hash and metadata, inspect the stored original and every generated size, and render the attachment in the block editor, Media Library, featured image, gallery, and front end at multiple viewport widths. Check CDN or optimization copies separately.
What to check first
- Record the image library and version, auto-rotation settings, image-size registry, conversion plugins, offload service, CDN transforms, and browser test set.
- Use labeled JPEG fixtures for normal, 90-degree, 180-degree, and mirrored orientations with known pixel dimensions and EXIF tags.
- Compare original upload, scaled original, thumbnails, WebP or AVIF derivatives, width and height metadata, srcset candidates, and attachment metadata.
- Render each fixture in Media Library grid and edit views, Image block, Cover block, gallery, featured image, Open Graph image, and front-end responsive sizes.
- Purge only the test image URLs, then compare origin and CDN hashes, dimensions, headers, and visual orientation.
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 |
|---|
| Prepare labeled EXIF fixtures | Record the image library and version, auto-rotation settings, image-size registry, conversion plugins, offload service, CDN transforms, and browser test set. | Each fixture has a source hash, EXIF value, and expected orientation. |
| Capture source and environment metadata | Use labeled JPEG fixtures for normal, 90-degree, 180-degree, and mirrored orientations with known pixel dimensions and EXIF tags. | Attachment dimensions and srcset descriptors match the corrected pixels. |
| Inventory every derivative and srcset candidate | Compare original upload, scaled original, thumbnails, WebP or AVIF derivatives, width and height metadata, srcset candidates, and attachment metadata. | Editor, featured image, gallery, and responsive front end show the same orientation. |
| Compare editor, front end, and CDN output | Render each fixture in Media Library grid and edit views, Image block, Cover block, gallery, featured image, Open Graph image, and front-end responsive sizes. | Origin and CDN copies agree after a targeted purge. |
Why this usually happens
- Some viewers rotate pixels at display time while other tools physically rotate and remove the EXIF flag.
- Width and height metadata can remain from the pre-rotation orientation.
- Optimization plugins may process the original before or after WordPress correction.
- A CDN can keep an older transformed copy after attachment metadata changes.
- Mirrored EXIF cases expose logic that a single 90-degree portrait test misses.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
fixture: exif-orientation-6-corners.jpg
source_pixels: 4032x3024
exif_orientation: 6
expected_display: 3024x4032
attachment_id: 9302
metadata_width: 3024
metadata_height: 4032
srcset_candidates_checked: 5
cdn_orientation: pass
editor_orientation: pass
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.
- Prepare labeled EXIF fixtures
- Capture source and environment metadata
- Inventory every derivative and srcset candidate
- Compare editor, front end, and CDN output
- Isolate the processing layer when any rendition disagrees
Decision rule
Pass only when displayed orientation, stored dimensions, responsive metadata, editor previews, front-end output, and CDN copies agree for every tested EXIF case. Do not repair the database until the failing transformation layer is identified.
What to tell the client or owner
Give the site owner the affected version, exact workflow, observed result, business impact, evidence location, temporary control, named owner, and next review time. Remove credentials and personal data from shared screenshots and logs.
Production verification checklist
- Each fixture has a source hash, EXIF value, and expected orientation.
- Attachment dimensions and srcset descriptors match the corrected pixels.
- Editor, featured image, gallery, and responsive front end show the same orientation.
- Origin and CDN copies agree after a targeted purge.
Mistakes to avoid
- Do not rely on Finder or Photos as the only source preview.
- Do not test only orientation value 6.
- Do not regenerate all production thumbnails during diagnosis.
- Do not strip metadata before recording the original EXIF value.
Questions teams ask during testing
Can the original file stay unchanged while thumbnails rotate?
Yes, depending on the WordPress and plugin pipeline. The important point is that metadata and displayed renditions remain consistent and intentional.
Why does desktop look correct while mobile is rotated?
A different srcset candidate or CDN transform may be selected on mobile. Inspect the actual requested image URL and its pixel orientation.
When HandL WP should help
Bring in HandL WP when this affects a production site, paid lead flow, checkout, email delivery, or a managed fleet. We can preserve evidence, isolate the failing layer, make the smallest corrective change, and verify the result across WordPress, the external service, logs, and the user journey.
If this is active on a production site, fix WordPress image orientation.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references