Skip to content

Black Friday 50% off your first year on all premium plugins and the Suite.

See the deals

Fix AI alt text problems

ByteKeel PixTag Pro AI alt text not working? Fixes for API key errors, rate limits, timeouts, local sites and alt text that comes from the file name.

2 min read · Updated 6 November 2026

Alt text comes from the file name, not the AI

When an AI request fails, ByteKeel PixTag Pro falls back to the file name so the image still gets alt text. The Dashboard’s Recent Activity then shows the method ai_fallback_filename. Run Preview (5 Images) on the Bulk Processor with the AI method to see the actual error message, then use the list below.

Error messages

  • OpenAI API key not configured / Claude API key not configured — the key for the selected provider is empty. Check AI Provider matches the key you entered.
  • Invalid OpenAI API key / Invalid Claude API key — the key was revoked or mistyped. Create a new one.
  • Rate limit exceeded. Please try again later. — your provider account hit its per-minute limit or has no credit. Lower Batch Size, add credit, or wait.
  • Access forbidden. Please check your Claude API permissions. — the key’s workspace cannot use that model.
  • Invalid request to Claude API or Claude API error — often a model your account cannot use. Anthropic retires older models over time; pick another Claude model, or switch to OpenAI.
  • Request error: … timed out — raise Processing Timeout on the Advanced tab (60 seconds is plenty).
  • Image content blocked by OpenAI safety filters — the picture was refused; ByteKeel PixTag Pro uses the file name for it.
  • Could not encode image for Claude API — your server could not download its own image (see below).

Works on the live site but not on a local or staging site

For OpenAI, ByteKeel PixTag Pro sends the image’s web address, and OpenAI downloads it. A site on localhost, a .test/.local domain, behind a password, or behind a “coming soon” plugin that blocks visitors cannot be reached, so the request fails. Use Claude there (your server sends the file itself), or test on a public site.

For Claude, your server downloads its own image first. If your host blocks requests from the site to itself (loopback requests) or the file is protected, you get “Could not encode image”. Tools › Site Health reports loopback problems.

Warning: “an API key is required”

ByteKeel PixTag Pro shows this on its screens when the default method is AI-powered and the selected provider has no key. The warning names the provider you chose (OpenAI or Claude). Add that provider’s key on Settings › Generation Rules, or switch the provider to the one whose key you saved.

The connection test passes but generation fails

For OpenAI the test always uses GPT-4o Mini, not necessarily the model you picked; choose GPT-4o Mini and try again, and if that works your account cannot use the other model. For Claude the test uses the model you saved, so a passing test means the key and model work: check the image itself (size, format, and whether your site can read the file) and the activity log message.

Generating again gives the same text

AI results are cached for an hour per image and prompt. Change the prompt, wait an hour, or (temporarily) turn on Debug Mode to get a fresh answer.

Did this answer the question? No — open a support request