First release in the WordPress.org plugin directory.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3709383,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3709383,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3709383,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3709383,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.11.101"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3709383,"resolution":"1","location":"assets","locale":"","width":1280,"height":690}},"screenshots":{"1":"The uploader: drop zone, run bar, and the Media, Sizes, Delivery and Advanced panels."}},"plugin_section":[],"plugin_tags":[194661,21756,233,259,15376],"plugin_category":[50],"plugin_contributors":[166418],"plugin_business_model":[],"class_list":["post-370039","plugin","type-plugin","status-publish","hentry","plugin_tags-avif","plugin_tags-bulk-upload","plugin_tags-media-library","plugin_tags-upload","plugin_tags-webp","plugin_category-media","plugin_contributors-48hmorris","plugin_committers-48hmorris"],"banners":{"banner":"https:\/\/ps.w.org\/flying-pigs-uploader\/assets\/banner-772x250.png?rev=3709383","banner_2x":"https:\/\/ps.w.org\/flying-pigs-uploader\/assets\/banner-1544x500.png?rev=3709383","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/flying-pigs-uploader\/assets\/icon-128x128.png?rev=3709383","icon_2x":"https:\/\/ps.w.org\/flying-pigs-uploader\/assets\/icon-256x256.png?rev=3709383","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/flying-pigs-uploader\/assets\/screenshot-1.png?rev=3709383","caption":"The uploader: drop zone, run bar, and the Media, Sizes, Delivery and Advanced panels."}],"raw_content":"\n
On the Media \u2192 Add New page WordPress uploads one file per request and makes every thumbnail on the server: two hundred photos means two hundred requests, two hundred rounds of server image work, and a host's rate limiter slowing the lot. WordPress 7.1 moves that work into the browser for block editor uploads, in Chrome and Edge only, and still sends every thumbnail as its own request. Flying Pigs does the image work in your browser for bulk uploads on the Media page, in every modern browser, and ships the results in a few large requests. The same 221 photos that take the Media page twelve minutes on a managed host, and twenty on a large shared host, take Flying Pigs Free two minutes and nineteen, and less again with Pro's turbo boost.<\/p>\n\n
Found under Media \u2192 Flying Pigs Uploader.<\/p>\n\n
Everything an upload needs is free: the browser image engine, every size, WebP and AVIF, optimizing, folders, delivery, retries. Pro adds the power tools for big libraries and product catalogs.<\/p>\n\n
Free shows every Pro control in place, disabled and badged PRO, so you can see where it would sit. The Free plugin carries none of the Pro code.<\/p>\n\n
Speed, 221 photos (209 MB), same files, same day.<\/strong> WebP-only, HTTP\/2, lean installs with no other plugin hooking uploads. The image work is in your browser, so the host's per-file resizing never enters the race.<\/p><\/li>\n A managed host.<\/strong> WP Media page: 12:20. Free, one lane: 2:19. Pro turbo, two lanes: 2:12.<\/p><\/li>\n A large shared host, its optimizer off.<\/strong> WP Media page: 20:05. Free, one lane: 11:08. Pro turbo, two lanes: 6:09.<\/p><\/li>\n Ready the moment it lands.<\/strong> WordPress: uploads the original, then resizes on the server; optimizers finish later still, on a background job or the first visitor. Flying Pigs Free: every file lands already final, with nothing left to wait on.<\/p><\/li>\n What it does<\/strong><\/p>\n\n Free means free<\/strong><\/p>\n\n There is no file limit, no monthly quota and no account. Your files go to your own site only.<\/p>\n\n None. Flying Pigs Free makes no call to any outside service: the image work happens in your browser and the uploads go to this site's own REST API. Nothing is sent anywhere else, and nothing is collected. (The Pro version has a link check, a speed test against Cloudflare's speed-test endpoint that runs when its button is pressed; the free plugin carries none of that code.)<\/p>\n\n The image engine is wasm-vips, libvips compiled to WebAssembly by Kleis Auke Wolthuizen (MIT), from https:\/\/github.com\/kleisauke\/wasm-vips. The files under vendor\/wasm-vips (vips-es6.js, vips.wasm and vips-heif.wasm) are that project's published npm release 0.0.18, unmodified; vendor\/wasm-vips\/SOURCE.txt records the release, the SHA-256 of each file, and the build instructions. The two .wasm files are the engine itself: every size, WebP and AVIF file is made by them in the browser, and they are served from your own site because the plugin loads no code from anywhere else. The plugin's own worker, vendor\/wasm-vips\/fpig-vips-worker.js, and everything else in the plugin are plain source.<\/p>\n\n Fonts: DSEG (SIL OFL 1.1) for the run timer and Fredoka (SIL OFL 1.1) for the wordmark, both under vendor\/ with their licenses.<\/p>\n\n\n No. Your files go from the browser to your own site, and the free plugin makes no request to any outside service; see External services. There is no account or key in the free plugin.<\/p><\/dd>\n Any browser with WebAssembly threads: Chrome, Edge, Brave, Safari 16.4 or later, and Firefox. On a browser without them, and on most iPads and iPhones, the page still uploads, with WordPress making the sizes on the server as usual.<\/p><\/dd>\n The image work happens in a browser engine that needs a fixed 1 GB of memory per worker. Desktop browsers grant it; iPadOS and iOS (Safari and Chrome alike, the same engine underneath) 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 run does not start: a notice says why, the header switches, and from then on that device works in fallback mode \u2014 the originals upload as they are and WordPress makes the sizes on the server, the way its own uploader does.<\/p>\n\n What you lose in fallback is every job only the engine can do: optimizing the original (auto rotate, remove metadata, resize), PNG to JPG, the AI Data Mining statement, the WebP and AVIF effort settings, and in Pro the watermark and overwriting in place. HEIC and other formats the engine decodes but your host's PHP cannot land as they are. And the speed win: the host resizes every image again, so the run costs it CPU and takes longer. Those options disable on the page with the reason beside them, so what you see is what will run.<\/p>\n\n Optimizer plugins such as Smush and EWWW tell WordPress 7.1 to turn its own browser-side processing off so that originals keep reaching them on the server. That does not put Flying Pigs in fallback: the page brings its own engine, its own isolation headers, and hides its uploads from those plugins. A site that really wants the server path can return false from the What you keep is everything the server can honour: the upload machinery itself (packed batches, chunked large files, retries, run recovery, and Pro's turbo lanes), the Sizes panel, JPG quality, WebP and AVIF companions with their quality and discard-if-larger settings (where the host's image library writes them), media folders, file and post dates, delivery and throttling. WebP only (Pro) works too, in two steps: the JPEG or PNG uploads, the server makes its WebP, and the base is dropped before the file reaches the library.<\/p><\/dd>\n Only if something serves them, and the Delivery panel makes sure something does. If a delivery plugin is already active, the panel names it and leaves it in charge; the sidecar names Flying Pigs writes are the ones those plugins serve. If nothing is serving them, \"Set up delivery for me\" tests your server and turns on a rewrite in the site .htaccess (Apache and LiteSpeed; the panel reports whether WebP, AVIF and the Vary: Accept header came back from the test) or, where the host will not honour one, wraps your images in a tag on the page. Both are reversible from the same panel. Pro's WebP only needs none of this: the uploads are WebP and are served as they are.<\/p><\/dd>\n Not on upload. Smush, EWWW, ShortPixel, reSmush.it and the host's bundled optimizers take their turn from WordPress's upload hooks, and Flying Pigs lifts them off for its own writes, so a file optimized in the browser lands once and stays as the browser made it. A bulk or background optimizer that scans the library later can still touch the files; leave those off for the pig's uploads or exclude the folder.<\/p><\/dd>\n It can say so, in the file. The Media panel's AI Data Mining option writes the IPTC \"Data Mining\" rights statement (IPTC Photo Metadata Standard 2023.1) as an XMP packet into every file the browser makes: the original when it is optimized, every size, every WebP and AVIF. Choose \"No AI training, allow search indexing\" (the default), \"No AI training, no search indexing\", \"Allow AI training\" or \"No statement\". With Remove metadata on it is the only metadata that travels (about 400 bytes); off, the original keeps its own metadata with the statement merged into its XMP packet, while sizes and companions carry the statement alone, as WordPress strips their metadata. It is a statement, not a lock: crawlers that read the standard honour it, and the rest do not. It is engine work, so fallback mode lands files without it. For a signal crawlers cannot miss, add robots.txt rules or an X-Robots-Tag header for your uploads folder as well.<\/p><\/dd>\n FileBird, Real Media Library, CatFolders, Mediamatic, Folders by Premio, Wicked Folders (once its media folders are switched on in its settings), HappyFiles, and any plugin that files media under a hierarchical taxonomy. Pick the folder in the run options, subfolders included, and every upload in the run lands in it. Media folders are virtual: they never change where the file sits on disk. That is the File date picker's job, in Pro.<\/p><\/dd>\nWhat Pro adds<\/h4>\n\n
\n
\n
Requirements<\/h3>\n\n
\n
External services<\/h3>\n\n
Source code<\/h3>\n\n
\n
Does anything leave my site?<\/h3><\/dt>\n
Which browsers work?<\/h3><\/dt>\n
What is fallback mode, and what do I lose in it?<\/h3><\/dt>\n
fpig_client_side_possible<\/code> filter.<\/p>\n\nDo visitors actually get the WebP and AVIF files?<\/h3><\/dt>\n
Will my optimizer plugin compress the uploads again?<\/h3><\/dt>\n
Can it tell AI crawlers to leave my photos alone?<\/h3><\/dt>\n
Does it work with my folder plugin?<\/h3><\/dt>\n
What is in Pro?<\/h3><\/dt>\n