Squishify
| 开发者 | xcastaneda |
|---|---|
| 更新时间 | 2026年8月1日 13:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Real encoders — libavif (AVIF), libwebp (WebP), MozJPEG, and Oxipng (PNG), running as WebAssembly in your browser
- Batch queue with per-image format, quality, and effort controls
- Resize images individually or all at once to the exact size needed
- 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
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.
安装:
- 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.
屏幕截图:
常见问题:
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_files capability 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.
更新日志:
- Fixed resized images looking softer or jagged compared to a desktop editor's export, especially on small or heavily cropped outputs — resizing now uses a sharper algorithm, with safeguards to keep large source photos fast.
- Drag a whole folder of images onto the dropzone to queue everything inside it at once.
- SVG images now rasterize at a proper working size instead of their (often tiny) declared dimensions.
- Added an in-app "what's new" modal so you'll see a quick summary the next time a new version ships.
- Fix: guard against a file being added to the queue twice from a single drop/select action.
- First public release: editor overlay, batch queue, upload to Media Library.
- First development release: editor overlay, batch queue, upload to Media Library.