DEV Community: zippic

Compressez vos images sans jamais les envoyer sur un serveur

zippic — Wed, 21 Oct 2026 22:40:58 +0000

Vous connaissez le réflexe : pour compresser une photo, on l'envoie sur un site en ligne, on attend, puis on télécharge le résultat. Le problème, c'est que la photo quitte votre ordinateur. Pour une photo de client, un visuel pas encore publié ou un document sensible, ce n'est pas anodin.

ZipPic fait l'inverse : tout se passe dans votre navigateur. Ouvrez https://zippic.app, déposez vos images, et la compression a lieu localement, sur votre appareil. Aucun fichier n'est envoyé sur un serveur, aucune inscription n'est demandée.

Concrètement, j'ai testé avec une photo de téléphone de plusieurs Mo : après compression, elle ne pèse plus que quelques centaines de Ko, et la différence visuelle est imperceptible. Le comparateur avant/après, intégré à l'outil, permet de le vérifier en direct, sans faire confiance à une promesse.

Et ce n'est pas qu'un compresseur. ZipPic regroupe 18 outils gratuits dans le navigateur : compression d'images (JPG, PNG, WebP, GIF, AVIF), compression par lots, recadrage, filigrane, conversion HEIC vers JPG/PNG, PSD vers image, PDF vers images, création et découpage de GIF, création d'APNG, conversion et recadrage vidéo, vidéo vers GIF, et compression de documents (PDF, Word, PowerPoint).

Contrairement à TinyPNG, il n'y a pas de limite de 20 images ni de 5 Mo. Pour un vendeur PrestaShop ou Shopify qui doit préparer des dizaines de photos de produits, ou pour un photographe qui livre des images à un client, cette absence de limite change vraiment l'usage.

L'interface existe en français, et l'outil est gratuit, sans inscription. Si vous cherchez un moyen de compresser vos images sans les envoyer quelque part, essayez-le : https://zippic.app

I Stopped Uploading Client Photos to Online Tools. Here's What I Use Instead.

zippic — Wed, 21 Oct 2026 22:36:12 +0000

If you handle client photos — real estate shoots, product photos, headshots, unreleased designs — every "free" online compressor asks you to do something you probably shouldn't: upload someone else's files to a server you don't control.

I used to do it too, because it was fast. Then a client asked, point blank: "Where do these photos go when I compress them?" I didn't have a good answer.

So I built the tool I wanted to exist.

ZipPic runs 18 media tools entirely in your browser with WebAssembly. Compression, bulk compression, HEIC to JPG, PSD to images, PDF to images, GIF and APNG makers, video tools, doc compression — all of it happens on your device. Nothing uploads. Open the Network tab while you work and check: zero bytes leave your browser.

That changes the workflow in three practical ways:

No caps to work around. TinyPNG stops you at 20 images and 5MB per file. A real estate shoot or a Shopify product batch blows past that in minutes. Local processing has no batch limit to hit.
No waiting on uploads. A 50MB PDF or a folder of RAW-adjacent phone photos doesn't need to go up to a server and back down again. It just processes.
No awkward client conversation. You can honestly say the files never left your machine.

It's free, no signup, and it works offline after the first load. That last part matters more than I expected — I've compressed photos on planes and in cafes with bad Wi-Fi.

I'm not saying never use a server tool. If you need heavy AI upscaling or team collaboration, a server makes sense. But for compress, convert, crop, watermark, and split — the everyday jobs — local is faster, more private, and has no reason to cap you.

Try it and check the Network tab. That's the whole pitch: https://zippic.app

