[WordPress] 外掛分享: Squishify

首頁外掛目錄 › Squishify
WordPress 外掛 Squishify 的封面圖片
全新外掛
安裝啟用
尚無評分
5 天前
最後更新
問題解決
WordPress 6.5+ PHP 7.4+ v1.7.0 上架:2026-07-22

內容簡介

Squishify 是一款專為優化圖片而設計的 WordPress 外掛,能在圖片上傳前於瀏覽器中進行轉換與調整,避免原始圖片佔用伺服器空間,讓網站運行更流暢。

【主要功能】
• 瀏覽器內優化圖片,無需上傳原始檔
• 自動優化功能,簡單設置後無需記憶
• 批次編輯圖片,支持調整格式與品質
• 實時前後比較,確保最佳效果
• 支持拖放操作,提升使用便利性

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.7.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Squishify」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

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

Two views, one queue — a Grid / Preview switch sits in the header all session. Grid shows every image you queued at a glance; Preview works through them one at a time with the full before/after comparison
Batch settings apply to every image in one move — format, quality and effort, a max width, a crop ratio, and a numbered rename sequence
Jump straight to an image — click any tile in the grid to open it on its own, then switch back whenever you like
Batch settings stick — add more images later and they inherit the size, crop and rename sequence you already chose

Resize, crop and rename

Resize images individually or all at once, to the exact size you need
Crop to a fixed ratio (1:1, 4:3, 16:9) or to exact output dimensions — one image, or the same shape across the whole batch
Batch crop by ratio — every image gets the largest centred window at the ratio you pick, shown right in the thumbnails
Batch rename three ways — rename one image, number a whole sequence, or type a name for every image in one pass
Numbered sequences with or without a prefix (gallery-01… or just 1, 2, 3), zero-padded so 12 images sort correctly instead of running 1, 10, 11, 12, 2

Real encoders, running on your own machine

libavif (AVIF), libwebp (WebP), MozJPEG, and Oxipng (PNG) — the same encoders behind Squoosh, compiled to WebAssembly and running in your browser
Per-image format, quality and effort controls, with a live before/after comparison loupe
No cloud API, no credits, no quotas, no account — there is no server to send anything to
Your images never leave your device until you choose to upload the finished files to your own site

Getting images in

Drag and drop a batch, or a whole folder — everything inside it gets queued at once, up to 50 images per batch
Paste from your clipboard — press Ctrl/Cmd+V to drop a screenshot straight into the queue, no saving to disk first
SVG files rasterize at a proper working size instead of their (often tiny) declared dimensions
Upload straight to the Media Library when you’re ready

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.
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.

延伸相關外掛

文章
Filter
Mastodon