Flying Pigs Uploader

Not for new uploads. Everything Flying Pigs uploads arrives already optimized, with its WebP and AVIF copies. It also keeps its uploads away from optimizer plugins' upload hooks, so a file optimized in the browser lands once and is not compressed again. Keep your optimizer, or its bulk tool, for images that were in your library before.

Flying Pigs works on uploads. Images already in your library stay as they are. To redo one, upload it again; Pro's Overwrite replaces it in place at the same address.

No. Your files go from your browser to your own site, and the free plugin makes no request to any outside service. There is no account or key.

Chrome, Edge, Brave, Safari 16.4 or later, and Firefox on a computer. On a browser without WebAssembly threads, and on most iPads and iPhones, the page still uploads, and WordPress makes the sizes on the server as usual.

The engine needs a fixed 1 GB of memory per worker. Desktop browsers grant it; iPads and iPhones often refuse it, and so does a page that is not cross-origin isolated. When you press Start, the page checks the engine first. If it cannot start, the page says why and switches to fallback: the originals upload as they are and WordPress makes the sizes on the server, the way its own uploader does. In fallback you keep the upload machinery (batches, chunked large files, retries, run recovery), the Sizes panel, WebP and AVIF copies where your host's image library can write them, folders and delivery. You lose the jobs only the engine can do: optimizing the original, PNG to JPG, the AI statement, and the speed, because the server does the resizing again. Those options disable on the page with the reason beside them. A site that wants the server path on purpose can return false from the fpig_client_side_possible filter.

Only if something serves them, and the Delivery panel makes sure something does. If a delivery plugin is active, the panel names it and leaves it in charge; Flying Pigs writes the standard file names those plugins serve (photo.jpg.webp). If nothing serves them, "Set up delivery for me" tests your server and turns on a rewrite in the site's .htaccess where the host honors it, or wraps your images in a <picture> tag on the page. Both can be undone from the same panel.

It can say so, in the file. The AI Data Mining option writes the IPTC "Data Mining" rights statement (IPTC Photo Metadata Standard 2023.1) into every file the browser makes: "No AI training, allow search indexing" (the default), "No AI training, no search indexing", "Allow AI training" or "No statement". It is a statement, not a lock: crawlers that read the standard honor it. For a signal no crawler can miss, add robots.txt rules or an X-Robots-Tag header for your uploads folder as well.

FileBird, Real Media Library, CatFolders, Mediamatic, Filorium, Folders by Premio, Wicked Folders (once its media folders are switched on), HappyFiles, and any plugin that files media under a hierarchical taxonomy. Pick the folder in the run options, subfolders included. Media folders never change where a file sits on disk; that is the File date picker's job, in Pro.

Resize before upload, WebP only, a watermark with a text and logo maker, turbo-boost uploads with a link check, overwriting in place, the File date and Set post date pickers, and photos onto WooCommerce products by SKU or product name, plus updates through your Plugins screen and the help desk. Optimizing, PNG to JPG, WebP and AVIF, choosing sizes, delivery, the AI statement and folders are all free. See flying-pigs.wpspeedmeup.com for Pro.