(Disclosure: I'm the developer.)

ZipPic vs Squoosh: The Three Jobs Squoosh Can't Do

zippic — Tue, 20 Oct 2026 14:00:40 +0000

Squoosh is a genuinely good tool. If you want to squeeze one hero image and compare AVIF against WebP against MozJPEG with a side-by-side preview and fine-grained codec settings, it's still one of the best pages on the internet for that.

But most image work isn't one hero image. It's a folder of product photos. It's a GIF that's 12MB. It's an animated WebP banner. And on those three everyday jobs, Squoosh simply can't help you — not "does it worse," but doesn't do it at all. I checked each one against Squoosh's app and its GitHub repo before writing this.

1. Batch compression: one image at a time, forever

Squoosh's editor loads exactly one image. There is no multi-file upload, no queue, no "download all." Fifty screenshots means fifty rounds of open → compress → download.

This isn't an oversight that got fixed. Users have been requesting batch support since 2018 (the GitHub issues are still open), and the maintainers' answer at the time was to use the Squoosh CLI instead — which has since been deprecated.

ZipPic's bulk image compressor is built the other way around: drop in as many images as you like (there's no strict count limit; files under 50MB each are recommended), let it process, and hit Download All to get everything back as a single ZIP. JPG, PNG, WebP, GIF, AVIF, HEIC and even RAW files are accepted, and like Squoosh, everything runs locally in your browser — nothing is uploaded to a server.

2. GIF: Squoosh can't output one — and destroys animated ones

Open Squoosh's format dropdown and you'll find AVIF, MozJPEG, OxiPNG, WebP, WebP v2, JPEG XL (beta), QOI and the browser codecs. No GIF. Squoosh cannot save a GIF file, compressed or otherwise.

Worse, if you open an animated GIF in Squoosh, you don't get a smaller GIF back — you get the first frame as a still image. The animation is gone.

In ZipPic, GIF is a first-class format: the compressor takes GIFs in and gives compressed GIFs back, animation intact. And when a GIF needs more than compression — trimming frames, adjusting delays, reordering — there's a dedicated GIF Maker for creating and editing animated GIFs locally.

3. Animated WebP: flattened to frame one

Animated WebP is where this gets painful, because it's the format people reach for precisely to replace heavy GIFs. Squoosh doesn't preserve it. As its own maintainer put it in the repo: Squoosh doesn't "support animation at all" — open an animated WebP and only the first frame survives, converted to a static image. The same applies to animated AVIF.

ZipPic's compressor lists Animated WEBP as an output format. Feed it an animated WebP and you get a smaller animated WebP back, still moving. Feed it an animated GIF and you can convert it to animated WebP instead — usually the single biggest saving available for web animations, since WebP typically cuts 60–80% off a GIF's size at similar quality.

The honest summary

Job	Squoosh	ZipPic
Single image, deep codec tuning (AVIF, JPEG XL, QOI)	✅ Excellent	✅ Good
Batch-compress many images at once	❌ One at a time	✅ Unlimited batch + ZIP download
Compress a GIF	❌ No GIF output	✅ GIF in, GIF out
Compress an animated GIF / WebP, keeping the animation	❌ First frame only	✅ Animated WebP / GIF output
Runs 100% locally, no upload	✅	✅
Price	Free	Free

Squoosh remains a superb single-image codec laboratory, and I still use it that way. But the moment your job involves many images, a GIF, or anything that moves, you need a tool that actually does those jobs — that's the gap ZipPic was built to fill.

Disclosure: I build ZipPic. Every Squoosh limitation above is verifiable in the live app and the public squoosh repo on GitHub — check for yourself before you trust either of us.

Your PNG Screenshots Are 5x Bigger Than They Need to Be

zippic — Mon, 19 Oct 2026 03:34:51 +0000

I published a tutorial last month with 14 screenshots. After it went live, I checked the page weight out of curiosity: 38MB. Thirty-eight megabytes — for a page that is mostly text.

Every screenshot was a PNG, straight from my Mac's screenshot tool. A single full-screen Retina capture was 4.2MB. I had uploaded them exactly as they came out of the OS, the way most of us do.

Why screenshots are so heavy

Three things conspire against you:

Retina resolution. A screenshot on a modern display is 2x or 3x the CSS pixels. That 1440px-wide illustration in your article is actually a 4320px-wide PNG.
PNG is lossless. Great for crisp UI text, terrible for file size. Any photo-like gradient or shadow in the shot balloons fast.
Nobody compresses before uploading. Platforms will happily serve your 4MB original to every single reader.

