Short answer, and it corrects the question slightly: WordPress 7.0 did not rebuild the Media Library. It restyled it along with the rest of the admin and made one change that people notice immediately, an accessibility label that now sits on top of each thumbnail in grid view. The functional changes came in WordPress 7.1, released 19 August 2026: infinite scrolling in the grid by default, a new media editor modal that replaces the old inline crop tool, image processing that happens in your browser before upload, and native support for AVIF, HEIC and HDR gain maps. If you cannot find an image you uploaded last week, the cause is almost always one of those two things, and both have a fix.
Verified against WordPress 7.1 "Mary Lou", released 19 August 2026. Last verified 24 August 2026. Sources named in the text are WordPress's own: the 7.0 and 7.1 Field Guides on make.wordpress.org, the 7.1 release announcement, the 7.0 accessibility dev note (23 May 2026), and a WordPress.org support thread. Admin screens change between releases. Check which version you are running before assuming a step here is wrong.
Be careful with "7.0 media library changes" articles
There is a lot of content dated May and June 2026 listing Media Library features for WordPress 7.0 that we could not find in any WordPress.org source. So here is the honest position, with the reasoning shown.
The WordPress 7.0 Field Guide has no Media Library section at all. The 7.1 Field Guide does, and it is short: infinite scrolling enabled by default in the grid with a per-user option to go back to the old behavior, plus fixes to upload counting and duplicate caption IDs. If a feature like media folders had shipped in either release, that is where it would be documented, and it is not there. We could not confirm that core gained folders, collections or a built-in file replacement in 7.0 or 7.1, so this page does not tell you they exist.
What 7.0 genuinely did to media is recorded in its accessibility dev note, and it is real work: using the Media Library with voice control technology is now possible, and where an image carries alternative text embedded in its photo metadata, WordPress imports it and sets it as the image's text alternative automatically.
The 7.0 change that makes images harder to scan
This is the single most reported Media Library complaint after the 7.0 update, and it has a documented explanation.
In grid view, the Media Library now overlays the media item's title on the thumbnail. A site owner raised it in the WordPress.org support forums after the 7.0 upgrade, saying the overlay made it hard to locate images. The reply confirmed the behavior is intentional: the text is an accessibility label for the media item's title, and it exists to help voice-control users find and select images. It is the front end of the voice control support the 7.0 accessibility note describes.
Two things follow, and you should know both before you go hunting for a setting:
- There is no built-in option to switch it off. The workarounds discussed in that thread are CSS, added through a plugin, an mu-plugin or a code snippets plugin, either to hide the labels entirely or to reveal them only on hover after a short delay. The person who reported it chose to wait for a future core release rather than add a plugin, which is a reasonable call.
- Switching to list view sidesteps it. The Media Library has had a grid view and a list view for years, and the toggle is still at the top of the Media Library screen. List view gives you filenames in a column, which is usually what you wanted when you were scanning for something specific anyway.
If the card-and-grid feel of the whole admin is the underlying problem, the same shift affected your Posts and Pages screens, and DataViews explained without the jargon covers what happened there and why. The Media list view is built on the same system, so plugins that customize Posts, Pages or Media list views were all affected by the same 7.0 change.
Finding a file you know you uploaded
Work through these in order. The first two solve most cases.
- Search by filename, not by what the picture shows. WordPress matches on the attachment's own text fields, and the filename is the one you can predict. If you uploaded
IMG_4471.jpgstraight off a phone, search4471. - Check whether the list is actually finished loading. In 7.1, the grid uses infinite scrolling by default, so the library keeps loading as you scroll rather than showing a Load more button. On a big library, an image can be present but not yet loaded. Scroll further before concluding it is gone.
- Switch to list view and sort by date. Something uploaded last week is near the top of a date-sorted list, whatever it is called.
- Confirm you are looking at the whole library. The media picker inside the editor and the full Media Library screen are different views of the same files, and the picker can open with a filter already applied.
- Check the trash. A deleted attachment is not always gone immediately.
If none of that finds it, the file may have been uploaded under a different user account or removed by a plugin that manages media, which is a different problem from a Media Library change.
Turning infinite scrolling off in 7.1
WordPress documented this one properly, which is a relief. The dev note published 23 July 2026 records that the media_library_infinite_scrolling filter kept its signature and only its default value changed, from false to true, so any site that had already set the filter is unaffected and its setting still takes precedence.
For everyone else there are two routes. A per-user option in the User Profile lets an individual turn infinite scrolling off and go back to the Load more button, which is the route to use if it is just you and just this browser habit. The media_library_infinite_scrolling filter, returning false, switches the default back site-wide and belongs in a small site-specific plugin.
We are describing the profile option by what it does rather than quoting a label, because we have verified the option exists from WordPress's own dev note but have not seen the 7.1 profile screen on this site. Look for it on your own profile screen, alongside the other Personal Options, in the same block that holds the admin color scheme picker.
Replacing a file: what core does and does not do
Core WordPress still has no "replace this file" button, and 7.1 did not add one. This is the thing people most often expect to find and most often cannot, so it is worth stating plainly rather than sending you looking.
What 7.1 did add is a new media editor modal that replaces the previous inline cropping tool. WordPress's own announcement describes it as bringing freeform and aspect-ratio cropping, horizontal and vertical flipping, precise rotation control, and metadata editing together in one place, reached from the same Crop entry point as before. That edits the image you already have. It does not swap in a different file.
So if you need to put a new version of an image at the same address, your options are:
- Upload the new file and update where it is used. Reliable, and tedious in proportion to how many posts use the image.
- A third-party plugin. The WordPress.org plugin directory carries plugins for this, of which Enable Media Replace is the long-established one. We have not tested it on this site, so treat that as a starting point for your own evaluation rather than a recommendation, and try it somewhere that is not your live site.
There is a good reason core is cautious here. Replacing a file in place means the same URL serves different content, which interacts with caching, with CDNs and with every copy of that URL already saved elsewhere. A plugin can make that choice for you; core declining to make it by default is defensible.
Uploads changed underneath you in 7.1
The other 7.1 media change is invisible until something behaves differently. Image compression, resizing and thumbnail generation now happen in the browser before the file is sent, and 7.1 adds native support for AVIF, HEIC and HDR gain maps, the formats modern phones and cameras already produce.
The practical upshot for a site owner is that uploads that used to fail on a server limit may now succeed, and that the file arriving on your server is not always byte-for-byte the file you selected. We covered the mechanics separately in what actually changed in WordPress 7.1 media processing, and the wider release is summarized in our guide to what shipped in 7.1.
FAQ
Did WordPress 7.0 add media folders?
Not that we could verify. The 7.0 Field Guide has no Media Library section, and the 7.1 Field Guide's Media library section covers infinite scrolling and two bug fixes. Organization in core is still search, filters, list view sorting and the attachment's own fields.
How do I get rid of the text sitting on top of my thumbnails?
There is no built-in setting. It is an intentional accessibility label added in 7.0 to support voice control. The workarounds discussed in the WordPress.org support forums are CSS, added through a plugin or an mu-plugin. Switching to list view avoids the overlay without adding anything.
Why does my Media Library keep loading as I scroll?
That is 7.1's default. Infinite scrolling replaced the Load more button in the grid view. There is a per-user option on your profile screen to switch it back, and a filter for changing it site-wide.
Can I replace an image without changing its URL?
Not with core. Core 7.1 lets you crop, flip, rotate and edit metadata on an existing image through the new media editor modal, but it does not swap the underlying file. That job needs a plugin or a re-upload.
Do these changes affect images already on my site?
Existing files are not reprocessed by the 7.1 upload changes, which apply to new uploads. The 7.0 grid label is a display change in the admin only and does not alter your files or your public pages.
