WunderPaint Pro<\/a> takes those same designs and runs them at scale, in the background and on your website: featured images generated across whole archives from one template (with per-category templates and generate-on-publish), WooCommerce catalog and product gallery graphics, image series from a CSV file, batch processing of your existing library (optimize, resize, watermark, apply recorded actions), dynamic images on the front end through blocks, shortcodes and native Elementor widgets that re-bake on a schedule, on shop events or via webhook, live badges, personalized per-visitor images, an AI content generator that drafts complete posts with matching graphics and SEO fields, multiple brand kits, one-click extension installs including all premium studios, and scheduled backups to S3-compatible storage.<\/p>\n\nRequirements<\/h4>\n\n
A current desktop browser (Chrome, Edge, Firefox or Safari); the editor runs inside the WordPress admin and shows a notice on phones. Works with Gutenberg, Elementor, Bricks, Divi and any plugin that uses the media picker. The interface, the built-in handbook, the guided tours and the help assistant are available in English, German, Spanish, French, Portuguese, Italian and Dutch.<\/p>\n\n
External Services<\/h3>\n\n
This plugin can talk to a number of external services, each only when you use the feature it belongs to, and a service that needs an API key stays silent until you enter that key. There is no analytics, no tracking and no telemetry of its own, and it never sends your content anywhere by itself.<\/p>\n\n
The complete list, with the exact data each service receives and when, is in the FAQ below: \"Which external services does this plugin use?\"<\/strong> The same list, in more detail, is at https:\/\/help.wp-image-editor.com\/#services<\/p>\n\nBundled Libraries<\/h3>\n\n
WunderPaint is licensed GPL-2.0-or-later (see license.txt). Every bundled component is under a GPL-compatible license; full attributions are in third-party-licenses.txt.<\/p>\n\n
The complete list, with the license of each component, is in the FAQ below: \"Which third-party libraries are bundled?\"<\/strong><\/p>\n\nDevelopment<\/h3>\n\n
The free plugin is open source (GPL-2.0-or-later). The human-readable source\nof everything it ships - the editor bundle, the bundled studios and the\ntranslations - is published at https:\/\/github.com\/tbitdesign\/WunderPaint.\nBUILD.md there lists every generated file next to its source and the command\nthat produces it; the FAQ entry \"Where is the source code of the compiled\nfiles?\" is the short version.<\/p>\n\n\n
\nDo I need to be a designer?<\/h3><\/dt>\nNo. You start from templates and drag things into place, and it already looks designed. The depth is there when you want it, not before.<\/p><\/dd>\n
Where do my images go?<\/h3><\/dt>\nThey stay in your media library. The editor runs on your own server and the local tools work inside your browser, so nothing is uploaded for them. Cloud AI only runs when you trigger it, with your own key; the full list of services any feature can reach is under External Services below.<\/p><\/dd>\n
Do I need AI API keys?<\/h3><\/dt>\nNo. The whole editor works without one, including background removal, subject selection, depth blur, face blurring, upscaling and semantic search. A key (Settings, WunderPaint) additionally enables text-to-image generation, prompt-based editing, inpainting and outpainting, panorama generation and AI-written alt text.<\/p>\n\n
If you run WordPress 7.0 or newer and have set up a provider in WordPress itself, the plugin uses that one for text and for plain image generation when you have entered no key of your own. Your own key always wins where you set one, because it also carries the model choice per feature and the spend counter.<\/p><\/dd>\n
What runs locally and what needs a key?<\/h3><\/dt>\nBackground removal works out of the box: its model ships with the plugin. Smart select, depth estimation, image captioning, text importance and semantic search download their model once, through your own server, and run in your browser from then on; the in-browser runtime is configured never to fetch models remotely. Enlarging an image is plain high-quality resampling in a worker, so it needs neither a model nor a key. Everything that invents new pixels or writes text for you goes to the provider whose key you entered, and only when you ask for it.<\/p><\/dd>\n
Which layers can carry data?<\/h3><\/dt>\nText, image and raster layers, plus QR codes, charts and tables, and Smart Objects whose embedded layers are bound. Shapes, gradients, groups and adjustment layers do not take a binding, and patterns do not either.<\/p><\/dd>\n
Where are my API keys stored?<\/h3><\/dt>\nObfuscated in the WordPress database, or preferably as constants in wp-config.php (WPIE_GEMINI_KEY, WPIE_OPENAI_KEY, WPIE_ANTHROPIC_KEY, WPIE_PEXELS_KEY, WPIE_PIXABAY_KEY, WPIE_UNSPLASH_KEY, WPIE_MESHY_KEY). They are only ever read server-side and never sent to the browser.<\/p><\/dd>\n
Does it work with my page builder?<\/h3><\/dt>\nGutenberg, Elementor, Bricks, Divi and any media picker: every image gets an Edit Image button that opens the full editor over your layout and drops the result straight back.<\/p><\/dd>\n
Can I open Photoshop files?<\/h3><\/dt>\nYes. PSD files open as layered, editable documents (including Smart Objects), and you can export your work back to PSD. Round-tripping keeps the layer structure as far as the two formats allow.<\/p><\/dd>\n
Will it slow my site down?<\/h3><\/dt>\nNo. The editor only loads in wp-admin when you open it. Your visitors just receive normal, optimized images.<\/p><\/dd>\n
What if I deactivate the plugin one day?<\/h3><\/dt>\nNothing dramatic. Exported images are ordinary files in your Media Library and stay exactly where they are. Folders and tags are stored as regular WordPress taxonomies. Your layered projects wait in the uploads folder for the day you come back.<\/p><\/dd>\n
Is it available in my language?<\/h3><\/dt>\nEnglish is built in. Other languages come from translate.wordpress.org as WordPress language packs and install themselves once your locale has been translated.<\/p><\/dd>\n
What are the system requirements?<\/h3><\/dt>\nA current desktop browser: Chrome or Edge 110+, Firefox 115+, Safari 16.4+. Some 3D extension studios additionally need WebGL2 with hardware graphics, which every current desktop browser on a normal machine provides; Help, System Status shows exactly what your device offers.<\/p><\/dd>\n
Where do I get help?<\/h3><\/dt>\nThe handbook lives right inside the editor (press ?), the built-in help assistant answers questions and builds little guided tours, and https:\/\/help.wp-image-editor.com covers every feature down to the single control.<\/p><\/dd>\n
Where is the source code of the compiled files?<\/h3><\/dt>\nAll of it is public, at https:\/\/github.com\/tbitdesign\/WunderPaint - the readable original of every generated file this plugin ships. Node.js 20 and npm are the only things needed to rebuild them.<\/p>\n\n
\n- build\/.js and build\/<\/em>.css are webpack output, built from src\/ with \"npm ci && npm run build\". The files named after a library (build\/agpsd..js, build\/jszip..js and so on) are those npm dependencies, bundled by the same run; each one is listed with its own source link under \"Which third-party libraries are bundled?\" below.<\/li>\n
- bundled-extensions\/\/extension.js is esbuild output, built from extensions\/\/src\/ with \"npm ci && npm run build\" inside that studio's folder; \"bash tools\/bundle-free-extensions.sh\" then collects the built studios into bundled-extensions\/ (it does not build them itself and stops when one is missing).<\/li>\n
- Translations are not part of the download: wordpress.org delivers them as language packs from translate.wordpress.org. Their sources (tools\/.py, languages\/*.po) stay in the repository.<\/li>\n
- build\/vtracer..wasm is not compiled during that build and is not ours: webpack copies it out of the npm package vtracer-wasm (MIT), a WebAssembly build of VTracer (https:\/\/github.com\/visioncortex\/vtracer, MIT). It is the vectorizer behind the editor's Vectorize command, which turns a bitmap into paths in the browser.<\/li>\n
- build\/ort.wasm.min..mjs is copied from npm in the same way: the CPU build of onnxruntime-web (MIT, https:\/\/github.com\/microsoft\/onnxruntime), which carries the local AI features.<\/li>\n<\/ul>\n\n
BUILD.md in that repository lists every generated file next to its source and the exact command that produces it.<\/p><\/dd>\n
Which third-party libraries are bundled?<\/h3><\/dt>\nEach library below is bundled into its own file under build\/, named after the library, so a file there can be traced back to its source at a glance. Full attributions and copyright notices are in third-party-licenses.txt.<\/p>\n\n