-rw parameters inside your posts because Blogger automatically serves WebP delivery. However, this automation ignores your theme template, meaning you must still manually add -rw to layout elements like headers and sidebar widgets. You should still manually compress files to WebP before uploading to protect your personal Google storage quota and control your visual clarity.WebP confusion in Blogger image optimization
If you have been reading my recent guides on Blogger image optimization, you might feel a bit confused.
In one post, I said that Blogger automatically converts everything to WebP.
In another, I urged you to manually compress your files to WebP before uploading.
And in a third, I told you to stop manually adding -rw parameters into your posts.
At first glance, this sounds like a complete contradiction.
Why waste time manually converting or coding files if the Blogger platform does it for you?
Today, let's clear up the confusion.
These tips don't contradict each other.
They actually cover three completely different stages of your blogging workflow.
Here is the ultimate breakdown of how they fit together perfectly.
The master breakdown: what to automate vs. what to do manually
1. Physical image files (on your computer)
- What Blogger does automatically: Compresses your file upon delivery to the reader.
- What you still need to do manually: Save and compress your images as WebP before uploading them to the editor.
- Why it matters: This protects your personal Google Storage quota from filling up and guarantees crisp, professional image quality.
Related guide: Blogger image storage limit explained: unlimited uploads, compression & Google Photos
2. Post HTML (inside your articles)
- What Blogger does automatically: Injects the
-rwcode into the live page source on the spot. - What you still need to do manually: Stop typing manual
-rwcode strings into your post HTML editor. - Why it matters: Letting Blogger handle this prevents messy layout conflicts, weird stretching, and broken media scaling on modern responsive themes.
👉 Related tip: Since custom templates disconnect your site from Blogger’s automated image systems, you need a different strategy depending on your template layout. Read my complete guide on how to optimize Blogger images based on theme type: default vs. custom layouts to safely configure your template.
3. Theme layout (logos, sidebars, and widgets)
- What Blogger does automatically: Nothing. Blogger's automated post helper completely ignores this area of your site.
- What you still need to do manually: You must manually add the
-rwparameter to these specific layout URLs. - Why it matters: This is the only way to force Google's servers to compress your background template assets and keep your overall blog template loading instantly.
👉 Read: How to fix Blogger blurry images without slowing down your site
Phase 1: File storage vs. image delivery (why upload WebP?)
The confusion: "If Blogger automatically delivers WebP to my readers, why should I bother saving it as WebP on my computer first?"
The truth: Blogger's automatic conversion only optimizes delivery speed, but it destroys quality control and completely ignores your personal storage limits.
- The Storage trap: When you upload a massive, unoptimized 4MB PNG, Blogger stores that exact heavy original file in your Google account storage (which is shared with Gmail and Google Drive). Uploading raw files will rapidly deplete your 15GB free limit. Pre-compressing keeps your cloud footprint tiny.
- The blur factor: Blogger’s automated compression algorithm is brutal. It prioritizes small file sizes over aesthetics, which can blur text overlays or pixelate photos. When you compress images to WebP before uploading, you control the quality slider to keep them looking sharp.
👉 Deep Dive: Read the full guide on how to compress images before uploading here.
Phase 2: The HTML code vs. the theme template (why stop using -rw?)
The confusion: "You told me Blogger automatically adds -rw to my post images, but then you said I still need to use it manually?"
The truth: It all depends entirely on where the image lives on your blog.
- Inside blog posts (automate it): Modern Blogger code is smart. When a reader loads an article, Google automatically appends
-rwto your post images to serve responsive sizes. If you try to manually force your own parameters into the post HTML, you jam the system, causing stretched or oddly cropped images on mobile devices. - Inside your theme template (manual only): Blogger's smart code only scans post bodies. It completely ignores your raw theme XML code, sidebar HTML widgets, and custom header logos. For these template areas, your site will load the heavy, original file unless you manually inject the
-rwtrick into the image source links.
👉 Deep Dive: Learn why adding -rw to post images is a trap (and where to use it instead).
Summary: Blogger image optimization webP confusion
To get the absolute fastest loading speeds without breaking your layout or fusing up your Google account storage, adopt this simple three-step routine:
- Convert & compress first: Use a free tool to convert your images to WebP or compressed formats on your computer to save storage and lock in image clarity.
- Just upload normally: Let Blogger handle the HTML code inside your posts automatically. Don't add any manual size or
-rwtext parameters to the code. - Hardcode your theme layout: Manually add
-rwstrictly to your logo, background, and widget image URLs inside your theme layout to keep your template lightweight.
👉 Explore the full series in: The complete Blogger image guide: optimization, compression & rendering