GPT-3.5 Turbo is a chat-oriented language model from OpenAI, positioned as an older, lower-cost tier in the company's GPT lineup for general text and conversational tasks.
| Provider | Input / 1M | Output / 1M |
|---|---|---|
| $0.250 | $0.750 | |
| $0.500 | $1.50 | |
| $1.50 | $2.00 |
Prices updated daily. Last check: Sep 20, 2026
Input, output, and batch rates, plus alternatives, for one provider at a time.
Benchmarks measured Sep 2026. Scores are independent evaluations, not vendor-reported.
GPT-3.5 Turbo fits high-volume, cost-sensitive text workloads where the task is narrow and well-defined: intent classification, sentiment and topic tagging, short summarization, data cleanup and reformatting, template-driven copy, FAQ-style chat responses, and synthetic data generation for evaluation sets. It is also commonly retained in legacy production systems whose prompts and guardrails were tuned specifically against it, where swapping models would require re-validation. It is a weaker choice for agentic pipelines, difficult coding tasks, math-heavy reasoning, or long-document analysis; those workloads generally point toward the GPT-4o generation or a dedicated reasoning model.
Costs depend on which provider serves the model, whether you are billed for input or output tokens, and whether you use batch, cached, or fine-tuned variants. Because those rates change frequently, see the pricing table on this page for current per-provider numbers rather than relying on figures quoted elsewhere.
Narrow, high-throughput text tasks — classification, tagging, extraction, short summaries, format conversion, and simple conversational replies. It is a reasonable default when the prompt is tightly specified and volume matters more than reasoning depth.
For new projects, most teams compare it against the compact tiers of OpenAI's GPT-4o generation, which generally handle reasoning, instruction following, and code better. GPT-3.5 Turbo remains relevant mainly for legacy deployments already tuned to it, or where a specific pinned snapshot is required for reproducibility.
We do not track confirmed image-input support for this model. Vision capability arrived in OpenAI's later GPT-4 class models, so if your workload requires image understanding, verify modality support on your provider's model card before building against GPT-3.5 Turbo.
Our database does not carry a confirmed context length for this entry. GPT-3.5 Turbo has shipped in several dated snapshots with different context limits, so check the specific revision your provider serves before designing long-prompt workflows.