Your images are too heavy. Fix them all at once.
Skwiz connects to your Framer project and batch-optimizes every image - CMS collections, galleries, pages. Runs locally using Google Squoosh. Nothing leaves your machine.
bandwidth costs and load times. See exactly what ships.
Real numbers from a real project
5 hero images on a typical Framer site. Before and after Skwiz.
Your source images need more than delivery optimization
Framer's CDN handles delivery brilliantly. But the source files you upload? That's on you.
You upload, Framer serves
Framer's CDN handles responsive delivery, but the source file stays exactly as you uploaded it. A 4MB hero image is a 4MB hero image.
CMS makes it worse
When clients dump photos into CMS collections, you end up with hundreds of uncompressed images across every slug.
Manual work doesn't scale
You could export each image to Squoosh individually. For 20 images, maybe. For 500 CMS items? No chance.
Performance scores take the hit
Lighthouse doesn't care about your layout skills if LCP is a 3MB PNG. Heavy source files drag down real-world speed.
What Skwiz actually does
Pick a target - a page, a collection, or your whole project - and Skwiz handles the rest.
Batch compression
Select dozens or hundreds of images. Compress them all in one pass, same quality settings.
Format conversion
Convert PNGs to WebP, or re-encode JPEGs at lower quality. You choose format and effort.
Resize to fit
Downscale images to match their container. No point serving 4000px for a 400px card.
Side-by-side preview
Compare before and after visually - pixel-level - before committing changes to Framer.
Encoder controls
Quality, effort, encoding parameters. Same controls from Google Squoosh, built in.
Two modes
Lite for quick one-click optimization. Advanced for full control over every parameter.
Here's what it looks like once your images are loaded.
What optimization actually looks like
Real comparison data from a project with 5 hero images.
Performance impact
| Metric | Before | After Skwiz |
|---|---|---|
| Total file size | 5.2 MB | 480 KB |
| Page load | 3.2s | 0.4s |
| Bandwidth / mo (1k visits) | 5.2 GB | 480 MB |
| Reduction | - | ~90% |
Everything included in every plan
No feature gates. No tiers. Just the full toolset.
Smaller files mean less data transferred. Save on hosting and CDN costs every month.
Process your entire project in one session. No per-image limits on Pro plans.
Scan your entire Framer project, current page, or selected elements. Find every image automatically.
Batch-compress entire CMS collections - hundreds of items optimized in minutes.
Compare original vs compressed side by side. Only commit changes you're happy with.
Apply visual effects - brightness, contrast, grayscale, and more - to all images at once.
One plan, every feature. Pick your billing.
No tiers, no gated functionality. Every plan gets everything.
Solo Monthly
Solo Yearly Best Value
Lifetime Access Early Users Offer
Common questions
Everything you need to know before getting started.
Yes, 100%. All image processing happens locally in your browser using WebAssembly. No images are ever uploaded to any server. Your files never leave your machine.
Skwiz is powered by Google Squoosh's WebAssembly encoders - the same battle-tested codecs (MozJPEG, libwebp, oxipng) used by the Squoosh web app. These are widely recognized for delivering one of the best quality-to-size ratios available.
Skwiz lets you optimize entire Framer projects and thousands of CMS pages in one click. Features like real-time preview, per-image or batch settings, a built-in visual effects pipeline, and granular control over format, quality, and dimensions - all without leaving Framer.
Framer's built-in optimization is a great start, but Skwiz complements it by addressing what Framer doesn't control: source image file size (large uploads still cost bandwidth), browser rendering cost, slow Largest Contentful Paint (LCP) and rendering bottlenecks. Skwiz gives you fine-grained control over format, quality, and dimensions to ensure every image is truly optimized for web performance.
Skwiz always shows a real-time preview before replacing any image. You decide the format, quality, and dimensions - nothing is applied automatically without your confirmation. You stay in full control of the visual result.
Yes - in a positive way. Smaller image files improve page load speed, which directly impacts Core Web Vitals like LCP. Faster sites lead to better user experience and stronger search performance.
Skwiz offers flexible pricing including monthly ($7.49/mo), yearly ($64.99/yr), and lifetime ($89.99 one-time) options. You can cancel anytime on subscription plans.
Skwiz replaces images inside your Framer project only after you confirm. We recommend duplicating your project before large-scale optimization, but no changes are made automatically without your approval.
Yes. Since all processing happens locally in your browser, Skwiz can function without uploading anything to external servers.
Skwiz is engineered to handle large-scale projects efficiently. Images are processed in controlled sequential batches with memory management optimized for Framer's API, allowing you to safely compress thousands of images without freezing your browser.
WebP (recommended for best compression), JPEG, and PNG. Each format includes advanced options like chroma subsampling, progressive rendering, lossless mode, and compression effort controls.
From the Skwiz team
Tips and guides on Framer performance, image optimization, and building faster sites.
Framer Image Optimization Checklist: Ship Every Project Under 2MB
A pre-launch checklist for Framer designers who want fast sites without the guesswork.
GuideHow to Reduce Framer Bandwidth Costs Without Changing Your Design
Practical steps to cut hosting costs by optimizing image weight - without redesigning anything.
SEOWhat is LCP and How to Fix It on Your Framer Site
A practical breakdown of Largest Contentful Paint and how image optimization directly improves it.
GuideHow to Cut Your Framer Site's Load Time in Half
A step-by-step walkthrough on identifying heavy images and batch-compressing them without visible quality loss.
Deep DiveWebP vs JPEG vs PNG: Which Format Should You Use in Framer?
Breaking down format tradeoffs, browser support, and when each format makes sense for your project.
Case StudyOptimizing 500+ CMS Images for a Real Estate Agency
How one agency used Skwiz to compress an entire property catalog and save 2.3GB of bandwidth per month.
Earn by recommending Skwiz
Know Framer designers or agencies? Send them our way and earn on every sale.
How it works
Sign up for a referral link. Share it with your audience, community, or clients. When someone subscribes through your link, you earn a commission - recurring on subscriptions, flat on lifetime.
- 20% commission on every referral
- Recurring on monthly and yearly plans
- 30-day cookie window
- Real-time dashboard to track earnings
- Payouts via PayPal or Stripe
Your images should be as polished as your layout.
Stop uploading raw camera exports. Stop ignoring CMS bloat. Skwiz handles it in minutes.
Get Skwiz - Free Trial