The kicker: after compression, my 4.2MB screenshot came out at 380KB — and I could not tell the difference at article width. The detail PNG preserves is detail no reader will ever see, because the image is displayed at a fraction of its native resolution anyway.

The 30-second fix

I don't hand-tune screenshots anymore. My workflow now:

Take the screenshot as usual — PNG, full Retina glory.
Drop it into ZipPic's image compressor — free, runs entirely in your browser, no signup, no upload.
It compresses locally and shows a live before/after comparison. Nudge the quality slider until the text edges still look crisp.
Download, then upload the compressed version to your post.

That 14-screenshot tutorial went from 38MB to under 5MB. Load time went from "go make coffee" to instant — and every reader on mobile data got a faster page for free.

The part nobody thinks about: what's in the screenshot

Screenshots are uniquely sensitive uploads. Open tabs, file paths, a Slack DM in the background, an API key sitting in a terminal window you forgot was visible. Every "free online compressor" that asks you to upload a screenshot is asking you to hand all of that to a stranger's server first.

I started compressing locally for the file size. I keep doing it for the privacy. Nothing leaves your machine — the work happens in your browser via WebAssembly, and the file you download is the only copy that ever moves.

Next time you write a tutorial, try this: take one PNG screenshot, run it through a local compressor, and compare them side by side at article width. If you can't spot the difference — and you won't — there's no reason to ever upload the original again.

That 50MB PDF You're Trying to Email? It Could Be 3MB.

zippic — Sun, 18 Oct 2026 08:47:02 +0000

Last week I tried to send a scanned contract over email. 47MB. Gmail's attachment limit is 25MB. The client's upload portal capped at 10MB. I ended up splitting it into five parts like it was 2004.

The file was 40 pages of mostly text with a few scanned signatures. There was no reason for it to be 47MB — except that whoever scanned it saved every page as a full-resolution image with zero compression.

Why PDFs get so fat

Most bloated PDFs come from the same source: scanned pages or exported slides where images were embedded at far higher resolution than anyone will ever view. A scanned page at 600 DPI looks identical to one at 150 DPI on screen, but takes 4x the space. Multiply by 40 pages and you're emailing a small movie.

The traditional fix is Adobe Acrobat's "Reduce File Size" — if you have a subscription. Or one of those free online PDF compressors, where you upload your contract (with signatures, account numbers, whatever) to a stranger's server and hope for the best.

I wasn't comfortable with either option for client documents.

Compress it where it already is

PDF compression is just image recompression plus metadata cleanup — the kind of thing a browser can do locally with WebAssembly. No server needed, which means your documents never leave your machine.

Here's what I do now:

Open ZipPic's document compressor — free, runs entirely in the browser, no signup.
Drop in the PDF. It handles the parsing locally.
Pick a compression level. For screen reading and email, the middle setting is usually plenty — my 47MB contract came out at 3.1MB with no visible difference.
Download the result. Nothing was uploaded anywhere.

That 3.1MB file sailed through Gmail and the client portal without a second thought.

The files you should never upload

Here's the thing I keep coming back to: the documents that most need compressing are exactly the ones you least want to upload. Contracts, financial statements, medical records, unreleased specs — the "please compress this 80MB PDF" request almost always involves something sensitive.

We've normalized uploading these to random free tools because there wasn't a convenient alternative. Now there is. Your browser is fast enough to do it locally, and the result is identical.

Next time a PDF won't fit through email, try compressing it without the upload step first. Your documents — and whoever's waiting on them — will thank you.

Your iPhone Photos Are HEIC. Here's How to Convert Them Without Uploading Anything.

zippic — Fri, 16 Oct 2026 14:55:49 +0000

Every time I transfer photos from my iPhone to my computer, the same thing happens: a folder full of .HEIC files that half my tools refuse to open. My image editor shrugs. The CMS upload form rejects them. A client once asked me why I sent "broken images."

HEIC is genuinely a better format — smaller files, better quality than JPEG. Apple knew what it was doing. The problem is everything else in the world still expects JPG or PNG.

The usual fix is worse than the problem

