{"id":1440,"date":"2026-08-21T15:13:00","date_gmt":"2026-08-21T19:13:00","guid":{"rendered":"https:\/\/www.xconvert.com\/blog\/?p=1440"},"modified":"2026-07-16T23:42:59","modified_gmt":"2026-07-17T03:42:59","slug":"convert-jpg-to-webp-how-much-smaller","status":"publish","type":"post","link":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller","title":{"rendered":"Convert JPG to WebP (How Much Smaller, and What You Lose)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Google\u2019s pitch for WebP fits in one number: lossy WebP comes out <strong>25\u201334% smaller than a comparable JPEG<\/strong>. That figure is real and measured \u2014 but it was measured under conditions that aren\u2019t quite the ones you\u2019re in when you drag an old vacation JPG into a converter, and the format has a mode toggle that can quietly make your files <em>bigger<\/em> instead. This guide gives you the honest version: where the number comes from, what \u201ccomparable quality\u201d actually means, when converting an existing JPG pays off, when it\u2019s pointless, and where a WebP file still can\u2019t follow a JPG. We verified the figures against Google\u2019s WebP documentation and compression study, the support tables against caniuse and Can I Email, and walked the real converter UI so the steps below match what you\u2019ll click.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Quick answer:<\/strong> Converting a JPG to <strong>lossy WebP<\/strong> typically yields a <strong>25\u201334% smaller file at equivalent measured quality<\/strong> \u2014 Google\u2019s own published figure. Keep the <strong>Lossless?<\/strong> toggle on <strong>No (Recommended)<\/strong> for JPG sources: Google\u2019s FAQ warns that lossless WebP built from a lossy JPEG <strong>typically comes out larger than the original<\/strong>. Expect less than the headline saving if your JPG was already aggressively optimized, and remember a JPG\u2192WebP conversion is a lossy copy of a lossy copy \u2014 quality can hold, but it can never improve. Keep the original JPG for email (classic Outlook for Windows won\u2019t display WebP), strict upload forms, and print.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Jump to a section<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"#numbers\">Where the 25\u201334% figure comes from<\/a><\/li><li><a href=\"#quality\">What \u201ccomparable quality\u201d actually means<\/a><\/li><li><a href=\"#pointless\">When converting is pointless \u2014 or backfires<\/a><\/li><li><a href=\"#where-not\">Where WebP can\u2019t go<\/a><\/li><li><a href=\"#tool\">Convert JPG to WebP on xconvert<\/a><\/li><li><a href=\"#faq\">FAQ<\/a><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"numbers\">Where the 25\u201334% figure comes from<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google\u2019s WebP documentation states it plainly: <strong>\u201cWebP lossy images are 25-34% smaller than comparable JPEG images at equivalent SSIM quality index.\u201d<\/strong> That sentence links to Google\u2019s own <a href=\"https:\/\/developers.google.com\/speed\/webp\/docs\/webp_study\">WebP compression study<\/a>, and the methodology is worth thirty seconds, because it defines what the number does \u2014 and doesn\u2019t \u2014 promise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The study took source images from standard test sets (the Kodak and Tecnick photo collections, plus about 11,000 images crawled from the web), encoded each one to JPEG at quality settings 50, 75, and 95, and measured the result\u2019s <strong>SSIM<\/strong> \u2014 a structural-similarity score that approximates how close the compressed image looks to the source. Then it encoded WebP versions tuned to hit the <em>same<\/em> SSIM score and compared the byte counts. Across those quality levels, the WebP files needed roughly <strong>0.66\u20130.75\u00d7 the bytes of the equivalent JPEG<\/strong> \u2014 in other words, 25\u201334% smaller at the same measured quality.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Applied naively, that means a 2 MB photo re-encoded to WebP at matching quality lands somewhere around <strong>1.3\u20131.5 MB<\/strong>. Two honest caveats before you bank that:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>The study dates to the early libwebp era (libwebp 0.1.2 vs. libjpeg 6b with size optimization on). Encoders on both sides have improved since, so treat the range as a well-sourced ballpark, not a per-file guarantee.<\/li><li>The saving is <strong>content-dependent<\/strong>. Smooth, photographic images compress differently from noisy or highly detailed ones, and the ratio shifts with the quality level you target.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"quality\">What \u201ccomparable quality\u201d actually means<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cEquivalent SSIM quality index\u201d is doing a lot of work in Google\u2019s sentence. SSIM compares a compressed image against its source and scores how structurally similar it still looks; two files \u201cat equivalent SSIM\u201d sit at the same measured distance from the original. So the claim is: <em>same measured visual quality, 25\u201334% fewer bytes.<\/em> Fair enough.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s the fine print that matters for you: <strong>the study\u2019s sources were clean, lossless PNG masters.<\/strong> Both the JPEG and the WebP were <em>fresh encodes of an uncompressed original<\/em>. When you convert an existing JPG, your situation differs in two ways:<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li><strong>There is no clean master.<\/strong> The JPEG\u2019s compression artifacts \u2014 the slight blockiness, the ringing around edges \u2014 are baked into the pixels the WebP encoder now has to reproduce. Some of your output bytes get spent faithfully encoding another codec\u2019s noise.<\/li><li><strong>You\u2019re adding a second lossy generation.<\/strong> The converter decodes your JPG and re-encodes the pixels with WebP\u2019s lossy mode. Detail the JPEG already threw away is gone forever, and the re-encode discards a little more. At a high quality setting the difference is visually negligible on screen \u2014 but the direction only goes one way. <strong>No conversion can make a JPG look better; the ceiling is \u201clooks the same, weighs less.\u201d<\/strong><\/li><\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The practical consequence: a large, lightly compressed JPG \u2014 a photo straight off a camera or a high-quality editor export \u2014 converts close to the headline range. A small JPG that has already been through an optimizer or a \u201ccompress for web\u201d pass has far less fat left, and the saving shrinks toward zero. If you\u2019re choosing an image format from scratch rather than converting existing files, the trade-offs are laid out in <a href=\"https:\/\/www.xconvert.com\/blog\/png-vs-webp-vs-jpg\/\">PNG vs WebP vs JPG<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"pointless\">When converting is pointless \u2014 or backfires<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three situations where JPG\u2192WebP isn\u2019t the win the headline suggests:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. The JPG is already squeezed hard.<\/strong> Google\u2019s own FAQ answers the question <a href=\"https:\/\/developers.google.com\/speed\/webp\/faq\">\u201cCan a WebP image grow larger than its source image?\u201d<\/a> with <em>yes<\/em> \u2014 it happens in specific conversion setups, and an already-optimized source is the classic setup for a disappointing result. If a JPG has been through a compressor already, WebP may shave only a few percent, or occasionally come out larger. Nothing is broken; the algorithm simply met a file that was already near its floor. Convert, compare sizes, and keep whichever file is smaller.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. The Lossless trap.<\/strong> WebP has two modes, and the <strong>Lossless<\/strong> one is the wrong tool for a JPG. Lossless WebP must reproduce every pixel exactly \u2014 including every JPEG artifact \u2014 and Google\u2019s FAQ is explicit that using lossless WebP to capture a lossy source \u201cwill typically result in a larger file.\u201d Lossless mode earns its keep on clean graphics from PNG-style sources \u2014 logos, icons, screenshots that were never lossy to begin with. Pointed at a photograph that\u2019s already JPEG, it usually <em>grows<\/em> the file while preserving the artifacts you\u2019d happily lose. For JPG sources, lossy WebP is the correct mode.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. The image hasn\u2019t reached its final form.<\/strong> Every lossy re-encode stacks another generation of loss. If you\u2019re still editing the picture, keep editing the original and convert only the final delivery copy. And if the destination re-compresses uploads on its own servers anyway \u2014 as most social platforms do \u2014 converting first just inserts an extra lossy generation before theirs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The through-line: <strong>WebP is for the copy you serve, not the copy you keep.<\/strong> Convert duplicates; archive the original JPG.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"where-not\">Where WebP can\u2019t go<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the browser, WebP is a solved problem: <a href=\"https:\/\/caniuse.com\/webp\">caniuse<\/a> puts global support at <strong>about 96%<\/strong> \u2014 Chrome since version 32, Firefox since 65, Edge since 18, and Safari fully since 16 (iOS Safari since 14). The holdouts are Internet Explorer (never supported it) and pre-2020 Safari. For images on your own website, WebP is safe.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Off the web, the JPG habit still earns its keep:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Destination<\/th><th>WebP a good idea?<\/th><\/tr><\/thead><tbody><tr><td>Your own website \/ web app<\/td><td><strong>Yes<\/strong> \u2014 ~96% global browser support (caniuse)<\/td><\/tr><tr><td>Email attachments<\/td><td><strong>Risky<\/strong> \u2014 classic Outlook for Windows doesn\u2019t render WebP in any version Can I Email has tested, and Gmail converts attached WebP files to JPG<\/td><\/tr><tr><td>Government \/ ID \/ job-application upload forms<\/td><td><strong>Check first<\/strong> \u2014 many accept only <code>.jpg<\/code>\/<code>.png<\/code>; it varies by site, so read the form\u2019s accepted-formats line<\/td><\/tr><tr><td>Print services<\/td><td><strong>No<\/strong> \u2014 lossy WebP is limited to 8-bit Y\u2019CbCr 4:2:0 color (per Google\u2019s FAQ), with no CMYK; print vendors expect JPEG, TIFF, or PDF<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The email row deserves emphasis because it surprises people: per <a href=\"https:\/\/www.caniemail.com\/features\/image-webp\/\">Can I Email\u2019s support table<\/a>, the classic Outlook desktop client on Windows simply doesn\u2019t display WebP images, and Gmail\u2019s partial support includes converting the file to JPG on its side. If the picture\u2019s destination is an inbox, attach the JPG.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">None of this argues against converting \u2014 it argues for converting <em>copies<\/em>. Serve WebP where it works; keep the original JPG for everywhere it doesn\u2019t.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"tool\">Convert JPG to WebP on xconvert<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/www.xconvert.com\/convert-jpg-to-webp\">xconvert JPG to WebP converter<\/a> exposes exactly the two decisions this article is about \u2014 the lossy quality level and the lossless toggle:<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Open <a href=\"https:\/\/www.xconvert.com\/convert-jpg-to-webp\">xconvert.com\/convert-jpg-to-webp<\/a> and click <strong>+ Add Files<\/strong> to upload your image \u2014 from your computer, Google Drive, or Dropbox. The page accepts JPG, JPEG, and JFIF files.<\/li><li>Open <strong>Advanced Options<\/strong> (the gear icon) to reveal the controls.<\/li><li>Leave <strong>Lossless?<\/strong> on <strong>No (Recommended)<\/strong>. For a JPG source this is the setting that matters most: lossy is the correct mode, and switching to <strong>Yes<\/strong> typically produces a file <em>larger<\/em> than your original (see <a href=\"#pointless\">the Lossless trap<\/a> above).<\/li><li>Pick a <strong>Quality Preset<\/strong> \u2014 the default, <strong>Very High (Recommended)<\/strong>, targets the \u201csame look, fewer bytes\u201d trade this article describes. If you need to hit an exact budget instead, use the <strong>Specific file size<\/strong> option.<\/li><li>Optionally shrink the pixels too under <strong>Image resolution<\/strong> (a Resolution Percentage, a preset, or exact Width\/Height with aspect ratio kept). If the image is displayed smaller than its pixel dimensions, downscaling saves more than any format change will.<\/li><li>Click <strong>Convert<\/strong>, then download your WebP \u2014 and compare it against the original. If a particular file came out barely smaller (or bigger), that JPG was already at its floor: keep the original.<\/li><\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Your image is uploaded over an encrypted connection, is processed on our servers and deleted automatically a few hours later. Nothing stays around.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the converted WebP is still heavier than you\u2019d like, the quality-and-dimensions levers are covered in <a href=\"https:\/\/www.xconvert.com\/blog\/compress-a-webp-image\/\">how to compress a WebP image<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"faq\">FAQ<\/h2>\n\n\n\n<h5 class=\"wp-block-heading\">How much smaller will my JPG get as a WebP?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Google\u2019s measured figure is <strong>25\u201334% smaller than a comparable JPEG at the same SSIM quality<\/strong>. That\u2019s the expectation for well-compressible sources; a JPG that was already heavily optimized will save less \u2014 sometimes almost nothing. The result is content-dependent, so convert and compare rather than assuming the headline number.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Does converting JPG to WebP lose quality?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Technically yes \u2014 it\u2019s a second round of lossy compression, so a little more detail is discarded on top of what JPEG already removed. At a high quality setting (the converter\u2019s default <strong>Very High<\/strong> preset) the difference is <strong>visually negligible for on-screen use<\/strong>. What conversion can never do is <em>improve<\/em> a JPG: detail the original encode threw away is unrecoverable.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Why did my WebP come out bigger than my JPG?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Two usual causes. Either <strong>Lossless mode was on<\/strong> \u2014 Google\u2019s FAQ notes that lossless-encoding a lossy JPEG source \u201cwill typically result in a larger file\u201d \u2014 or the source JPG was <strong>already compressed near its floor<\/strong>, which Google acknowledges can produce a WebP larger than the source. Set <strong>Lossless?<\/strong> to <strong>No<\/strong>, try a lower <strong>Quality Preset<\/strong> or a <strong>Specific file size<\/strong>, and if it\u2019s still bigger, keep the JPG.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Should I ever use lossless WebP for a JPG?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Almost never. <strong>Lossless WebP is designed for clean sources<\/strong> like PNG graphics, where it beats PNG by about 26% (Google\u2019s figure). Applied to a JPEG, it must reproduce every compression artifact pixel-perfectly, which typically inflates the file while locking in the flaws.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Can I email a WebP image?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s risky. Per Can I Email\u2019s tests, the <strong>classic Outlook desktop client on Windows doesn\u2019t render WebP at all<\/strong>, and <strong>Gmail converts attached WebP files to JPG<\/strong>. For anything destined for an inbox, attach the JPG original instead.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Is WebP better for SEO?<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">Indirectly, via page speed. Lighthouse\u2019s <strong>\u201cServe images in modern formats\u201d<\/strong> audit recommends WebP and AVIF because, in Google\u2019s words, encoding images in these formats means \u201cthey will load faster and consume less cellular data\u201d \u2014 and faster pages help Core Web Vitals. The format itself isn\u2019t a ranking switch; the smaller payload is the benefit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Last verified 2026-07-15.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/developers.google.com\/speed\/webp\">Google \u2014 An image format for the Web (WebP docs)<\/a> \u2014 the verbatim claim: \u201cWebP lossy images are 25-34% smaller than comparable JPEG images at equivalent SSIM quality index.\u201d<\/li><li><a href=\"https:\/\/developers.google.com\/speed\/webp\/docs\/webp_study\">Google \u2014 WebP Compression Study<\/a> \u2014 methodology behind the figure: PNG source sets, JPEG at Q50\/75\/95, SSIM-matched WebP encodes, 0.66\u20130.75 size ratio; encoder versions used.<\/li><li><a href=\"https:\/\/developers.google.com\/speed\/webp\/faq\">Google \u2014 WebP FAQ<\/a> \u2014 WebP can exceed the source size; lossless-encoding a lossy source \u201cwill typically result in a larger file\u201d; lossy WebP is 8-bit Y\u2019CbCr 4:2:0 only.<\/li><li><a href=\"https:\/\/caniuse.com\/webp\">caniuse \u2014 WebP image format<\/a> \u2014 ~96% global browser support; Chrome 32+, Firefox 65+, Edge 18+, Safari 16+\/iOS 14+; IE and old Safari unsupported.<\/li><li><a href=\"https:\/\/www.caniemail.com\/features\/image-webp\/\">Can I Email \u2014 WebP image support<\/a> \u2014 classic Outlook for Windows does not render WebP; Gmail converts WebP attachments to JPG.<\/li><li><a href=\"https:\/\/developer.chrome.com\/docs\/lighthouse\/performance\/uses-webp-images\">Chrome Developers \u2014 Lighthouse: \u201cServe images in modern formats\u201d<\/a> \u2014 the audit recommending WebP\/AVIF for faster loads.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.<\/p>\n","protected":false},"author":4,"featured_media":1439,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,14],"tags":[],"class_list":["post-1440","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to-guides","category-tools"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Convert JPG to WebP (How Much Smaller, and What You Lose)<\/title>\n<meta name=\"description\" content=\"How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Convert JPG to WebP (How Much Smaller, and What You Lose)\" \/>\n<meta property=\"og:description\" content=\"How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller\" \/>\n<meta property=\"og:site_name\" content=\"XConvert Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/xconvertcom\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-21T19:13:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/07\/featured-7.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1260\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Stephanie Taylor\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@xconvert_com\" \/>\n<meta name=\"twitter:site\" content=\"@xconvert_com\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Stephanie Taylor\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller\"},\"author\":{\"name\":\"Stephanie Taylor\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#\\\/schema\\\/person\\\/ae9300506c0e9e85f1a6ece4d762980d\"},\"headline\":\"Convert JPG to WebP (How Much Smaller, and What You Lose)\",\"datePublished\":\"2026-08-21T19:13:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller\"},\"wordCount\":2088,\"image\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/featured-7.png\",\"articleSection\":[\"How To Guides\",\"Tools\"],\"inLanguage\":\"en-CA\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller\",\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller\",\"name\":\"Convert JPG to WebP (How Much Smaller, and What You Lose)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/featured-7.png\",\"datePublished\":\"2026-08-21T19:13:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#\\\/schema\\\/person\\\/ae9300506c0e9e85f1a6ece4d762980d\"},\"description\":\"How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#breadcrumb\"},\"inLanguage\":\"en-CA\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-CA\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#primaryimage\",\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/featured-7.png\",\"contentUrl\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/featured-7.png\",\"width\":2400,\"height\":1260,\"caption\":\"The xconvert JPG to WebP converter at \\\/convert-jpg-to-webp with the + Add Files button highlighted \u2014 upload a JPG and download a smaller WebP copy\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/convert-jpg-to-webp-how-much-smaller#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.xconvert.com\\\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Convert JPG to WebP (How Much Smaller, and What You Lose)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/\",\"name\":\"XConvert Blog\",\"description\":\"Blog for XConvert file converter\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-CA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/#\\\/schema\\\/person\\\/ae9300506c0e9e85f1a6ece4d762980d\",\"name\":\"Stephanie Taylor\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-CA\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/af9a54599087d3f3dd2d0ea950291c9e18fcc503af09b136b37fa52c418fe467?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/af9a54599087d3f3dd2d0ea950291c9e18fcc503af09b136b37fa52c418fe467?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/af9a54599087d3f3dd2d0ea950291c9e18fcc503af09b136b37fa52c418fe467?s=96&d=mm&r=g\",\"caption\":\"Stephanie Taylor\"},\"url\":\"https:\\\/\\\/www.xconvert.com\\\/blog\\\/author\\\/stephanie\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Convert JPG to WebP (How Much Smaller, and What You Lose)","description":"How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller","og_locale":"en_US","og_type":"article","og_title":"Convert JPG to WebP (How Much Smaller, and What You Lose)","og_description":"How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.","og_url":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller","og_site_name":"XConvert Blog","article_publisher":"https:\/\/www.facebook.com\/xconvertcom","article_published_time":"2026-08-21T19:13:00+00:00","og_image":[{"width":2400,"height":1260,"url":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/07\/featured-7.png","type":"image\/png"}],"author":"Stephanie Taylor","twitter_card":"summary_large_image","twitter_creator":"@xconvert_com","twitter_site":"@xconvert_com","twitter_misc":{"Written by":"Stephanie Taylor","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#article","isPartOf":{"@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller"},"author":{"name":"Stephanie Taylor","@id":"https:\/\/www.xconvert.com\/blog\/#\/schema\/person\/ae9300506c0e9e85f1a6ece4d762980d"},"headline":"Convert JPG to WebP (How Much Smaller, and What You Lose)","datePublished":"2026-08-21T19:13:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller"},"wordCount":2088,"image":{"@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#primaryimage"},"thumbnailUrl":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/07\/featured-7.png","articleSection":["How To Guides","Tools"],"inLanguage":"en-CA"},{"@type":"WebPage","@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller","url":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller","name":"Convert JPG to WebP (How Much Smaller, and What You Lose)","isPartOf":{"@id":"https:\/\/www.xconvert.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#primaryimage"},"image":{"@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#primaryimage"},"thumbnailUrl":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/07\/featured-7.png","datePublished":"2026-08-21T19:13:00+00:00","author":{"@id":"https:\/\/www.xconvert.com\/blog\/#\/schema\/person\/ae9300506c0e9e85f1a6ece4d762980d"},"description":"How much smaller is WebP? Google measures 25\u201334% vs comparable JPEG. When to convert JPG to WebP, when it backfires, and the settings that matter.","breadcrumb":{"@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#breadcrumb"},"inLanguage":"en-CA","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller"]}]},{"@type":"ImageObject","inLanguage":"en-CA","@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#primaryimage","url":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/07\/featured-7.png","contentUrl":"https:\/\/www.xconvert.com\/blog\/wp-content\/uploads\/2026\/07\/featured-7.png","width":2400,"height":1260,"caption":"The xconvert JPG to WebP converter at \/convert-jpg-to-webp with the + Add Files button highlighted \u2014 upload a JPG and download a smaller WebP copy"},{"@type":"BreadcrumbList","@id":"https:\/\/www.xconvert.com\/blog\/convert-jpg-to-webp-how-much-smaller#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.xconvert.com\/blog"},{"@type":"ListItem","position":2,"name":"Convert JPG to WebP (How Much Smaller, and What You Lose)"}]},{"@type":"WebSite","@id":"https:\/\/www.xconvert.com\/blog\/#website","url":"https:\/\/www.xconvert.com\/blog\/","name":"XConvert Blog","description":"Blog for XConvert file converter","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.xconvert.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-CA"},{"@type":"Person","@id":"https:\/\/www.xconvert.com\/blog\/#\/schema\/person\/ae9300506c0e9e85f1a6ece4d762980d","name":"Stephanie Taylor","image":{"@type":"ImageObject","inLanguage":"en-CA","@id":"https:\/\/secure.gravatar.com\/avatar\/af9a54599087d3f3dd2d0ea950291c9e18fcc503af09b136b37fa52c418fe467?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/af9a54599087d3f3dd2d0ea950291c9e18fcc503af09b136b37fa52c418fe467?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/af9a54599087d3f3dd2d0ea950291c9e18fcc503af09b136b37fa52c418fe467?s=96&d=mm&r=g","caption":"Stephanie Taylor"},"url":"https:\/\/www.xconvert.com\/blog\/author\/stephanie"}]}},"_links":{"self":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts\/1440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/comments?post=1440"}],"version-history":[{"count":1,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts\/1440\/revisions"}],"predecessor-version":[{"id":1441,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/posts\/1440\/revisions\/1441"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/media\/1439"}],"wp:attachment":[{"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/media?parent=1440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/categories?post=1440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.xconvert.com\/blog\/wp-json\/wp\/v2\/tags?post=1440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}