Aimogen ProDocumentation
Product page Support

Image problems

Fixing missing, broken, irrelevant or oversized images in Aimogen Pro generated content.

Images disappear after a few hours#

Symptoms#

Images appeared when the post was created, then broke.

Cause#

Almost always this one. AI providers serve generated images from short-lived URLs. With image copying disabled, your posts hotlink those URLs and they expire.

Resolution#

Settings › AI Images › Copy Royalty Free / AI Images From Post Content — set it to on for the Media Library, or to an S3 destination.

Existing broken posts need regenerating; the original URLs are gone.

Work through:

  1. Auto Set A Featured Image For Posts is off on the rule.
  2. The chosen source has no credentials. Check the provider key.
  3. Generation failed. Check System & Logs › Activity Logs.
  4. Royalty-free search found nothing. Enable broad search, or improve keyword extraction.
  5. The post was skipped. With Do Not Skip Importing The Article If No Royalty Free Image Found off, the whole post is skipped when no image is found — so the symptom is a missing post, not a missing image.

Images are irrelevant#

For royalty-free sources, the search query is the problem:

Settings › Royalty Free Images › Improve Royalty Free Featured Image Precision Using This Service — set it to an AI model or TextRazor rather than disabled.

The default extraction prompt combines the specific keyword with the article niche, so an article about dogs with a heading about food yields "dog food" rather than "food". That behaviour is the difference between relevant images and unrelated stock photos.

For AI-generated images, the prompt is the problem. See Image generation.

Every image looks the same#

One prompt line, or one search query. Add several prompt lines — one is selected per run — or enable Random Results Order and widen the image pool for royalty-free sources.

Since 2.8.8, each royalty-free image is used only once per created post, so within one article they should already differ.

Images are enormous#

Set Settings › AI Images › AI Generated Image Resize Width and Resize Quality.

A 1024×1024 PNG from an image model is often several megabytes. Resizing applies only when images are copied locally.

Text in images is garbled#

Expected from most image models. Either exclude text from the prompt ("no text, no words, no logos"), or use Ideogram, which is specifically good at rendering text.

429 errors during bulk runs#

Image endpoints rate-limit far more aggressively than text endpoints. Raise Delay Between API Requests For AI Image Generator APIs (ms).

The prompt was rejected#

Every provider applies content policy to image prompts. Rephrase. People, brands, public figures and anything violent or adult are the usual triggers.

Images upload but 404 when displayed#

Only with S3-compatible storage. The bucket or the objects are not publicly readable.

For Cloudflare R2, check the cloud_public setting. For S3, check the bucket policy.

Generation is very slow#

Midjourney via GoAPI is asynchronous and slow by design — tens of seconds.

Large sizes and high step counts on Stability.AI cost time as well as money.

If a request times out, raise PHP max_execution_time.

Media Library AI panels are missing#

Advanced Tools › More Features › Media Library Extensions is off, or No Media Library is set under Settings › General Settings.

The edit and upscale panels specifically require a Stability.AI key.

Alt text is generic#

The model is not vision-capable, so it is guessing from the filename and surrounding content. Use a vision model. See Media Library tools.

Costs more than expected#

Images cost far more per unit than text.

  • One featured image per post, not one per heading
  • Royalty-free sources are free
  • Cloudflare Workers have no per-image cost
  • Raise the image request delay so you do not pay for retried requests

See Controlling cost.

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.