Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.fluximage.io/llms.txt

Use this file to discover all available pages before exploring further.

If something isn’t working as expected, the sections below cover the most common errors and how to resolve them. Errors are grouped by category so you can jump straight to what you’re seeing.

​
Upload & compression errors

Fluximage processes up to 20 images per batch. If you select more than 20 files at once, the entire batch is rejected before processing begins.To fix this: Split your files into groups of 20 or fewer and submit each group separately. All other batch settings — format, quality, AI options — carry over between batches.
Each file in a batch must be 20 MB or smaller. If any single file exceeds this limit, the request is rejected for the whole batch.To fix this: Reduce the file size before uploading. Options include:
  • Re-export the image from your editing software at a lower resolution or quality
  • Resize the image dimensions so the file falls under 20 MB
  • Use a local tool to do a first-pass compression before uploading to Fluximage
Processing time scales with file size and batch count. A full batch of 20 large files can take up to 60 seconds — this is expected behavior.What to do: Leave the tab open and wait. The progress indicator will update when each image finishes. If the page appears stuck for more than 90 seconds, refresh and re-submit the batch.
Converting to WebP (the default format) tends to be faster than AVIF for large batches.

​
AI feature errors

Smart alt text and SEO filename rename are not available on the Free plan. If you check either AI option and are on a Free account, the batch fails with this error.To fix this: Upgrade to Starter or higher. Once upgraded, AI credits are included with your plan each month.
Each AI operation (alt text, SEO rename, or both together) consumes one AI credit per image. When your monthly credits and any top-up credits are both exhausted, AI features are blocked until credits are available again.To fix this: You have two options:
  • Purchase a top-up — available in packs of 200, 1,000, or 5,000 credits from your plan page. Top-up credits never expire.
  • Wait for your monthly reset — credits reset on the same calendar date your billing period started. Check your plan page for the exact reset date.
Running out of AI credits does not affect standard image compression. You can keep compressing without AI until your credits are restored.
If your images came back without alt text or with their original filenames, the AI step may have been skipped.Check the following:
  1. Confirm the checkbox is enabled — the Generate smart alt text and Auto-rename files for SEO options must each be checked before you click Compress. They are off by default.
  2. Confirm you are on a paid plan — AI features require Starter or higher. Free plan users will see an error if either option is checked.
  3. Check your AI credit balance — if credits ran out mid-batch, some images may have been processed without AI. Visit your plan page to see your remaining balance.

​
Account & billing

Free accounts include 20 compressions per month. Once this limit is reached, further compression attempts return a 403 error until your credits reset or you upgrade.To fix this: Upgrade to Starter (200 compressions/month), Pro (unlimited), or Agency (unlimited). Changes take effect immediately after checkout.
Credits reset on the same day of the month that your billing period started — not on the 1st of every calendar month. For example, if you subscribed on the 15th, your credits reset on the 15th of each month.To check your reset date: Go to your plan page. The next reset date is displayed next to your current usage.
If your reset date falls on a day that doesn’t exist in the current month (for example, the 31st in February), the reset rolls to the last day of that month.
If your API key returns an authentication error, check the following:
  1. Verify the key format — valid keys start with flx_live_. If yours does not match this pattern, you may have copied an incorrect value.
  2. Check whether the key was rolled — generating a new API key immediately invalidates the previous one. If someone on your team rolled the key, you need to use the new value.
  3. Confirm the header format — the key must be sent in the Authorization: Bearer <your-key> header. A missing Bearer prefix will cause a 401.
  4. Check your plan — API access is available on the Agency plan only. Keys generated on lower-tier plans will not authenticate against the API.