The standard advice is "just use an online converter." So you drag your photos — sometimes personal, sometimes client work — onto a stranger's website, wait for the upload, wait for the conversion, download the result, and then trust that they actually deleted your files from their server.

For a handful of vacation photos, fine. For a batch of 200 product shots or unreleased screenshots, that's a privacy habit I don't want.

Convert them where they already are: your browser

Modern browsers can run real image codecs locally through WebAssembly — near-native speed, no server involved. Your files never leave your machine because there's nowhere for them to go.

Here's the workflow I use now:

Open ZipPic's HEIC converter — 18 free media tools that all run locally in the browser, no signup.
Drag in the HEIC files — one or a hundred, it handles batches.
Pick the output: JPG for maximum compatibility, WebP or AVIF if you're optimizing for the web.
Hit convert, download the results. Done. Nothing was uploaded.

The same tab also does the obvious next steps: batch-compress the converted files, resize them for web, or strip them down to WebP for a site deploy. One workflow, no new tools to install, no accounts.

Why this matters beyond HEIC

The format mismatch is just the most visible symptom. The deeper issue is how casually we've accepted "upload your files to a random server" as the default step in every media workflow. Compression, format conversion, watermarking, PDF shrinking — we've been trained to hand all of it to someone else's infrastructure.

We don't have to anymore. The browser on your machine right now is fast enough to do all of it locally. Once you've converted a hundred HEIC files without a single byte leaving your laptop, the old upload-wait-download dance feels absurd.

Try it with your next batch of iPhone photos. You won't go back.

5 Tools Every E-Commerce Store Owner Should Be Using

zippic — Thu, 15 Oct 2026 23:03:42 +0000

Most e-commerce advice obsesses over the storefront — the theme, the hero banner, the color of the buy button. But ask any store owner where their week actually goes, and it's the unglamorous stuff: compressing product photos, chasing abandoned carts, begging customers for reviews. The right tools make all of that disappear into the background. Here are the five I'd install on day one.

1. Shopify — The Store Itself

The obvious one, but it earns the top spot. Shopify is still the fastest way to get a real store online: checkout, payments, inventory, and a theme ecosystem that doesn't require a developer for day-to-day changes. If you're running on a patchwork of plugins and spreadsheets, consolidating here pays for itself in the first month.

2. ZipPic — Image Optimization Without the Upload Dance

Here's the unsexy truth: product images are the biggest performance bottleneck on most stores. A single uncompressed hero image can add seconds to load time — and every extra second measurably hurts conversions.

ZipPic is a free toolbox of 18 media tools that run entirely in your browser. No uploads, no signup, nothing leaves your computer. The routine: bulk-compress new product shots, convert iPhone HEIC photos straight to JPG, and export WebP versions for the site. A typical 3MB product photo drops to a few hundred KB with no visible difference. It also covers the boring-but-necessary jobs — batch watermarks for supplier images, GIFs for social posts, PDF compression for spec sheets.

If your product pages feel slow, start here before touching anything else.

3. Klaviyo — Email That Earns Its Keep

Paid ads get expensive; email doesn't. Klaviyo's abandoned-cart flows, post-purchase sequences, and win-back campaigns run on autopilot once set up. For most small stores, email becomes 20–30% of revenue within a few months. The free tier is generous enough to prove it before you pay.

4. Judge.me — Reviews That Do the Selling

Shoppers don't trust product descriptions — they trust other shoppers. Judge.me collects photo and video reviews, displays them where they matter (product pages, Google Shopping), and nudges happy customers at the right moment. Social proof is the cheapest conversion-rate optimization you'll ever buy.

5. Google Analytics 4 — Know What's Actually Working

You can't improve what you don't measure. GA4 tells you which products get views but no carts, which traffic sources actually convert, and where people drop off in checkout. Pair it with Search Console and you have a free analytics stack that covers 90% of what a growing store needs.

None of these tools will sell your products for you. What they buy is your week back — fewer slow pages, fewer abandoned carts, fewer manual chores — so you can spend it on the part that actually grows the business: better products and happier customers. If you only do one thing from this list today, make it the image optimization. It's the fastest win here.

网站图片还不用 WebP？这些好处你可能低估了

