{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia7qvtzl52goeztptzokw6d5tqszdaqaioocb3ql3j7wqmyyrzgra",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mhclj23j2oy2"
  },
  "path": "/t/introducing-gpt-5-4-mini-and-nano-our-most-capable-small-models-yet/1377015#post_7",
  "publishedAt": "2026-03-18T01:24:11.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "hotnova.com",
    "OpenAI Vision Token Calculator"
  ],
  "textContent": "It seems just about every bit of documentation is wrong.\n\n  1. The models comparison page has **rounded values** for token pricing that are incorrect:\n\n### gpt-5.4-mini vs gpt-5-mini\n\n\n\nBad rounding:\n$0.075 → 0.08\n$0.025 → 0.03\n\n  2. The “patches” multiplier in documentation is all screwed up:\n\n\n\nWhat it should look like, given the currently realized costs:\n\n\n\n\n> Model | Multiplier\n> ---|---\n> `gpt-5.4-mini-2026-03-17` | `1.2x`\n> `gpt-5.4-nano-2026-03-17` | `1.2x`\n> `gpt-5.4-2026-03-05` | `1.2x`\n> `gpt-5.3-codex` | `1.2x`\n> `gpt-5.2-2025-12-11` | `1.2x`\n> `gpt-5-mini-2025-08-07` | `1.2x`\n> `gpt-5-nano-2025-08-07` | `1.5x`\n> `o4-mini-2025-04-16` | `1.72x`\n> `gpt-4.1-mini-2025-04-14` | `1.62x`\n> `gpt-4.1-nano-2025-04-14` | `2.46x`\n> `gpt-5.3-codex` | `1.2x`\n> `codex-mini-latest` | `1.72x`\n\n  3. The maximum vision input size of the new GPT-5.4-mini and nano models is wrong. You **can** send 1600x1600 and get billed for 50x50 patches = 2500 (haven’t tested “original”).\n\n\n\n  4. Chat Completions with gpt-5.4-mini and nano is resizing wrong or billing wrong (cheaper). Here is sending that 1600x1600px for 2500 patches/tokens:\n\n\n\n\nmodel | vision | mult | ChatC | Ccalculated | Responses | Rcalculated\n---|---|---|---|---|---|---\ngpt-5.4 | patch | 1.2 | 2813 | 2338 | 3008 | 2500\ngpt-5.4-mini | patch | 1.2 | 2813 | 2338 | 3008 | 2500\ngpt-5.4-nano | patch | 1.2 | 2813 | 2338 | 3008 | 2500\ngpt-5-mini | patch | 1.2 | 1834 | 1522 | 1833 | 1521\ngpt-5-nano | patch | 1.5 | 2290 | 1522 | 2289 | 1521\n\nThe amount of input “usage” received back per endpoint is the columns “ChatC” and “Responses”. Image consumption then by input difference due to inclusion of the image, and then reversing the apparent multiplier.\n\nIf it were downsized, like the original mini and nano:\n`1248 × 1248 px (39 × 39 patches) = 1521 tokens.`\n\nThis is not the only model disparity in billing between API endpoints. Here’s sending the image to others to where it should be downsized. Price should be the same between Chat Completions and Responses, but is not.\n\nmodel | vision | vision_mult | chat input | calculated | responses input | calculated\n---|---|---|---|---|---|---\ngpt-5.3-chat-latest | patch | 1.2 | 1667 | 1383 | 1833 | 1521\ngpt-5.3-codex | patch | 1.2 | - | - | 1833 | 1521\ngpt-5.2-chat-latest | patch | 1.2 | 1667 | 1383 | 1833 | 1521\n\nAnd I have even another way of sending the same image to Chat Completions - the same vision, cheaper price for me still on the “chat” model:\n\nmodel | vision | vision_mult | chat input | calculated | r | rerror\n---|---|---|---|---|---|---\ngpt-5.4 | patch | 1.2 | 2813 | 2338 | E400 | E400\ngpt-5.3-chat-latest | patch | 1.2 | 1548 | 1284 | E400 | E400\n\n* * *\n\n## Vision price inflation\n\nUltimately, when I integrate what the API is currently costing into my own calculator, - the same image, downsized manually to the old “high” resolution (which doesn’t happen as documented), vision still costs **3x** on mini and **3.2x** on nano new models.\n\n\n\nUpdated models:\n\nhotnova.com\n\n### OpenAI Vision Token Calculator",
  "title": "Introducing GPT-5.4 mini and nano — our most capable small models yet"
}