Katrangan
Every major image plugin optimizes images after they’re uploaded — the full-size originals still travel over the wire, still land on your server, and still eat disk space.
Squishify flips the order. Drag a batch of images into the Squishify editor (right inside wp-admin), tune format, quality, and size with a live before/after comparison, and nothing touches your site until you click Upload. Only the finished, optimized files reach your Media Library.
- Real encoders — libavif (AVIF), libwebp (WebP), MozJPEG, and Oxipng (PNG), running as WebAssembly in your browser
- Batch queue with per-image format, quality, effort, and resize controls
- Live before/after comparison loupe
- Upload straight to the Media Library when you’re ready
- No cloud API, no credits, no quotas — the work happens on your machine
- Your images stay private until you upload them to your own site
Images are capped at 2560px on the longest edge before encoding — the same threshold WordPress core itself uses (big_image_size_threshold). Because the file you upload is already at or under that size, WordPress never generates its own separate -scaled copy: what you see in the editor is what ends up in your Media Library, one file, no server-side duplicate.
assets/squishify-wp.js is shipped unminified — a Rollup/Vite bundle of the plugin's source with original names and formatting intact, not obfuscated or compressed.
Credits
Squishify’s WebAssembly encoders are provided via jSquash (MIT/Apache-2.0), which wraps libavif (BSD-2-Clause), libwebp (BSD-3-Clause), MozJPEG (BSD-style), and Oxipng (MIT) — all GPL-compatible. The .wasm files are unmodified upstream builds.
Gambar conto
Pemasangan
- Upload the
squishifyfolder to/wp-content/plugins/, or install the zip via Plugins Add New Upload Plugin. - Activate the plugin.
- Open Media Squishify, or click the Squishify button on the Media Library screen.
FAQ
-
Are my images sent anywhere for processing?
-
No. All compression, conversion, and resizing happens locally in your browser. The only network transfer is the final upload of finished files to your own WordPress site.
-
What formats can it produce?
-
AVIF, WebP, JPEG (MozJPEG), and optimized PNG (Oxipng). AVIF uploads require WordPress 6.5+.
-
Uploads fail with an error mentioning a security plugin or firewall
-
Some security hardening (Sucuri, ModSecurity, host firewalls) can block media uploads through the WordPress REST API before WordPress ever sees them. If uploads fail with that message, review your security plugin’s hardening options or ask your host to allowlist REST media uploads (
/wp-json/wp/v2/media). Squishify uses the same standard upload format as WordPress’s own uploader. -
Does it work with multisite?
-
Yes. Squishify checks the standard
upload_filescapability on whichever site you’re on, so it works whether the plugin is network-activated or activated per-site — no separate configuration either way. -
What happens to my original files?
-
Nothing — Squishify never touches them. Everything happens in your browser on a copy of the image; your source file is only read, never modified. Only the optimized output you choose to upload leaves the editor, and only after you click Upload.
-
Why is the first AVIF encode slower than the rest?
-
The AVIF encoder is a WebAssembly module that has to be downloaded and compiled by your browser the first time it’s used in a session. After that one-time warmup, your browser caches the compiled module and subsequent encodes are much faster.
-
What browsers are supported?
-
Any current version of Chrome, Firefox, Safari, or Edge. All processing uses standard Web APIs (WebAssembly, Web Workers) with no browser-specific requirements.
Mācā ulang
There are no reviews for this plugin.
Contributors & Developers
“Squishify” is open source software. The following people have contributed to this plugin.
Kontributor
Translate “Squishify” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Caathetan Owahan
1.0.1
- Fix: guard against a file being added to the queue twice from a single drop/select action.
1.0.0
- First public release: editor overlay, batch queue, upload to Media Library.
0.1.0
- First development release: editor overlay, batch queue, upload to Media Library.