Descripción
WordPress will not let you change the file behind an existing attachment. You delete, re-upload, then hunt down thirty broken images by hand.
EvoMedia replaces the file in place, keeps the attachment ID, and rewrites every reference to it across your whole database – post content, postmeta, and the serialized structures page builders and custom fields store their data in.
That last part is the whole point. An image URL is not only in your post content. It is buried inside Elementor’s JSON, inside ACF fields, inside WooCommerce gallery meta – all of it serialized, where a naive search-and-replace corrupts the data and takes the page down with it. EvoMedia unserializes, replaces, and re-serializes each value, so the byte lengths stay correct and nothing breaks.
The same engine then lets it do something no image optimizer does: convert a JPEG to WebP and keep the attachment, renaming photo.jpg to photo.webp and repointing every reference at the new file. Other plugins keep the original and add a parallel file served through an .htaccess rule, a <picture> tag or a CDN. EvoMedia changes the actual file on your disk. There is no rewriting layer at page-render time – nothing to break when you switch hosts, and nothing to un-install later.
And once your library grows, EvoMedia helps you see into it: an index of where every image is actually used, so you know what is safe to remove – plus reports of the duplicate and orphaned files quietly wasting your disk.
Everything runs on your own server, through Imagick or GD. No account, no API key, no credits, no monthly quota, no upload limit. Your images are never sent anywhere.
What it does
- Replace media, safely – upload a new file over an existing attachment. Keep the current file name and the URL never changes; or adopt the uploaded file’s name; or change format entirely. Every reference across posts and postmeta is rewritten, serialized data included. Optionally back up the current file first, edit the title, set the date.
- Convert to WebP, AVIF or JPEG – whichever your server can encode, automatically on upload or in bulk across your existing library, with progress feedback. The System Info page shows exactly which formats your image driver supports.
- Manage image sub-sizes – pick which of WordPress’s resized copies get generated on upload, and switch off the ones your theme never uses so WordPress stops making them: faster uploads and less clutter from here on. See a live count of how many images in your library have each size, and regenerate the whole library to match in one click. WordPress core sizes are flagged, so you never turn one off by mistake.
- Resize oversized uploads – optionally cap every incoming image at 2560px and drop the full-size original WordPress would otherwise keep beside it, so oversized photos never bloat your library. Off by default; nothing changes until you switch it on from the upload panel.
- See where every image is used – build an index of your content, then read a count on each image showing how many places refer to it. Open it to see the exact pages, posts, custom fields and site settings, and which size each one uses. Sort by it to bring the unused ones together, and get a report of pages asking for files your library no longer has.
- Find duplicate images – spot pictures your library holds more than once, compared byte for byte rather than guessed from their size, with the disk space the extra copies are wasting. Entries that merely share one file on disk are listed apart, because deleting one of those would take the file the others use.
- Find orphaned files – list files sitting in your monthly upload folders that no Media Library item claims, each with a preview. Only the year and month folders WordPress itself creates are scanned, so caches, page-builder folders and backups are never touched, and any file your content still asks for by name is flagged as still in use.
- A record of every rewrite – when Replace renames a file it rewrites the references to it across your posts, custom fields and site settings; that history is listed, so you always know what changed and where.
- Backup and restore – the original is archived before every conversion, and can be restored or deleted per image or in bulk.
- Compression quality – one slider, from 10 to 100. A master switch turns the engine off without deactivating the plugin.
- Control Center – your whole library on one screen: sort, search, preview, download, see each file’s format, size and backup state.
- System Info – a one-click report of what your server can actually do, and of every other plugin EvoMedia has to coexist with.
Why the serialization matters
Try this with any other tool: put an image in an Elementor section, then rename the file. Elementor stores its layout as a serialized PHP array inside postmeta, and every string in it is prefixed with its own byte length. Change photo.jpg to photo.webp with a plain SQL replace and the recorded length no longer matches the string. PHP refuses to unserialize it. The section disappears.
EvoMedia walks the structure, replaces the value, and lets PHP recompute the lengths. This is why it can offer replace, format conversion and (in the Pro add-on) renaming at all – and it is the part that took the longest to get right.
Take control of the sizes WordPress generates
Every upload, WordPress quietly creates a stack of resized copies – thumbnail, medium, large, and hidden HiDPI versions – whether your theme uses them or not. EvoMedia lists every registered size with a live count of how many images in your library have it, lets you turn off the ones you don’t need (only new uploads and regenerations are affected – files already on disk are left alone), and regenerates your whole library to match with a single button and a progress bar. Core sizes are flagged, so you never switch off one the theme relies on by accident.
Know which images you can actually delete
Every library accumulates images nobody uses, and the reason they are never cleared out is that you cannot tell which ones they are. Deleting the wrong one takes a page down.
EvoMedia scans your posts, pages, custom fields and site settings and records where each image is referenced – including the ones page builders name by ID with no URL to search for, and the ones held in a category image, an author profile or your site logo. Each image then carries a count you can sort by, and opening it lists the exact places, with the size each one uses.
It reports only what it can prove. An image referenced solely from a theme file, a stylesheet or an external service cannot be seen from the database, and every list says so rather than pretending otherwise. An image that has not been scanned yet shows “?” and never “0” – because “nobody uses this” and “nobody has looked” are different answers, and confusing them is how cleanup tools delete pictures that were still on a page.
Built to coexist
Media plugins break each other. EvoMedia is written to notice what else is installed:
- WPML and Polylang – translated attachments share one file. EvoMedia keeps every language sibling in sync and collapses duplicates in its own lists.
- Page builders – Elementor and friends store their data as slashed JSON inside postmeta. EvoMedia writes exact bytes rather than letting WordPress re-escape them.
- Cloud offload – if WP Offload Media, Cloudinary, Media Cloud, WP-Stateless or S3 Uploads is active, EvoMedia refuses to touch the files rather than corrupt your remote bucket, and tells you why.
Requirements
PHP 8.1 or later, and either Imagick (recommended) or GD. Which output formats you can use depends on your host’s image driver – WebP and AVIF are common, JPEG XL is rare; the System Info page tells you exactly what your server can do.
EvoMedia Pro
Every WordPress library quietly fills with weight nothing uses: the same photo uploaded three times, sub-sizes your theme never touches, the full-resolution originals WordPress keeps beside every large image, and files left orphaned by years of renames and imports. It swells your backups, slows every migration, and quietly runs up your storage bill – and it never gets cleaned out for one reason: you cannot safely tell what is still in use.
The free EvoMedia shows you exactly where all that waste is. EvoMedia Pro is what clears it – built on the same link-safe engine, so it does the one thing other cleanup plugins get dangerously wrong: it never removes anything your site still needs.
Before it deletes a single file, the Pro re-checks your live content at that moment, not some stale scan. An image still used anywhere is left alone. A resize that would break a page is refused, and shows you which posts to fix first. Merging duplicates moves every reference – in posts, meta and page-builder data, by URL and by ID – onto the copy you keep before the others go. You get the disk space back without the broken images.
- Reclaim the space unused images waste – the free “Used in” count shows which pictures nothing on your site points at; the Pro removes them, one at a time or in bulk, re-checking live and refusing to delete a file another library entry shares.
- Collapse duplicate uploads into one – the same image uploaded three times is three times the disk. The Pro merges a set onto the copy you keep, repointing every reference first, then removing the rest. Reversible.
- Clear orphaned files – the leftovers of old renames and imports that no library item claims, often the single heaviest files on your disk. Deleted only after a fresh re-scan, and never while your content still asks for them.
- Strip the oversized “-scaled” originals – WordPress keeps a full-resolution copy beside every image over 2560px, frequently several megabytes each, named by nothing and invisible in the admin. Clear them library-wide while keeping the image people actually see.
- Delete the sub-sizes you turned off – the free build stops generating them; the Pro removes the copies already on disk across your whole library, and can regenerate a single size for every image in one pass.
- Resize on your own terms – set your own maximum width and height on upload instead of the fixed 2560px cap, and shrink any single image already in your library straight from the Control Center: proportional, never enlarging, and refusing rather than breaking a page that uses the old size.
- Rename without breaking anything – rename a file from the Media Library and have every reference rewritten, serialized page-builder and ACF data included, exactly like Replace. Reversible.
- And more – JPEG XL uploads where your server supports them, and a backups manager to browse, download and delete your archived originals.
EvoMedia Pro installs alongside this plugin and needs it to run. It is available from the author at store.gfxproductions.com.
None of that code is in this plugin. This plugin is not a trial and has nothing locked, disabled or limited. There is no licence check, no upsell nag, no counter, no expiry, and no cap on how many images you may process. Everything it ships, it does.
Capturas de pantalla








