FAQ

Both, if you want Pro features. The free plugin is the foundation — it has to be active. Pro is a separate add-on plugin that loads on top of free, layering in the bulk runner, real-time upload optimization, Caption / Description fields, flagship AI models, and CPT / WooCommerce support. See Installation for activation order.

On WordPress 6.1 through 6.x, yes — add a key for one provider on the API Keys page. On WordPress 7.0 and later there is a second option: set Connection method to WordPress AI (Connectors) and core answers the request through a connector you configured under Settings → Connectors, with no plugin API key involved. Existing key setups keep working untouched, and keys you already saved are kept for switching back. See AI Connectors.

One image is one AI call on the free plugin, and three with a Pro license, which also writes the caption and the description. Cost scales with tokens rather than with a fixed per-image price. The plugin estimates spend from blended per-million-token pricing: Claude 4.5 Haiku $2.00, Gemini 3.1 Flash-Lite $0.56 (the default model), GPT-4.1 mini $0.70. Pro-tier models cost more per million: Claude 4.5 Sonnet $9.00, Gemini 3.1 Pro $2.50, GPT-5 mini $1.20. The API Usage dashboard shows the running estimate per model; your provider invoice is the real number.

Any of the three works, and you can save keys for all three and switch by picking a different model — there’s no separate provider switch. Anthropic’s Claude 4.5 Haiku is the priciest of the cheap tier at $2.00 per 1M tokens blended. Google’s Gemini 3.1 Flash-Lite is the cheapest at $0.56 and the default in a fresh install. OpenAI’s GPT-4.1 mini sits between them at $0.70, which suits sites already holding an OpenAI Platform account.

For straightforward product photography and blog hero images, no — the cheap models are fine. Pay the premium when output quality matters more than per-call cost: complex multi-subject photography, brand-sensitive copy, or rarely used locales where the cheap-tier models drift back to English. Pro adds Claude 4.5 Sonnet, Gemini 3.1 Pro and GPT-5 mini; see Pro AI Models for details.

No. Images are sent directly from your WordPress server to the AI provider you’ve configured (Anthropic, Google or OpenAI) — never to InfyPress. The only call to infypress.com is for Pro license validation, and it sends only your license key, no content.

Keys are encrypted with AES-256-GCM before they reach the infyp_api_keys option, under a key derived from your site’s AUTH_KEY and SECURE_AUTH_KEY. Anyone with database-only access — a leaked SQL dump, say — can’t read them without also having your wp-config.php. Two consequences: rotating those salts means re-entering your keys, and a server without the PHP OpenSSL extension can’t save a key at all.

Your license is tied to one site at a time. To move it to another site, deactivate it on the current site (License page → Deactivate) and then activate the same key on the new site. See License Activation.

The plugin itself doesn’t collect or transmit personal data — it sends image files to AI providers for processing only. Your obligations under GDPR depend on what the images contain and on your AI provider’s policies (each provider publishes its own data-handling terms). Configure providers whose policies you accept; the plugin doesn’t get in the way.

Six builders are handled out of the box: Gutenberg, Elementor, WPBakery, Visual Composer, Uncode, and Divi. When you rename an image, references in all six are rewritten automatically. Divi arrived in 1.0.4 and goes further than a shortcode swap — it covers et_pb_* layouts, custom CSS stored in post meta, Divi Library and Theme Builder templates, and it clears Divi’s static CSS cache afterwards. Other builders aren’t broken; they just don’t get the auto-rewrite step, so the 301 redirect covers the gap until you update them by hand. See Renaming Files & 301 Redirects.

The free plugin scans post and page only. Pro automatically includes every public custom post type — no toggle needed. See Custom Post Types & WooCommerce.

Yes — WooCommerce is a first-class citizen with Pro. Product featured images, product gallery images, and product-category thumbnails are all included in the image table. Pro also injects product context (name, description, categories) into the AI prompt so the alt text reflects what the product actually is, not just what it looks like.

The plugin operates on attachment-level metadata, which sits below the translation layer — so it generally plays nicely with multilingual setups. Each language version of a post can reference the same optimized image, and the AI’s output language is set independently in AI Settings. If your translation plugin duplicates attachments per language, each duplicate is optimized independently.

Yes — install and configure per site as normal. Each site has its own API keys, settings, and (for Pro) license activation. There’s no network-wide settings panel; multisite is treated as a collection of independent installs from the plugin’s perspective.

WordPress 6.1 and PHP 8.0 are the minimums, both taken from the plugin headers and checked at activation. Pro requires WordPress 6.5 plus the free plugin active under it. There’s no separate database requirement — the plugin’s tables are created through dbDelta on whatever database your WordPress install already uses. Full details on System Requirements.

No — the free plugin runs one image at a time, click by click, and since 1.0.6 also one image per REST request. Bulk is a Pro feature: the in-browser runner with progress bar and pause/resume, plus server-side jobs that keep going after you close the tab. See Bulk Optimization (free) for the row-by-row workflow and Bulk Optimization (Pro) for what Pro adds.

Not for site visitors or search engines — every rename auto-creates a 301 redirect from the old URL to the new one, and references inside your posts and supported page builders are rewritten in place. The 301 catches anything outside that (external links, bookmarks, indexed pages). Hand-written theme code and third-party caches (CDN, server cache) won’t auto-update — see the Image Usage modal to check first if you’re unsure.

Click the score badge in the row to open the SEO Breakdown modal — it lists every component contributing to the score and which criteria still need to change to hit 100. Typically it’s a missing keyword, a too-short alt text, or a filename that wasn’t renamed off the camera default.

Open the relevant field’s modal on the row and edit it back by hand — the Change History shows the Before value so you can copy it. The Change History itself is a read-only record: it shows what changed and when, and it has no restore button.

Open wp-admin/admin.php?page=ai-image-seo-optimizer-wizard directly. The wizard renders for any user with manage_options whether or not it has been completed before — the infyp_wizard_completed option only suppresses the automatic redirect after activation and the reminder notice. There’s no menu item for it, since the page is registered hidden. Your saved keys and preferences are pre-filled, and leaving a key field empty on the API Keys step leaves the stored key alone. See Setup Wizard.

Both, with different tiers. The free plugin exposes the infyp/v1 REST namespace since 1.0.6 — images, per-field optimization, settings and scoring — authenticated with Application Passwords for scripts or cookie plus nonce in the browser, capped at 100 optimization calls per user per hour. Pro 1.0.1 adds server-side jobs at /jobs and the wp infyp WP-CLI commands, both license-gated. See the REST API reference and the WP-CLI commands.