Linux 软件免费装
Banner图

Squishify

开发者 xcastaneda
更新时间 2026年9月15日 01:41
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

webp resize images auto optimize image optimization avif

下载

1.3.1 1.8.0 1.1.2 1.2.2 1.3.0 1.0.1 1.2.0 1.4.0 1.1.0 1.5.0 1.6.0 1.7.0

详情介绍:

Prep your images. Nothing gets uploaded. 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. It converts and resizes images in your browser, before they are sent — so the full-size original never reaches your server at all. Switch it on once and forget it Turn on auto-optimize, pick an output format and a maximum width, and every image added to your site from then on is handled on the way out: the Media Library, the block editor, anywhere WordPress takes an upload. No editor, no extra step, nothing to remember. That is the part no other plugin can copy. Every one of them optimizes uploads after the file has landed on your server, because that is the only place they can reach it. Squishify is the only one where even the zero-effort path never uploads your original. Images it can't make smaller are uploaded exactly as they are, and GIFs and SVGs are never converted. Auto-optimize is free — it is not a Pro feature. Or open the editor and work a batch by hand Drag a batch of images into the Squishify editor, right inside wp-admin. Resize, crop, rename, and tune format and quality with a live before/after comparison — then nothing touches your site until you click Upload. Only the finished, optimized files reach your Media Library. Work on the whole batch at once Resize, crop and rename Real encoders, running on your own machine Getting images in No duplicate -scaled files on your server 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.

安装:

  1. Upload the squishify folder to /wp-content/plugins/, or install the zip via Plugins → Add New → Upload Plugin.
  2. Activate the plugin.
  3. Open Media → Squishify, or click the Squishify button on the Media Library screen.

屏幕截图:

  • **The Squishify editor**, open as a full-screen overlay inside wp-admin. Drop a batch in; nothing has been uploaded yet.
  • **A batch queued up** — five images waiting with their original sizes, before anything is processed.
  • **Preview view** — drag the before/after loupe to compare the original against the encode. 4.78 MB down to 111.4 KB, a 98% saving, before a single byte reaches the server.
  • **Grid view** — the whole batch at a glance, with batch settings underneath: format, quality and effort, a max width, a crop ratio, and a rename sequence, applied to every image at once.
  • **Resize** to an exact width — on this image, or across the whole batch.
  • **Finalize** — what the batch saved, and the one button that sends the finished files to your Media Library.
  • **Optimized files in the Media Library** after upload — one file each, no server-side duplicate.
  • **Media → Squishify** — the compatibility check that confirms uploads work on your site.

常见问题:

Does auto-optimize apply to images other people upload?

Yes — that is what makes it useful. Once an administrator switches it on it covers every upload by every user on the site, including people who have never opened Squishify. They see a short "Squishify is optimizing" dialog with a link to the setting, so nobody is left wondering what happened to their file. Only administrators can change or switch it off.

My host can't make thumbnails from AVIF. Does auto-optimize still work?

Yes, and it checks for you. Some hosts' image libraries are built without AVIF support, and on those WordPress stores and serves the full-size AVIF but generates no smaller crops. Squishify asks your server that question and pre-selects WebP instead when the answer is no — and if you choose AVIF anyway, the setting says plainly what it will cost.

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.

Can I paste a screenshot straight in?

Yes. Copy an image anywhere, then press Ctrl/Cmd+V with Squishify open and it joins the queue like any dropped file — no saving to disk first. On Chromium-based browsers (Chrome, Edge), Squishify can also notice an image waiting on your clipboard when you switch back to the tab and offer to paste it for you; there's a Don't ask again if you'd rather it didn't. Firefox and Safari don't allow that passive check, so on those browsers use the keyboard shortcut.

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.

更新日志:

1.8.0 1.7.0 1.6.0 1.5.0 1.4.2 1.4.0 1.3.1 1.3.0 1.2.2 1.2.0 1.1.2 1.1.0 1.0.1 1.0.0 0.1.0