The WordPress 7.1 roadmap and Gutenberg 23.3 notes point to a more capable media editing flow with modal-based cropping, aspect ratio options, rotation, flip controls, metadata editing, and broader media handling. That is useful, but image editing touches public pages, responsive image sizes, caching, and editorial habits.
Use this for WordPress sites where editors crop featured images, product photos, author portraits, logos, favicon assets, Open Graph images, or campaign landing page graphics inside wp-admin.
Quick answer
WordPress 7.1 Media Cropper QA Checklist should be handled with a narrow evidence-first workflow: build media test set, run crop actions, check theme output, then verify the result before making broader changes.
What to check first
- Create staging copies of the image types editors crop most often: hero image, square thumbnail, product image, logo, favicon, and social share image.
- Test freeform crop, fixed aspect ratio crop, rotation, flip, save, cancel, and metadata changes from the real editor path.
- Confirm the theme still renders the expected image size, srcset, alt text, caption, and focal area after editing.
- Check whether WebP, AVIF, PNG transparency, and JPEG uploads behave differently in the cropper.
- Purge page cache and CDN cache before judging public pages that use edited images.
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 media test set | Create staging copies of the image types editors crop most often: hero image, square thumbnail, product image, logo, favicon, and social share image. | Edited images render correctly in the editor, frontend, mobile viewport, and social preview image size. |
| Run crop actions | Test freeform crop, fixed aspect ratio crop, rotation, flip, save, cancel, and metadata changes from the real editor path. | Alt text, captions, and attachment metadata are still present after the crop or rotation. |
| Check theme output | Confirm the theme still renders the expected image size, srcset, alt text, caption, and focal area after editing. | The browser receives the current image file after cache purge. |
| Verify metadata | Check whether WebP, AVIF, PNG transparency, and JPEG uploads behave differently in the cropper. | Editors have a short rule for when to crop in WordPress and when to use a design tool first. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
wp media image-size
wp post list --post_type=attachment --fields=ID,post_title,post_mime_type,post_date --posts_per_page=10
wp post meta get 123 _wp_attachment_metadata
curl -sSI https://example.com/wp-content/uploads/2026/06/hero.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 media test set
- Run crop actions
- Check theme output
- Verify metadata
- Purge cache
Production verification checklist
- Edited images render correctly in the editor, frontend, mobile viewport, and social preview image size.
- Alt text, captions, and attachment metadata are still present after the crop or rotation.
- The browser receives the current image file after cache purge.
- Editors have a short rule for when to crop in WordPress and when to use a design tool first.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, test WordPress 7.1 media workflows.
Beta 3 orientation and Safari media checks
For source-orientation problems, run the WordPress 7.1 Beta 3 EXIF rotation test. For iPhone media uploaded through Safari, use the Safari HEIC duplicate attachment test to correlate one browser action with one attachment family.
CDN and offload checks for corrected media
Trace corrected image orientation through every responsive and social copy with the EXIF CDN derivative cache regression test. For Safari uploads, continue with the HEIC offload idempotency test to prove conversion and retry create one attachment family.
Helpful references