zippic — Thu, 15 Oct 2026 08:33:12 +0000

我做独立开发这些年，见过太多网站打开慢，根本不是代码的问题——就是几张 2、3MB 的原图在拖后腿。图片优化里投入产出比最高的一招，就是把 JPG/PNG 换成 WebP。

WebP 到底好在哪

体积小 25%–35%：同等画质下，比 JPEG 和 PNG 小一大截。一张 200KB 的 JPEG 转成 WebP，通常只有 130KB 出头。
有损无损都支持：JPEG 只能有损、PNG 无损但体积大，WebP 两种模式都有，按需选。
支持透明通道：PNG 的透明图可以直接替换，不用担心背景问题。
动图也行：同样动画，WebP 比 GIF 小得多。

首页 10 张图，批量转一遍就能省掉大几百 KB，首屏加载（LCP）改善非常直观。

对 SEO 是真利好

Google 早就把页面速度（Core Web Vitals）算进排名信号。图片更小 → 加载更快 → LCP 更好，这是实打实的加分项。图片搜索对 WebP 也完全正常收录，不用担心"换格式影响收录"。

顺带一提，AVIF 压缩率更高，但编码慢、兼容性还弱一些。现阶段 WebP 是省心度和收益最平衡的选择。

怎么把图转成 WebP

两条路：

命令行批量转：cwebp、sharp、imagemin，适合已经有构建流程的项目；
在线工具直接转：不想折腾环境就用网页工具。

我自己做的 zippic 就是后者思路：18 个媒体工具全部在浏览器本地运行，图片不上传，打开页面就能批量转 WebP，运营和编辑同学也能直接用。中文站地址：https://zippic.cn

上线时的兼容写法

个别老浏览器不支持 WebP，用 <picture> 做一行兜底：

<picture>
  <source srcset="banner.webp" type="image/webp">
  <img src="banner.jpg" alt="banner">
</picture>

新浏览器吃 WebP，老浏览器自动回退 JPG，零风险上线。

总结

换 WebP 是我见过改动最小、收益最大的优化之一。下次发文章、做落地页、传产品图，先转一遍 WebP 再上线，页面会快得让你意外。

Image Compression Is the SEO Win You're Probably Ignoring

zippic — Wed, 14 Oct 2026 07:46:21 +0000

I build and run ZipPic — known as zippic.app internationally and zippic.cn for Chinese users — a free toolkit of 18 media tools that run entirely in your browser. I spend most of my days thinking about one surprisingly neglected topic: how much your images are costing you in search rankings.

Here's the thing nobody tells you when you're obsessing over meta tags and backlinks: images are typically 50–70% of a page's total weight. And page speed — specifically Largest Contentful Paint — is a confirmed Google ranking factor. In other words, that beautiful 4MB hero PNG is quietly dragging your SEO down.

Why I care about this

A while back I was optimizing my own site's Core Web Vitals and discovered something embarrassing: my tool pages were slow because of the demo screenshots. The irony of a compression tool shipping uncompressed images was not lost on me.

That experience shaped how I think about image SEO. It's not a separate discipline — it's just performance work with a search-ranking payoff.

The three levers that actually matter

1. Pick the right format

This is the highest-ROI change most sites can make:

Photos → WebP or AVIF (typically 30–50% smaller than JPG at the same quality)
Graphics with transparency → WebP instead of PNG
Simple icons/logos → SVG, always

I converted my entire site's imagery to WebP and watched LCP drop by over a second on mobile. One format change, no redesign.

2. Compress before you upload, not after

Most CMS "optimization" plugins compress images after they've already been uploaded at full size. That's backwards. The damage — slow uploads, wasted storage, oversized originals sitting on your CDN — is already done.

My workflow now: compress locally first, then upload the already-optimized file. Because zippic runs 100% in the browser via WebAssembly, there's nothing to install and no file ever leaves my machine — which matters when you're handling client assets.

3. Batch it or you won't do it

The reason most sites ship unoptimized images isn't ignorance — it's friction. Nobody wants to compress 40 blog images one by one.

