| 开发者 |
blinkimg
devsahadat |
|---|---|
| 更新时间 | 2026年11月19日 09:16 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Only for Blinkimg's engine. A free Blinkimg account includes 500 credits every month. Create one at blinkimg.com, then paste its API key on the Blinkimg page under Media. This server needs no account.
Yes. Choose This server in Settings, Compression, or Use local conversion without an account when you connect. Your server's GD or Imagick then makes the files, with no credits. Making images takes your server's CPU and memory, so your site can slow down, most of all on shared hosting. Blinkimg's engine does the work on our servers and makes better-looking, smaller files.
Every account gets 500 free credits a month, and the sizes WordPress makes of an image are free. An image and all its sizes cost 1 credit to compress, 2 with WebP and 4 with WebP and AVIF, so 500 credits cover 250 images a month with WebP copies.
A bulk run pauses and goes on by itself when credits arrive, and new uploads wait in the queue. Nothing else stops: your images, Restore and your settings keep working.
Yes. Every optimization uses credits, even when the file was already small. All sizes of one image count as one. Restoring an original uses no credits.
Yes. Each new image is compressed in the background, about 15 to 30 seconds after its upload finishes. Turn it off in Settings, Compression.
JPEG, PNG, WebP and AVIF. Blinkimg also turns iPhone HEIC photos into JPEG, then optimizes them. Blinkimg reads each file's contents to tell its type, so a renamed file is caught. It skips GIF, SVG and animated images. The Media Library says why Blinkimg skipped a file.
Yes. Blinkimg turns each HEIC photo into a JPEG, then optimizes the JPEG like any other image. Most browsers cannot show a HEIC file, and every browser shows a JPEG. When your server's ImageMagick reads HEIC, WordPress converts the photo itself, and that costs no credit. Otherwise, with an account, Blinkimg's engine sends the HEIC to the Blinkimg API and gets back a JPEG. The JPEG is at most 2560 px on its longer side, or the limit you set in Settings, Resize. The conversion costs 2 credits, so a photo with WebP copies costs 4 in all. The HEIC file stays beside the JPEG, and Restore takes the JPEG back to how the conversion made it. Older HEIC photos convert when you optimize them or run Bulk optimize. With This server, a HEIC stays as it is unless WordPress can convert it.
Not with the default. Auto keeps each image looking the same at a smaller size. High quality uses quality 90 for every format and keeps JPEG's full colour, so files are larger. Custom sets one quality from 1 to 100. Choose in Settings, Compression. Compare shows the original beside the result, and Restore restores the original.
Yes. In Media, Library, switch to the list view and select up to 500 images. Choose Optimize with Blinkimg in Bulk actions, then Apply. You see the credits those images need before anything starts. Restore with Blinkimg, in the same menu, restores the originals at no credit cost.
It starts with the images your published posts and pages use, so your visitors see the gains first. Then it takes the rest, newest first. Blinkimg sends at most 100 requests a minute, two for each image, so a run handles up to 50 images a minute and never takes your whole server.
Yes. Use Exclude in an image's Blinkimg column, or open Settings, Exclusions to skip folders, file names or images smaller than a size in KB. A folder ends in a slash, such as 2019/. A file name can hold one star, such as logo-*. A skipped image costs no credits, and the Media Library says why Blinkimg skipped it.
Yes. Before Blinkimg changes a file, it copies the original into a private backup folder. Restoring an image restores its original and removes the WebP and AVIF copies. Restoring uses no credits.
Choose Delete originals in Settings, Backups. Each image you optimize after that moves its backup to a private bin, and your site does not change. To move the backups you already have, open the Space tab's Free space page and use Move to the bin for one image, or Move all originals to the bin. The bin keeps files for 7, 15 or 30 days, or until you empty it, and Restore works until then. Bring back, on the Bin page, keeps an original for good again. Leftovers finds the originals of images you deleted from the Media Library, and deletes them for good after you confirm. On a host that does not allow hard links, Blinkimg moves a file by a copy, checks the copy's bytes, and only then removes the old file.
Open Media, Blinkimg, then the Space tab's Unused images page, and press Find unused images. Blinkimg checks every image in the background and changes nothing. Select images in the Unused list, or press Move all unused images to the bin, and they go to Blinkimg's private bin. Each one comes back with Bring back, or on its own when a visitor asks for it. The bin deletes them for good after 7, 15 or 30 days, or when you empty it.
Open Media, Blinkimg, then the Space tab's Broken images page, and press Find broken images. It runs the same background check as Unused images, so one check fills both pages, and it changes nothing. Blinkimg lists the images your pages, settings and theme ask for that are not on disk, in five kinds: files it can make again, WebP or AVIF copies that are missing, images in Blinkimg's bin, Media Library items with no file, and files that are gone for good. Regenerate makes missing sizes again from the original. Stop serving it shows the original until you optimize the image again. Bring back returns an image from the bin. Remove the record moves an empty item to the bin, where you can bring it back. For a file that is gone, Where it was found shows each place, with an edit link. Blinkimg repairs images and never edits your pages.
With Blinkimg, yes, because nothing is deleted on the spot. Unused images moves an image to a private bin with every size and copy, and only when nothing names it and Blinkimg can bring it back on its own. If a page still asks for it, Blinkimg brings it back the first time a visitor's browser does. The bin deletes images for good only after 7, 15 or 30 days, or when you empty it.
Not without a way back. Unused images, on the Space tab, reads your content, settings, theme and up to 200 of your pages. It lists an image as unused only when nothing names it and it can come back on its own. Just before it moves an image, Blinkimg looks for it again. A moved image leaves the Media Library, and its files wait in Blinkimg's private bin. Bring back, on the Bin page, returns it whole, with its ID, title and alt text. If a page still links to it, Blinkimg brings it back the first time a visitor asks for it. Before the first move, Blinkimg checks that your server lets a visitor's request bring an image back. Where it does not, Move all is off, and Blinkimg warns you before it moves the images you select. An image is deleted for good only when the bin empties.
Blinkimg found only a weak sign that your site uses the image, or it cannot bring the image back on its own. Either way, Blinkimg never moves it. An image needs a look when:
Press Keep on its row, and Blinkimg will not list it as unused again. Blinkimg reads your content, settings, theme files and up to 200 of your pages, so an image a page it read shows is In use. If you already moved the image, it comes back on its own the first time a visitor's browser asks for it, or with Bring back on the Bin page.
WebP only keeps one file of each image: its WebP copy. Choose it in Settings, Backups. Blinkimg points each optimized JPEG or PNG at its WebP file and updates the posts, page builder data, widgets and theme settings that link to it, through WordPress's own functions. The old files move to the bin. An image it cannot update everywhere keeps its JPEG or PNG. WebP only needs WebP copies in Settings, Formats and a bin that keeps files at least 7 days. Restore turns all of it back. Afterwards Blinkimg reads up to 200 pages from your sitemap and lists any image that is missing, with Bring back for each. If an old post still links to a file in the bin, Blinkimg brings the file back the first time a visitor asks for it. Visitors whose browser or app cannot show WebP, such as some email clients, see no image.
Not by default. Your images keep their URLs and file names, and Blinkimg leaves your posts alone. The WebP and AVIF copies sit beside each file, as photo.jpg.webp. WebP only is the exception: it points your posts at each image's WebP file, and Restore points them back.
Choose WebP, AVIF or both in Settings, Formats. Blinkimg then makes the copies for each new upload, and Bulk optimize makes them for the images you already have. Each copy sits beside its image, and your JPEG or PNG stays for browsers that need it. Convert PNG images, on by default, decides whether PNG files get copies too. To keep only the WebP file, choose WebP only in Settings, Backups. With This server, AVIF needs a GD or Imagick that can write it, and Blinkimg says when yours cannot.
Through picture tags, the default. When WordPress prints an image, Blinkimg adds WebP and AVIF sources beside it, and a browser that can show a copy gets it. Other browsers keep the original. It works on every server and needs no setup. Feeds, social previews and emails keep the original JPEG or PNG.
Yes, on Apache and LiteSpeed. Choose Server rules in Settings, Delivery. Blinkimg writes a few lines into the .htaccess file of your uploads folder only, tests them with two tiny test images, and keeps them only when the test passes. Blinkimg removes its lines at once when a test fails, and when you deactivate it. On nginx, Blinkimg shows the lines to add and tests them after you add them; when you leave Server rules, it shows the lines to remove. On IIS, Blinkimg uses picture tags. Server rules work with WP Rocket, W3 Total Cache, LiteSpeed Cache and Really Simple SSL in their usual settings. With Really Simple SSL, an image asked for over http is then sent over http; your pages still redirect.
Yes. Picture tags work with every CDN. For a pull CDN in front of your uploads, add its address in Settings, Delivery; offloaded media in a bucket is not covered. Server rules do not work with a CDN yet. Picture tags serve your copies. After you change delivery or restore images, Blinkimg clears the cache of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Optimizer, Breeze, Hummingbird, Cache Enabler, WP-Optimize or Super Page Cache. An optional Cloudflare API token clears Cloudflare too.
A few themes style an image through its parent, such as figure > img, and a few sliders read the image's parent. Add that page to Skip these pages in Settings, Delivery, or choose Off. Add ?blinkimg=original to a page's address to see it without the copies.
Yes, with the ones about format and file weight. PageSpeed Insights groups them under Improve image delivery. Older reports call them Serve images in next-gen formats and Efficiently encode images. Blinkimg compresses each image and serves WebP or AVIF copies to the browsers that show them. Warnings about image dimensions depend on the sizes your theme asks for. Rebuild image sizes, on the Tools tab's Improve images page, makes the sizes your theme now uses but older images lack. Your score depends on more than images, so test a page before and after.
Yes. Product galleries get the smaller copies too, and when a shopper picks a variation with its own photo, Blinkimg makes sure that photo shows. Elementor's image widgets and galleries get them as well. Elementor's Image Carousel slides keep the original JPEG for now.
Yes, for the images they print through WordPress. Picture tags cover images in post content, blocks and widgets, images printed by WordPress's own image function, and the cover block. Background images set in CSS, and images a theme prints by hand, keep the original JPEG or PNG under picture tags. Server rules, on Apache and LiteSpeed, cover every image under uploads, whatever the theme or builder prints. Picture tags stay off in the editors of Elementor, Beaver Builder, Bricks and Divi, and in the block editor's preview. Find where it is used, on the Space tab's Free space page and in the Media Library, also looks in Elementor, Beaver Builder, Divi and WPBakery page data.
Yes, but let only one of them compress new uploads. When two do, the same file is compressed twice and can get worse. The Logs tab warns when it finds a known image optimizer active. Blinkimg compresses each file as it is now, so an image another plugin already compressed may save little, and every optimization uses credits.
Yes. Network activate it, then open Network Admin, Settings, Blinkimg. Connect one account for every site, or let each site connect its own. You can also keep every site on the network's settings. Each site keeps its own backups, queue and Bulk optimize.
Yes. Run wp help blinkimg to see every command. Use wp blinkimg bulk start to optimize your library, and wp blinkimg run in a system cron if your host blocks WP-Cron. The optimize and bulk start commands ask before they use credits, and bin empty asks before it deletes. Add --yes in scripts.
On a network, a command acts on one site: add --url with the site's address. To run the queue on every site from a system cron, use: wp site list --field=url | xargs -I{} wp --url={} blinkimg run --seconds=50
Yes, by default. Remove EXIF metadata takes out the camera, date, GPS, copyright and author. Remove AI image metadata takes out AI tool names, prompts and the made-by-AI tag. Turn either off in Settings, Metadata. Colours are turned into sRGB either way, so they look the same in every browser.
Yes, when an image has none. Blinkimg uses the image title, cleaned, so red-velvet_cake-1024x768 becomes "Red velvet cake", and skips titles like IMG_4021. It never changes alt text you wrote. This uses no credits and no account.
Not in place. WordPress already scales every upload larger than 2560 px and keeps the full upload beside it. In Settings, Resize, you can set your own limit from 320 to 10,000 px for new uploads. Blinkimg never turns WordPress's scaling off.
With Blinkimg's engine, no. Blinkimg works in the background, at most 100 requests a minute, and never while a visitor loads a page. With This server, making images uses your server's CPU and memory, so your site can slow down. Blinkimg's engine does that work on our servers.
Yes. Choose Blinkimg's engine there: our servers make the files, and your site only sends each image and saves the results. Background work runs through WordPress's scheduled tasks. When they do not run on your host, Blinkimg tells you how to fix it.
Yes, if you choose it. By default only administrators and editors can optimize images, because each image spends your credits. Set Who can optimize images in Settings, Advanced. Each person still needs the right to edit that image.
No. Deactivating keeps your images compressed, and your pages show your JPEG and PNG files instead of the copies. Deleting Blinkimg removes its settings and records of work in progress, and keeps your backups and copies so a reinstall can restore your images. To delete those too, turn on Delete backups and copies in Settings, Advanced. Images that use WebP only keep working either way.
It works, but use one key per site: then Blinkimg shows each site's usage, and you can turn off one site without the others. On multisite, one network key can cover every site.
Only when you turn on "Email when a bulk run ends" in Settings, Advanced. WordPress then sends a short summary to the site's Administration Email Address. Nothing goes to Blinkimg, and the email never holds your API key or file names.
Email sahadat@blinkimg.com privately. We acknowledge a report within 2 days and aim to fix a high-severity problem within 7 days. Details are in SECURITY.md in the plugin folder.