Instalación
- Upload the
evomediafolder to/wp-content/plugins/, or install it through Plugins Add New. - Activate it through the Plugins menu.
- Go to EvoMedia Format Conversion to choose your target format and quality.
- Upload an image, or select existing ones and run a bulk conversion.
Visit EvoMedia System Info first if you are unsure whether your server supports WebP.
FAQ
-
Will converting break the images already used in my posts?
-
No. EvoMedia keeps the attachment and updates WordPress’s own metadata, so everything that renders through WordPress keeps working. And if a replace changes the file’s name or its format, every reference in posts and postmeta is rewritten to match – serialized data included.
-
Will replacing an image change its URL?
-
Only if you ask it to. Keep the current file name and the URL stays identical: nothing anywhere needs updating. Choose the uploaded file’s name, or a different format, and EvoMedia rewrites every reference for you. Be aware that if other websites link straight to the old file, those links will break – that is unavoidable once the filename changes.
-
Can I go back to the original file?
-
Yes. Tick “Backup originals before converting” and the original is archived before each conversion. Restore it from the Backup Status column, per image or in bulk.
-
Which output formats can I choose?
-
Whichever your server’s image driver can actually encode – commonly WebP, AVIF and JPEG, and JPEG XL on the rare host whose Imagick was built with it. Only formats your server can write are listed: nothing is shown that you cannot select and use immediately, and nothing your server supports is held back. The System Info page reports exactly what your image driver can do.
-
If I turn off an image size, does it delete the copies I already have?
-
No. Turning a size off only stops WordPress generating it for new uploads and regenerations – the files already on disk are left exactly as they are. (Reclaiming that disk space by deleting a size’s existing files is a job for the Pro add-on.)
-
Is it safe to turn off the thumbnail, medium or large sizes?
-
Those are WordPress core sizes, flagged with a warning, because themes and the responsive-image system often rely on them. WordPress falls back to a nearby size if one is missing, but layouts can shift – so turn off a core size only if you know your theme doesn’t use it. The extra HiDPI copies (1536×1536, 2048×2048) are usually the safest to drop.
-
What does “Regenerate all images” do?
-
It rebuilds every image’s sub-sizes to match your current settings – (re)creating the sizes you have on and dropping the ones you turned off. It never deletes files and only touches the sub-sizes, never your originals.
-
Can EvoMedia shrink images that are too big when I upload them?
-
Yes. Turn on “Resize on upload” in the upload panel to cap every incoming image at 2560px and drop the oversized full-size original WordPress would otherwise keep beside it. It is off by default, so nothing changes until you switch it on. (The Pro add-on lets you set your own maximum dimensions, and resize images already in your library.)
-
How do I find images that nothing uses?
-
Build the index from EvoMedia Media Usage. Every image then carries a “Used in” count in the Control Center that opens to show the exact posts, custom fields and site settings referring to it, and which size each one uses. A count of 0 means nothing on your site points at it. An image that has not been scanned yet shows “?” and never “0”, so you are never told an image is unused just because it has not been looked at. (Deleting unused images in bulk is a feature of the Pro add-on; the free build shows you what is safe to remove.)
-
Is it safe to delete duplicate or orphaned files?
-
The free build only lists them. Duplicates are compared byte for byte, not guessed from their size, so nothing is called a duplicate until the contents match; entries that merely share one file on disk are listed apart. Orphaned files are looked for only in the year and month folders WordPress itself creates, and any file your content still references by name is flagged as still in use. Removing them is the Pro add-on’s job, and it re-scans and re-checks each file at the moment of deletion, so nothing in use is ever taken off disk.
-
Why does it convert the file instead of serving a WebP copy?
-
Because a parallel copy has to be delivered by something: an
.htaccessrule, a<picture>tag rewrite, or a CDN. That layer can fail silently, breaks when you move host, and leaves orphaned files behind if you ever remove it. EvoMedia converts the file itself and repoints every reference at it. What is on disk is what is served, by WordPress, with no help from anything. -
What happens to my images if I deactivate the plugin?
-
Nothing. Converted files stay where they are and keep being served. EvoMedia does not proxy or rewrite anything at page-render time.
-
Because your files live in a remote bucket, and rewriting them locally would leave your site pointing at stale objects. EvoMedia detects the offload plugin and steps aside. If you know what you are doing, the
evomedia_allow_with_offloadfilter overrides this. -
Are there any limits, caps or trials?
-
None. No image quota, no counter, no expiry, no licence key, and no feature switched off waiting to be unlocked. Everything in this plugin works from the moment you activate it.
-
Does it send my images anywhere?
-
No. Conversion runs on your own server through Imagick or GD. The plugin makes no network requests of any kind.
Reseñas
No hay reseñas para este plugin.
Colaboradores & Desarrolladores
“EvoMedia – Link-Safe Media Replace, Convert & Cleanup” es software de código abierto. Las siguientes personas han contribuido a este plugin.
ColaboradoresTraduce “EvoMedia – Link-Safe Media Replace, Convert & Cleanup” a tu idioma.
¿Interesado en el desarrollo?
Revisa el código, echa un vistazo al repositorio SVN, o suscríbete al registro de desarrollo por RSS .
Historial de cambios
1.3.0
- Fixed: regenerating sub-sizes lost the link to WordPress’s full-size original. The file stayed on disk with nothing pointing at it – invisible in the admin, taking up space, and holding a filename that later renames then had to work around. This affected “Regenerate all images” and restoring from a backup, so a library that has been regenerated since 1.2.0 may have originals stranded this way; they are safe to leave, but they are only reachable over FTP. New regenerations no longer do this.
- Fixed: regenerating sub-sizes for an image WordPress had scaled on upload created a second full set under different filenames and abandoned the first, leaving six unused files per image. Regeneration now keeps the filenames it found, so the existing copies are replaced rather than duplicated – and pages that embedded the old URLs keep working.
- New: Media Usage. Build an index of where every image is used, then see a per-image count in the Control Center that opens to list the exact pages, posts, custom fields and site settings referring to it – and which size each one uses. The column is sortable, so unused images group together.
- New: the Image Sub-sizes panel now shows, for every size, how many times it is actually used and how much disk it occupies – so you can tell an unused 4 MB size from one your theme depends on before switching it off.
- New: a broken references report, listing pages that ask for image files your library no longer has.
- New: an image that has never been scanned shows “?” rather than “0”. Nothing here will ever tell you an image is unused because it has not been looked at yet.
- New: replacing an image larger than WordPress’s 2560px limit now offers to resize it, keeping the filename so your links stay valid. Replace deliberately never resizes on its own, which until now left oversized replacements at full size.
- New: Resize on upload. Cap every incoming image at 2560px and drop the oversized original it would otherwise keep beside it, from the upload panel – off by default, so nothing changes until you ask for it.
- New: the Replace dialog says when the file you picked has a name another attachment already owns, and what your replacement will be called instead.
- New: Recent Reference Changes. When a replace changes a file’s name it rewrites the references to it across your posts, custom fields and site settings – that history is now listed, so you always know what changed.
- New: Duplicate Images. Finds pictures your library holds more than once, comparing files byte for byte rather than guessing from their size, and shows how much disk the extra copies take. Library entries that share a single file on disk are listed separately, because deleting one of those destroys the file the others use.
- New: Orphaned Files. Lists files sitting in your monthly upload folders that no Media Library item claims. Only the year and month folders WordPress creates are examined, so caches, page-builder folders and backups are never touched – and any orphan your content still asks for by name is flagged as still in use rather than offered for removal.
- Fixed: undoing a rename or replace could restore only part of it. Where one operation had rewritten the same page more than once – the main filename and then each sub-size – the page was put back to an intermediate state and the result was still reported as a success.
1.2.0
- New: Image Sub-sizes – choose which of WordPress’s resized copies get generated for every upload, see a live count of how many images in your library have each size, and regenerate the whole library to match in one click. WordPress core sizes are flagged.
- New: WordPress’s own Media Settings screen now greys out the sizes you have switched off in EvoMedia, with a link back to the panel that manages them.
- New: a “Check for updates” button on the System Info page, with each version row showing whether it is up to date.
- Fixed: after a same-name Replace, on-demand crops created by page builders (WPBakery, Elementor, Avada) kept the old image while the builder’s cache kept serving it, so the new picture never appeared. These leftover crops are now cleared – and any crop that is another attachment’s own file is left untouched.
1.1.0
- First public release.
- Replace media: swap the file behind an existing attachment, keeping its ID and URL, with an optional backup of the current file, an editable title, and a date option.
- Control Center: sortable columns, search, per-format colour badges, and an image preview lightbox.
- Upload settings moved into a slide-out panel, reachable straight from the WordPress uploader.
- New System Info page, with a one-click report to paste into a support ticket.
- Compatibility: WPML and Polylang sibling sync; page-builder-safe metadata writes; cloud offload plugins detected, with media actions disabled rather than corrupting your bucket.
- Fixed: replacing an image larger than 2560px left the site’s references pointing at WordPress’s full-size original instead of the served file.
- Fixed: admin thumbnails kept showing the previous image after a replace, until a hard refresh.
- Fixed: two elements of the Replace dialog were displayed even when they should have been hidden.
