Workflow6 min read·Updated

Agency Workflow: Bulk WebP Before Every Launch

Launches slip because images are 'fine in Figma'. Add a fixed step: convert every raster in the build to WebP, show the savings number, and only then deploy. Clients understand megabytes; they do not understand Lighthouse jargon.

Make it a checklist item

Same as 'favicon' and 'GA'. The converter's batch total ('you save 12 MB') is the screenshot you put in the launch Slack.

Why it matters

  • PageSpeed at launch is a reputation issue.
  • Freelancers should not install CLI tools on client laptops.
  • Privacy: client product shots never hit a random compressor.

How to do it

  1. Dump /public, Webflow assets, or WP uploads into two folders: photos / UI.
  2. Photos 80% / 1920. UI 90% / 1600.
  3. Show the first image + savings. Client pays $9 once if they want the ZIP on their machine, or you already have PRO.
  4. Replace, deploy, re-run Lighthouse on 3 templates.

Settings that work

Record the settings in the project README so the next sprint matches.

Convert a batch in your browser. Nothing is uploaded.
Open the converter

Put it into practice

Convert your images to WebP right now, free and privately in your browser.

Open the converter

Frequently asked questions

The $9 lifetime licence is cheaper than an hour of your time. Buy it on the agency machine.

Video is out of scope. Poster frames should still be WebP.

Keep reading

Workflow6 min read

Client images, private

Client work, unpublished products and faces should not go to a random online compressor. Convert to WebP locally in the browser.

Read more
Tutorial5 min read

Bulk convert to WebP

The fastest way to batch convert hundreds of PNG and JPG images to WebP: drag, drop, set quality once, download a ZIP. Private, browser-based, no command line.

Read more
Performance6 min read

PageSpeed image audits

Clear 'next-gen formats', 'properly size images' and 'efficiently encode' by converting a batch to WebP at the right width.

Read more