Images added to the WordPress Media Library can differ significantly in dimensions, format, metadata and compression. Without a consistent process, an Elementor website may contain oversized uploads, unnecessary image information or several versions that are difficult to manage. Elementor Image Optimization brings these choices into one settings area, covering compression, resizing, EXIF metadata, WebP conversion, generated image sizes and original-image backups.
The documented defaults provide a useful starting point, but they are not a universal configuration for every website. A portfolio, WooCommerce store, agency website and content-heavy site may use different image types and have different quality requirements. The safest approach is to configure the settings, test representative files and review the result on the actual website before applying broad changes.
What Elementor Image Optimization controls
Finding the settings
To begin, open the WordPress administration area and go to Elementor > Image Optimization > Settings. This is the central location for reviewing how uploaded images will be processed. The available controls address several separate stages of image handling rather than one single compression switch.
Depending on the selected options, you can review compression, automatic optimization of new uploads, maximum image dimensions, EXIF removal, original-image backups, format conversion and the image sizes processed. Treat each option as an independent decision. Enabling compression does not automatically determine whether an image should be resized, converted to WebP or retained in its original form.
Separate settings from outcomes
Elementor documents defaults for several controls, but those defaults should be considered a starting point. The appropriate result depends on the image content, the display sizes used by templates, the need for editing or downloads, and the way the site delivers media.
Caching, a CDN and other image-related plugins can also affect how files are delivered. The settings therefore should be evaluated by checking real images and real pages, not by assuming that one configuration will produce the same result everywhere. The goal is a controlled balance between file size, visual quality, recovery options and compatibility.
Lossy vs. Lossless compression
When to start with Lossless
Elementor describes Lossless compression as preserving the original image quality while producing a smaller reduction in file size. This makes it the cautious starting point when visible changes are unacceptable or when an image contains details that must remain precise.
Lossless compression can be appropriate for logos, screenshots, diagrams, illustrations and graphics containing fine text. It does not mean that every resulting file will be small, and it should not be presented as a universal performance solution. Its main advantage is that it avoids discarding image data, while its trade-off is generally a more limited reduction in size.
Before processing a large collection, select representative images and compare them at the sizes used on the website. Inspect edges, small lettering, transparent areas and high-contrast details. If preserving the original visual appearance is the primary requirement, Lossless offers a more conservative basis for testing.
When to evaluate Lossy
Lossy compression aims for a larger reduction in file size by lowering image quality. This can be useful for photographs, where some changes may be difficult to notice at normal display sizes. However, a smaller file is not automatically a better file. The result must be inspected for visible artifacts.
Artifacts can be more noticeable around sharp edges, line art, logos, screenshots and text-heavy graphics. They may also matter in photographs containing faces or other important visual details. Compare optimized images with the originals and view them in the context of the Elementor template, rather than judging only the file in isolation.
The choice between Lossy and Lossless is therefore a quality-versus-size decision. Start with the method that matches the content and brand requirements, then test the actual output. Elementor’s documentation does not establish one compression level that is optimal for every image or website.
Recommended starting configuration for new uploads
Automate future uploads
Review Optimize new uploads before adding new media. When enabled, Elementor automatically optimizes images uploaded to the WordPress Media Library. The documentation states that this setting is active by default, which can help create a consistent process for future uploads.
Automatic processing reduces the need to remember a separate optimization step each time an editor, designer or store manager adds an image. It should still be monitored during the initial rollout. Upload several representative files, check their appearance and verify that the resulting images are available as expected in the relevant Elementor templates.
Automation is especially useful when several people manage a website, but it does not remove the need for quality control. Before bulk optimization or other large-scale changes, create a full website backup and keep original-image backups enabled while the configuration is being evaluated.
Control dimensions and metadata
Resize larger images can reduce images that exceed the configured maximum dimensions. Elementor documents a default maximum height and width of 1920 pixels when this setting is active. That value is a product setting, not a universal WordPress, SEO or performance requirement.
Review whether the configured dimensions fit the website’s design and media workflow. Some images may need larger source dimensions for a particular presentation, while others may be unnecessarily large for their intended use. Do not change the value solely because a number is documented as the default; test it against actual templates and media needs.
Clear EXIF metadata is a separate control. Elementor states that clearing EXIF metadata removes some additional image information that can increase file size, and the setting is active by default. Also review which generated image sizes should be optimized. The useful choice depends on the sizes that the website’s templates actually use.
WebP conversion: when it makes sense
What Elementor converts
Elementor documents that enabling WebP conversion turns optimized JPEG images into WebP format. WebP supports both Lossy and Lossless compression and has broad support in current major browsers, making it a practical format to evaluate for a modern WordPress website.
That does not mean every image workflow should automatically convert every available file. WebP conversion is not a guarantee of a fixed performance improvement, and the outcome depends on the source image, the selected compression method and the way the file is delivered. Keep the original JPEG or PNG available when it is needed for editing, downloads, integrations or compatibility requirements.
When deciding whether WordPress images should be converted to WebP, consider the role of the image as well as its format. Test important media, including product images, logos, screenshots and graphics used in prominent Elementor sections.
Fallback and delivery checks
Compatibility depends on the actual delivery configuration. Check how WebP files are served through the site’s caching layer, CDN and other image-delivery or image-related plugins. Where browser or workflow requirements call for it, retain JPEG or PNG fallbacks.
Avoid running multiple image optimization systems on the same files without reviewing their settings. Repeated conversion or compression can make it harder to identify which tool changed an image, complicate restoration and affect quality control. Test the front end in the environments relevant to the website rather than assuming that a conversion option alone defines the complete delivery process.
Why keep original-image backups
Recovery and re-optimization
Backup Original Images stores a copy of the original image so it can be used instead of the compressed version when needed. This creates a recovery path if an optimized file has visible artifacts, if a different compression choice should be tested or if the owner later wants to re-optimize the image.
Keeping originals is particularly useful during initial configuration and bulk optimization. It allows quality decisions to be revisited without relying only on the already processed file. Elementor’s documentation also states that restoring original images or permanently removing backups may be irreversible, so create a full website backup before either action.
Do not disable original-image backups simply because the first previews look acceptable. First confirm that separate, restorable website backups exist and that the site owner understands how recovery will work.
Storage trade-offs
Original copies consume server storage. Elementor states that they do not affect front-end performance, but their storage cost still matters for website operations. The retention decision should reflect available storage, the site’s editing workflow and the availability of an independent full-site backup.
There is no single retention period established by the provided documentation. Keep the copies while testing and during the rollout, then assess whether removing them is justified. Permanently remove backups only after confirming recovery options and creating a current website backup.
A safe testing and rollout workflow
Before applying changes
Start by creating a full website backup. Keep Backup Original Images enabled during initial testing, and avoid making irreversible changes until the backup has been confirmed as restorable. Prepare a representative sample rather than testing only one type of image.
- Include photographs, including images with faces.
- Include logos, screenshots, diagrams and graphics containing fine text.
- Include illustrations and transparent graphics where relevant to the website.
- Review the intended display sizes in Elementor templates.
- Check which generated image sizes are actually used.
Then review automatic uploads, resizing, EXIF handling, compression, WebP conversion and original backups as separate controls. Do not assume that enabling every option is appropriate without checking the site’s workflow and delivery requirements.
After applying changes
Preview the optimized files and inspect the front end. Check important Elementor templates, responsive image sizes and the way media is delivered through caching, CDN and other image-related tools. Look for compression artifacts around text, sharp edges and high-contrast areas, and compare WebP output with any required fallback formats.
Record actual quality and file-size results for the tested images instead of promising a fixed bandwidth saving, Core Web Vitals result or conversion improvement. If an image is unsuitable, use the original backup as the recovery source, provided a website backup exists before restoration.
Keep original backups during the initial rollout. Only consider permanent removal after independent recovery has been confirmed and the storage trade-off has been reviewed. If another optimization system is active, inspect the interaction before processing the same files again.
Elementor Image Optimization is easiest to manage when settings are treated as a workflow rather than a one-click solution. Review Optimize new uploads, Resize larger images, EXIF handling and the generated sizes used by the site. Choose Lossless when preserving visual fidelity is critical, and evaluate Lossy for suitable photographs after visual inspection. WebP is a practical format to test, but confirm fallback and delivery behavior on the actual website. Finally, keep original-image backups until independent recovery is confirmed. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.