Bulk processing changed this for me. Drag in a folder of images, pick WebP at 80% quality, download them all. Five minutes, done. If your tooling makes the right thing the easy thing, image SEO stops being a chore.

What the numbers look like

On a recent pass over my own content pages:

Average image size: 1.2MB → 180KB (WebP, visually identical)
Mobile LCP: 3.8s → 2.1s
The pages that got faster also started ranking better for their target keywords within a few weeks

Correlation isn't causation, and I won't pretend image compression alone moves rankings. But when Google explicitly tells you speed matters, and images are most of your page weight, the math isn't complicated.

My honest take

You don't need my tool for this — Squoosh, Sharp, and plain old cwebp all work. What you need is the habit: right format, compressed before upload, in batches.

I built zippic because I wanted that workflow to have zero friction: no signup, no upload limits, no files leaving the browser. If that sounds useful, it's free at zippic.app — or zippic.cn if you're in China. 18 tools, 11 languages, everything local.

But even if you use something else: go compress your images this week. Your LCP — and probably your rankings — will thank you.

Disclosure: I'm the developer of ZipPic. The performance numbers above are from my own site.

8 Mac Apps for Maximum Efficiency (With Minimum Software)

zippic — Wed, 14 Oct 2026 06:41:06 +0000

The best Mac setup isn't the one with the most apps. It's the one where every app earns its place. Here are 8 apps that cover AI, knowledge management, window control, screenshots, system cleanup, launching, and package management — nothing more, nothing less.

1. Claude Desktop (with Cowork)

The AI assistant, now living natively on your Mac. The Cowork feature is the real story here: it turns Claude into something closer to a colleague than a chatbot, able to work alongside you on documents, research, and writing tasks.

Why it's on the list: If you do any kind of text-heavy work — writing, summarizing, brainstorming — having Claude one click away beats switching to a browser tab every time.

2. Obsidian (+ AI plugins)

A Markdown-based note app that stores everything as plain local files. Pair it with an AI plugin (like the Claudian plugin) and your notes become a searchable, AI-augmented second brain.

Why it's on the list: Your knowledge stays yours — local files, no lock-in — while AI makes retrieval and synthesis dramatically faster. The 20-minutes-to-second-brain promise is real if you actually write things down.

3. Chrome

Yes, Safari is more power-efficient. But Chrome wins on ecosystem: extensions, dev tools, and seamless Gmail/Google Workspace integration.

Why it's on the list: If your work lives in Google's ecosystem, fighting Safari's quirks isn't worth the battery savings. Pick the browser that matches your workflow.

4. Rectangle

Free, open-source window management. Drag windows to screen edges to snap them into halves, thirds, or quarters — plus keyboard shortcuts for everything.

Why it's on the list: macOS's built-in window tiling is still catching up. Rectangle is lightweight, free, and instantly makes multitasking on a 13" screen bearable.

5. iShot

A clean, free screenshot and screen-recording tool. The rounded-corner screenshots alone make your docs and tweets look 10x more professional.

Why it's on the list: macOS screenshots are fine; iShot makes them beautiful — annotations, rounded corners, and quick sharing without opening another editor.

6. Lemon

A junk/cache cleaner for Macs with tight storage. Finds the gigabytes of caches, logs, and leftovers that macOS never cleans up itself.

Why it's on the list: Especially valuable on 256GB machines. Run it monthly and stop wondering where your disk space went.

7. Raycast

A Spotlight replacement: blazing-fast launcher with a calculator, clipboard history, window management, and hundreds of extensions.

Why it's on the list: Clipboard history alone justifies the install — stop losing that thing you copied three copies ago. The extension store turns it into a command center.

8. Homebrew

The package manager for macOS. Install dev tools, CLIs, and even GUI apps with one command. Also the prerequisite for running things like Claude Code and AI agents locally.

Why it's on the list: If you touch the terminal at all, Homebrew is non-negotiable. brew install beats hunting down .dmg files every single time.

The philosophy

Eight apps. No duplicates, no "just in case" installs. Each one replaces either a worse built-in tool or an entire category of clutter.

What's on your must-install list? I'm always looking for app number nine.