# GPT-4o-mini Vision API: High Prompt Token Usage in Batch Process

**URL:** <https://community.openai.com/t/gpt-4o-mini-vision-api-high-prompt-token-usage-in-batch-process/1149227>\
**Category:** Feedback\
**Created:** [March 22, 2025, 2:58am UTC](https://community.openai.com/t/gpt-4o-mini-vision-api-high-prompt-token-usage-in-batch-process/1149227 "2025-03-22T02:58:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [March 22, 2025, 5:17am UTC](https://community.openai.com/t/gpt-4o-mini-vision-api-high-prompt-token-usage-in-batch-process/1149227/2 "2025-03-22T05:17:09Z")

</div>

- Don’t use `gpt-4o-mini` for images.

It costs twice as much per image as `gpt-4o` - in dollars.

Intentionally.

This is done by multiplying the bill for image input tokens by 33.33x

The bug was a period of _not_ inflating the token bill.

✅Solved

---

_[View the full topic](https://community.openai.com/t/gpt-4o-mini-vision-api-high-prompt-token-usage-in-batch-process/1149227)._