100% Client-Side Privacy

Optimize assets.
Without the wait.

Convert. Compress. Rename. Runs entirely locally.

or

Drop your images here

PNG and JPEG only. Converts to WebP, compresses, renames — all locally.

PNG → WebP
JPG → WebP
Compress
Batch rename
100% Local · Privacy First

Verified Benchmarks

Real-world results measured directly from developer environments. No synthetic numbers, no fake social proof.

Current Release

v1.0.0

Production-ready CLI bundle equipped with watcher daemons, multi-format export, and framework diagnostics.

Size Reduction

47% Less Bloat

Compressed 89.3 MB → 47.7 MB across a test suite of 250 Images with zero perceptual loss.

Cache Performance

57× Faster

Subsequent executions utilize SHA-256 hash caching, bypassing untouched assets to optimize incremental builds instantly.

NPM Package Integration

Prefer terminal workflows? Integrate the local-only optimizer natively into your project and CI/CD pipelines in three simple steps.

Step 01Global

Install package

Install the CLI utility globally to access standard optimizations anywhere on your system.

npm i -g assetflow-cli
Step 02Recommended

Run diagnostics

Analyze project directories to flag large images, missing format alternatives, and caching state.

npx assetflow-cli doctor
Step 03Automation

Batch optimize

Compress and optimize directory files instantly. Progress and compression metrics are stored locally.

npx assetflow-cli optimize

How it works

AssetFlow processes files 100% locally in your browser. Your files are routed through a high-performance client-side pipeline powered by the Canvas API and Web Workers, outputting optimized, professional-grade formats instantly with zero server uploads.

Features

AssetFlow is packed with client-side utilities engineered for modern developer workflows. Convert, compress, and rename assets with zero delay.

Zero server uploads

Your files never leave your browser sandbox. All conversion, cropping, and optimization runs 100% locally on your computer via the Canvas API and isolated memory buffers.

Local ContextsProcessed inside sandbox context buffers.
Data IsolationZero server transit logs or API storage.
RUN LOCALLYPNGJPGWEBP

Web Worker powered

Offloads image encoding to parallel background threads, keeping your user interface responsive at 60fps under load.

UI Main Thread IdleNo UI freezing or scroll latency.
Worker PoolsParallel Web Workers for high throughput.
INPUTworker 1worker 2worker 3W1W2W3

Developer-first experience

Packed with client-side shortcuts and features engineered to speed up your asset pipelines: sequential renaming, slugs, automatic format mapping, and a keyboard-driven ⌘K command palette.

⌘K PaletteCommand center
Slugify ModeURL-safe names
SequentialAuto-numbering
ZIP ExportBatch downloads
assetflow-compiler
~/assetflow $ assetflow-cli optimize ./assets/*.png
→ [1/3] logo.png [342KB] -> logo.webp [41KB] (saved 88%)

Offline-first.
Your assets remain yours.

In an era of server harvesting, we believe your work should stay in your sandbox. Every single compression, format change, and batch slug conversion happens strictly inside your browser sandbox.

Your files are never serialized, never sent across a network cord, and never leave your hardware. Zero data collection, zero network request logs, 100% client-side execution.

Zero network requests · 100% Client-side sandbox
LOCAL DISKClient-sideSANDBOXDOWNLOADS

Frequently Asked Questions

Everything you need to know about AssetFlow, our client-side toolkit, and CLI integrations.

What is AssetFlow?

How does AssetFlow work?

AssetFlow vs Next.js Image

AssetFlow vs Imagemin

Does AssetFlow work with React, Next.js, and Vite?

Who is AssetFlow for?

Why not use an Image CDN?

AssetFlow vs TinyPNG

Does AssetFlow modify original images?