{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiapa34o36zw5ubg2mjgjhd5okdbyzgovjghnlqkm3q3v57uqczgpa",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmhqszwgpp32"
  },
  "path": "/t/responses-api-gpt-5-ignores-the-detail-parameter-on-image-inputs/1344058?page=2#post_21",
  "publishedAt": "2026-05-22T19:41:03.000Z",
  "site": "https://community.openai.com",
  "textContent": "Your reproduction on gpt-5.4-mini should be informed by:\n\n_j:\n\n> GPT-5.2 uses “patches” algorithm for vision, not “tiles”. That type of vision input does not have a low detail.\n\n“patches” being the way forward. You’ll have to resize smaller on images in your control if you want to pay less for less seeing.\n\nYou also will not see the embarrassing inflation in vision costs for comparable resolutions with the patches algorithm, multiplied by model token cost multipliers for vision tokens, multiplied by tripling input token pricing, in the pricing page vision calculator - it stopped being updated at gpt-5.2.\n\nI will also note: `gpt-5.4-mini` is terrible. I tried to drop it into a gpt-5-mini app that rewrites a selection, following a prompt. gpt-5-mini follows the varying instruction, four paragraphs of output; gpt-5.4-mini is however basically non-functional with the same input, returning the app prompt or the original word back.",
  "title": "[Responses API] GPT 5 ignores the detail parameter on image inputs"
}