gpt-4-vision-preview — Retired
- Deprecated
- —
- Shutdown
- 2024-12-06
- Status
- deprecated
- Replacement
- gpt-4o
Quick fix — copy & paste
Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.
# OpenAI: gpt-4-vision-preview (deprecated)
model = "gpt-4-vision-preview" # Replacement
model = "gpt-4o" // OpenAI: gpt-4-vision-preview (deprecated)
const model = "gpt-4-vision-preview"; // Replacement
const model = "gpt-4o"; "model": "gpt-4-vision-preview" "model": "gpt-4o" This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official OpenAI migration guide.
Error messages
Seeing one of these? You're in the right place.
-
model_not_found: gpt-4-vision-preview -
The model `gpt-4-vision-preview` has been deprecated -
The model `gpt-4-vision-preview` does not exist or you do not have access to it
Replacement options
-
gpt-4oCompare token cost →
Other OpenAI deprecations
What this means for your code
gpt-4-vision-preview is a multimodal model that accepts image inputs alongside text. Image input pricing differs across providers and is computed per image tile, not per token. Replacements may have different max image size, supported formats, or detail level enums.
gpt-4-vision-preview was retired by OpenAI on 2024-12-06. API calls now return an error and the model is no longer accessible. New code should use gpt-4o; legacy code that still references this model id needs to be updated immediately.
Find every call in your codebase
Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:
Python projects
grep -rn '"gpt-4-vision-preview"' --include="*.py" . JavaScript / TypeScript projects
grep -rn '"gpt-4-vision-preview"' --include="*.{js,ts,tsx,jsx}" . Anywhere (configs, scripts, infra)
grep -rn "gpt-4-vision-preview" . Migration checklist
Steps in order. Skip any that don't apply, but read the whole list — for vision models, the non-obvious steps are usually the ones that break in production.
- 1. Update the model id in API calls
- 2. Verify supported image formats (PNG, JPEG, WebP, GIF) match the new model
- 3. Check max image dimensions and detail level settings
- 4. Recompute image-input costs using the new model's tile pricing
- 5. Test with your largest and smallest typical image inputs
Will this migration cost more?
Switching from gpt-4-vision-preview to gpt-4o could change your costs significantly. Calculate the exact difference for your prompts.
Open the cost calculator →