Compare
Gpt 35 Turbo 16k vs Gpt 35 Turbo 16k 0613
This page is context-first: how much text each model can take in one request. Full specs adds capabilities and limits; the pricing matrix below is only about $/million tokens from hosts that list both models.
Context window · side by side
Bar length is relative to the larger of the two windows (100% = max of this pair). This is not pricing.
Same context window size for both models.
Gpt 35 Turbo 16k and Gpt 35 Turbo 16k 0613 have identical context windows (16K tokens). Gpt 35 Turbo 16k 0613 is 0% cheaper on input.
Full specs
Context, output, capabilities, and dates. Green highlights the favorable value where we compute a winner.
| Spec | Gpt 35 Turbo 16k | Gpt 35 Turbo 16k 0613 |
|---|---|---|
| Context window | 16,385 tokens (16K) | 16,385 tokens (16K) |
| Max output tokens | 4,096 tokens (4K) | 4,096 tokens (4K) |
| Speed tier | Balanced | Balanced |
| Vision | No | No |
| Function calling | No | Yes |
| Extended thinking | No | No |
| Prompt caching | No | No |
| Batch API | No | No |
| Release date | N/A | N/A |
Pricing matrix
Dollar rates only: hosts that list both models, per 1M tokens. For how much text fits, use the context section above — not this table.
| Provider | Gpt 35 Turbo 16k in | Gpt 35 Turbo 16k out | Gpt 35 Turbo 16k 0613 in | Gpt 35 Turbo 16k 0613 out |
|---|---|---|---|---|
| Azure | $3.00/M | $4.00/M | $3.00/M | $4.00/M |
Frequently asked questions
Powered by Mem0
Use a smaller model.
Get better results.
Mem0 gives your AI long-term memory so you stop re-sending context on every call. That means you can use a smaller, faster, cheaper model — and still get better answers.
Example: a multi-turn chat session
80% less to send — works with any model