Upload one image or a full batch. Convert between JPG, PNG, WebP, AVIF, BMP, GIF, and ICO favicons. WebP and AVIF conversion can cut image sizes by 25 to 70 percent, which improves your Google PageSpeed score, your Core Web Vitals, and your search rankings. Everything runs in your browser. Nothing uploads, nothing stores, nothing tracks.
AVIF output requires a recent browser. Update Chrome or Safari to enable it.
×
Leave blank to keep original size
Why image optimization matters for SEO, AEO, GEO, and AIO
Image weight is one of the largest contributors to slow page loads, and slow pages get pushed down in search results, lose featured snippets, and reduce the chance of being cited by AI tools. Converting your images to modern formats like WebP and resizing them to actual display dimensions is the single highest-leverage thing you can do for technical SEO. Here is how it connects to each layer of modern search.
SEO
Search Engine Optimization
Google uses Core Web Vitals as a confirmed ranking signal. Largest Contentful Paint, the metric that measures when the main content appears, is dominated by image load time on most pages. Compressing images cuts LCP directly and pushes you up the rankings.
AEO
Answer Engine Optimization
Featured snippets and AI Overviews tend to pull from pages that load fast and answer questions clearly. A page that takes four seconds to render gets skipped over for one that loads in one second. Optimized images keep you in the running.
GEO
Generative Engine Optimization
ChatGPT, Gemini, Perplexity, and Claude cite sources that load reliably and have clean structure. Slow image-heavy pages time out during crawl or get deprioritized in citation pools. Lighter pages get cited more.
AIO
AI-Integrated Operations
Modern marketing stacks pull images into ad networks, CRMs, email platforms, and AI workflows. Files in the right format and the right size move through every system without friction. Heavy or oddly-formatted files break workflows.
When to use which image format
Picking the right format matters more than people realize. The same photo saved as a PNG can be ten times larger than the same photo saved as a properly compressed WebP. Use this as a quick reference.
WebP
Websites, blog posts, product photos, hero images
Smallest file size at a given quality on most browsers. 25 to 50 percent smaller than JPG. Universal browser support since 2020.
AVIF
Modern websites where every kilobyte matters
Next generation format. 20 to 30 percent smaller than WebP at equal quality. Supported in recent Chrome, Edge, Firefox, and Safari 16.4+. Browser will tell you if your version cannot encode it.
JPG
Photographs when WebP is not an option
Reliable, universal, smaller than PNG for photos. Use quality 80 to 90 for the best size-to-quality balance.
PNG
Logos, icons, graphics with transparency, screenshots with text
Lossless. Preserves every pixel and supports transparent backgrounds. Larger files than WebP or JPG, so reserve it for graphics that need pixel accuracy.
ICO
Favicons for websites and Windows apps
Bundles multiple small sizes (16, 32, 48 px) in one file. Drop a square logo, get a favicon ready to upload. Works in every browser tab and bookmark bar.
GIF
Simple animated graphics under 256 colors
Limited color palette. For photos, JPG or WebP look better at smaller file sizes. Modern alternatives like animated WebP or video are usually better choices.
BMP
Almost never on the web
Uncompressed. Files are massive compared to any other format. Useful only for specific software workflows that require it.
How to convert images for the web
01
Drop or paste your images
Drag any number of files into the upload zone, click to pick from your computer, or paste a screenshot directly with Cmd or Ctrl plus V. Everything stays on your device.
02
Pick the right output format
WebP is the right answer for almost every web use case. JPG works as a fallback if you need maximum compatibility. PNG is for graphics that need transparency or pixel-perfect text.
03
Choose your quality setting
85 to 90 is the sweet spot for web photos. Visually identical to the original for most images, with file sizes 50 to 70 percent smaller than the source.
04
Resize if needed
If your image will display at 800 pixels wide on the page, do not upload a 4000 pixel wide source. Type the target width in the resize field and the height adjusts automatically to keep proportions correct.
05
Convert and download
Click convert and watch the file size savings appear next to each image. Download files individually or grab the whole batch as a single zip.
WebP vs. AVIF vs. JPG vs. PNG: complete format comparison
Five image formats account for over 99 percent of images on the modern web. Each one has specific strengths, specific weaknesses, and a specific use case where it is genuinely the right answer. Picking the wrong format is one of the most common reasons web pages are slower than they need to be.
AVIF2019, mainstream 2022+
Best for: The smallest file sizes on the modern web. 20 to 30 percent smaller than WebP at equal quality. Use when maximum speed matters and you can serve fallback formats for older browsers.
Weakness: Slower to encode than WebP. No support in browsers older than 2022. Limited tooling support in older design software.
WebP2010, mainstream 2020+
Best for: The practical default for the modern web in 2026. 25 to 50 percent smaller than JPG at equal quality. Universal browser support. Lossy and lossless modes both supported.
Weakness: Slightly larger than AVIF. Some legacy CMS plugins still default to JPG export. Older email clients may not display WebP.
JPG1992
Best for: Universal compatibility for photos. The right answer when you need an image to render absolutely everywhere with zero risk of incompatibility, including in older email clients, legacy systems, and print workflows.
Weakness: Larger files than WebP or AVIF at the same quality. No transparency support. Visible compression artifacts at low quality settings.
PNG1996
Best for: Lossless compression with full transparency. The right answer for logos, icons, screenshots, line art, and any content that needs pixel-perfect preservation or partial transparency.
Weakness: Much larger files than WebP or JPG for photos. Lossless compression is wasted on photographic content where some quality loss is invisible.
GIF1987
Best for: Short looping animations under a few seconds. Mostly replaced by MP4 video and WebP animation in modern web design but still used for memes and reaction graphics.
Weakness: Limited to 256 colors per frame. Larger files than equivalent WebP animation. Not suitable for photos or detailed graphics.
The defensible 2026 default for new content is WebP at quality 85, with PNG reserved for transparency-required content (logos, UI icons, screenshots) and AVIF as the upgrade target for sites where Core Web Vitals scores justify the extra encoding complexity. JPG remains a reasonable choice when broad compatibility outranks file size, and GIF is mostly retired except for short loops.
How modern image formats affect Core Web Vitals
Google uses Core Web Vitals as direct ranking signals as part of the page experience update. Three metrics matter for image-heavy pages. Largest Contentful Paint (LCP) measures how fast the largest above-the-fold element renders, target under 2.5 seconds. Cumulative Layout Shift (CLS) measures how much content jumps around as the page loads, target under 0.1. Interaction to Next Paint (INP) measures responsiveness to user input, target under 200 milliseconds.
Image format choice and image optimization habits affect all three. Here is the specific impact each one has.
LCP — Largest Contentful Paint
Target: Under 2.5 seconds
On most pages the LCP element is a hero image or featured photo. Converting that single image from JPG to WebP cuts download time roughly in half. Adding fetchpriority="high" to the LCP image and preloading it shaves additional milliseconds. Most LCP failures on image-heavy sites are fixable in under an hour with format conversion alone.
CLS — Cumulative Layout Shift
Target: Under 0.1
CLS spikes when images load without explicit width and height attributes, causing surrounding content to jump as the image fills its space. Always set width and height on every img tag, even when using responsive CSS. The browser uses these values to reserve correct space before the image downloads.
INP — Interaction to Next Paint
Target: Under 200 ms
INP is less directly tied to image format but image-heavy pages often have heavy JavaScript that hurts INP. Lazy-loading off-screen images with loading="lazy" reduces upfront work, freeing the main thread to respond faster to user input on the parts of the page that are actually visible.
How to compress images for the web without losing quality
Image compression has a quality range where file size shrinks dramatically while visible quality stays the same. The trick is finding that range for your specific content type. Compression that works perfectly for a textured product photo may produce visible artifacts on a smooth gradient sky. Five rules cover most situations.
01
Quality 85 is the standard sweet spot
For most photos in WebP or JPG format, quality 85 produces files 30 to 50 percent smaller than the original with no visible quality loss at normal viewing distances. This is the right starting point for nearly every web image.
02
Test at the actual display size, not zoomed in
Compression artifacts that are visible at 300 percent zoom usually disappear at the actual display size. Always evaluate quality at the resolution the image will render on the page, not at pixel-peeping zoom levels.
03
Resize before compressing
Resizing a 4000 pixel wide image down to 1600 pixels then compressing produces dramatically smaller files than compressing the 4000 pixel image at low quality. Do dimension reduction first, then format compression second.
04
Different content types compress differently
Photos with texture and noise compress aggressively without visible artifacts. Smooth gradients, sky, skin tones, and flat color regions show artifacts earlier. Logos, screenshots, and line art should stay in PNG to preserve sharp edges, or use higher quality settings (90 to 95) if forced to JPG/WebP.
05
Use modern formats over aggressive compression
Converting a quality 85 JPG to a quality 80 WebP often produces a smaller file with better visible quality than dropping the JPG to quality 60. The newer codec is doing the work, not aggressive compression that produces artifacts.
How to create a favicon: complete 2026 guide
A favicon is the small icon that appears in browser tabs, bookmark bars, mobile home screens, and search results. Modern websites need more than a single favicon.ico file. Different devices and contexts require different formats and sizes.
favicon.ico
Purpose: Legacy fallback for older browsers and Windows. Contains 16x16, 32x32, and 48x48 pixel versions in a single file.
Where: Site root: yourdomain.com/favicon.ico
favicon-32x32.png
Purpose: Standard browser tab icon for most modern desktop browsers.
Where: Linked from HTML head with rel="icon" type="image/png" sizes="32x32"
favicon-16x16.png
Purpose: Smaller tab icon for crowded tab bars and mobile browsers.
Where: Linked from HTML head with rel="icon" type="image/png" sizes="16x16"
apple-touch-icon.png (180x180)
Purpose: Icon used when iPhone or iPad users save your site to their home screen.
Where: Linked from HTML head with rel="apple-touch-icon"
android-chrome-192x192.png and 512x512.png
Purpose: Icons used when Android users save your site as a Progressive Web App.
Where: Referenced in your site.webmanifest file
site.webmanifest
Purpose: JSON file listing icon sizes and theme colors for PWA installation prompts.
Where: Site root: yourdomain.com/site.webmanifest
Image SEO best practices: filenames, alt text, sizing, and lazy loading
Format conversion is one half of image SEO. The other half is how the image is referenced in your HTML and surrounding content. Six rules cover the high-impact image SEO improvements that most sites are missing. If you would rather have all of this audited and fixed across an entire site, our SEO, AEO, and GEO agency service handles image optimization as part of a complete technical SEO implementation.
Use descriptive filenames
DSC_4892.jpg tells Google nothing. red-roof-replacement-indianapolis-2025.jpg gives Google a clear signal about what the image shows. Rename images before uploading to your CMS. The filename appears in image search results.
Write real alt text
Alt text describes what the image actually shows for screen readers and for Google when the image fails to load. Three sentences max. Avoid keyword stuffing. "Storm-damaged roof on a colonial home in Carmel, Indiana with missing shingles and exposed underlayment" is good. "Roofing services Indianapolis" is bad.
Set explicit width and height
Every img tag needs width and height attributes that match the actual image dimensions. This prevents Cumulative Layout Shift as the image loads and is required for Core Web Vitals scores. Most CMS plugins set this automatically. Custom HTML often misses it.
Lazy-load below-the-fold images
Add loading="lazy" to every img tag below the fold. The browser defers downloading these images until they are about to scroll into view, reducing initial page weight and improving LCP. Never lazy-load the LCP image itself.
Use a picture element for format fallbacks
The picture element lets you serve AVIF to modern browsers, WebP to slightly older ones, and JPG as a final fallback, all from a single tag. The browser picks the most efficient format it supports automatically.
Compress before uploading
Many CMS systems run their own image processing on upload, but the source image quality matters. Uploading a 25 MB camera JPEG and letting WordPress resize it produces a worse final result than uploading a pre-resized, pre-compressed 200 KB version.
Free vs. paid image converters: what's actually different
The actual conversion math is the same in every tool. JPEG, WebP, AVIF, and PNG encoding are public standards. The difference between free and paid tools is in features around the conversion, not the conversion itself. Here is what each category actually offers.
This converterFree, unlimited
Best for: Browser-based with no upload, batch conversion, ICO favicon generation, paste from clipboard, real-time file size savings display, all standard formats supported. The right choice for everyone who does not need server-side automation.
Squoosh (by Google)Free, unlimited
Best for: Excellent visual quality preview with side-by-side comparison. Supports advanced encoder settings for AVIF and MozJPEG. Single-image only, no batch mode, no favicon generation.
Photoshop / Affinity Photo$23-$60/month or one-time
Best for: Comprehensive image editing alongside format conversion. Worth it if you need editing capabilities. Overkill if you only need format conversion.
ImageOptim / TinyPNG (paid tiers)$0-$25/month
Best for: API access for automated workflow integration with build pipelines, CMS plugins, and design systems. Useful for engineering teams. Not needed for occasional manual conversion.
Best for: Server-side automatic format conversion based on the requesting browser. Useful for large sites with thousands of images and dynamic image needs. Replaces manual conversion entirely at scale.
Common image optimization mistakes that hurt SEO
Uploading camera-original photos
A 25 MB JPEG straight from a DSLR or iPhone is between 50 and 200 times larger than it needs to be for web display. Always resize and compress before uploading, even when your CMS has its own image processing.
Skipping width and height attributes
img tags without width and height attributes cause Cumulative Layout Shift, which hurts Core Web Vitals scores and ranking. Always set explicit dimensions on every image, even when using responsive CSS that scales them.
Stretching images beyond their resolution
Displaying a 600 pixel wide image at 1200 pixels wide produces a blurry result that signals low quality to users. Always source images at the maximum size they will display, multiplied by 2 for retina sharpness.
Using PNG for photographs
PNG is for transparency and pixel-perfect graphics. Saving photos as PNG produces files 4 to 10 times larger than the equivalent WebP or JPG with no visible quality benefit. Use the right format for the content type.
Lazy-loading the LCP image
Lazy-loading is for below-the-fold images. The Largest Contentful Paint image (usually the hero image) should never be lazy-loaded. Doing so delays LCP measurement and hurts the score it is supposed to help.
Forgetting alt text
Missing alt text fails accessibility standards (WCAG 2.1) and removes a strong relevance signal Google uses for image search. Alt text should describe what the image shows for someone who cannot see it. Decorative images can use alt="" intentionally.
Letting CMS plugins double-process images
WordPress, Wix, Squarespace, and Framer all run their own image processing. Pre-processed images sometimes get re-processed and degraded. Test what your CMS actually serves to users using browser dev tools, not what you uploaded.
Optimizing only hero images
Most pages have 10 to 50 images and only the hero gets optimized. Below-the-fold images, footer logos, social proof avatars, blog post thumbnails, and gallery images often add up to more weight than the hero alone. Audit every image on the page.
Frequently asked questions
Your images never leave your device
Every conversion happens locally inside your browser using the Canvas API. No uploads, no server processing, no tracking pixels, no cookies. Safe for confidential client photos, legal evidence, medical images, and proprietary product shots. Most online image converters cannot say the same.
Want better SEO, AEO, and page speed across your full site?
Image optimization is one piece of the picture. We help businesses rank higher in Google, get cited by ChatGPT and Gemini, and turn more visitors into paying customers. From technical SEO and schema markup to full microsite networks across hundreds of cities, we run the marketing infrastructure most agencies are not set up to deliver.