[WordPress] 外掛分享: Pixel Forge

首頁 › 外掛目錄 › Pixel Forge
WordPress 外掛 Pixel Forge 的封面圖片
全新外掛
安裝啟用
—
尚無評分
6 天前
最後更新
—
問題解決
WordPress 6.5+ PHP 7.4+ v1.0.0 上架:2026-10-09

外掛標籤

開發者團隊

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

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

原文外掛簡介

Pixel Forge converts the images already in your media library to WebP and AVIF, the modern formats that are far smaller than JPEG and PNG at the same quality. It works through your library in small batches with a progress bar you can watch, and it keeps every original file exactly as it is.
When you want the next-gen files gone, one click removes all of them and leaves your originals untouched. Nothing about the process is destructive.
What makes it different
Most converters in this space hand the work to a paid external service and your images leave your server. Pixel Forge does the opposite: everything runs locally through WordPress’ own image engine, with no third-party service, no account, no API key, and no per-image credits. Nothing about an image ever leaves your site.
It is also completely reversible. Originals are never modified or replaced, every generated file is recorded, and one click removes all of them. And you are not limited to a single bulk run: a Next-gen column in the Media Library shows each image’s status and real savings, with Convert and Remove right there on the row.
What you get

Bulk conversion of your whole library to WebP, AVIF, or both.
A live progress screen that converts in small batches, so large libraries do not time out.
A Next-gen column in the Media Library with per-image savings and one-click Convert or Remove.
A quality control, and automatic detection of which formats your server can create.
Optional front-end delivery: images are served inside a tag with the original as a fallback, so a missing file can never break a page.
One-click rollback that deletes every generated file and keeps your originals.
Fully local. No external services, no account, no data leaving your site.

How conversion works
Each original keeps its place. Pixel Forge writes the new file next to it with the format added to the name, for example photo.jpg gets a photo.jpg.webp beside it. The full-size image and every thumbnail size are converted, and each generated file is recorded so rollback can find and remove it.
How serving works
Serving is off until you turn it on. When it is on, an image that has a matching WebP or AVIF file is output as a element with the next-gen sources first and the original last. The browser downloads the first format it understands and falls back to the original otherwise.

延伸相關外掛

文章
Filter
Mastodon