How to Use GPT-5 for Everyday Work in 2026

GPT-5 is OpenAI’s 2026 flagship model, and for most people the hard part is not access — it is picking the right reasoning tier and context budget without burning money. You can get a genuinely useful setup running in about ten minutes.

Short answer: use GPT-5 in the ChatGPT app or via the API, set reasoning effort to medium for daily work, and keep individual prompts under roughly 50K tokens unless you actually need the full window.

What is GPT-5 and what changed?

GPT-5 is a multimodal large language model from OpenAI that accepts text, images, and audio input and returns text. It ships with a 400,000-token context window and roughly 128K tokens of maximum output, which is a real jump over GPT-4o’s 128K context.

The feature that matters most day to day is reasoning effort. You choose between low, medium, and high. Low answers fast and cheap. High spends 30 seconds to two minutes thinking before it writes anything.

Pricing on the API sits at $1.25 per million input tokens and $10 per million output tokens for the base tier. ChatGPT Plus is $20 a month and includes GPT-5 usage caps that reset every three hours.

How do you get started with GPT-5?

1. Sign in at chatgpt.com or openAI’s API dashboard, or download the desktop app for macOS and Windows.
2. In the model picker, choose GPT-5. The mobile app hides it behind the model dropdown at the top of the chat.
3. For API work, create a key under API keys and copy it once — OpenAI never shows it again.
4. Install the SDK: pip install openai and set export OPENAI_API_KEY=sk-....

Your first call looks like this:

from openai import OpenAI
client = OpenAI()
resp = client.chat.completions.create(
    model="gpt-5",
    reasoning_effort="medium",
    messages=[{"role": "user", "content": "Summarize this contract"}]
)

Which reasoning tier should you actually pick?

Medium is the right default for 80% of tasks. Low is for classification, extraction, and formatting where the answer is obvious. High is worth the wait only for multi-step math, debugging tricky code, or long-form planning.

Tier	Typical latency	Best for
Low	1-3 seconds	Tagging, rewriting, routing
Medium	3-15 seconds	Drafting, analysis, code
High	30-120 seconds	Math proofs, hard debugging

High effort can triple your output token bill. If you are prototyping, start at low and only move up when the output is genuinely wrong, not when it is merely terse.

Is the 400K context window worth using?

Sometimes — but it is a trap more often than people admit. Cost scales linearly with input tokens, so pasting a 300K-token codebase costs around $0.38 per call at input pricing, and quality drops in the middle of very long contexts.

Better approach: use retrieval. Split documents into chunks, embed them, and send only the five to ten most relevant chunks. You get faster responses and a smaller bill for the same result.

What does GPT-5 still get wrong?

It still fabricates citations if you ask for sources without web search enabled. It also over-explains when reasoning effort is high — you get the full chain of thought as visible output, which is verbose for a chat UI.

GPT-5 is a poor fit if you need guaranteed deterministic output. Any workflow requiring bit-for-bit reproducible answers should not route through an LLM at all.

Who should use it: developers writing code, analysts summarizing documents, and writers who need a first draft. Who should skip it: anyone whose task is a single lookup — a search engine is faster and free.

Quick Summary

• GPT-5 has a 400K-token context window and three reasoning tiers: low, medium, high.
• Use medium effort as your default; reserve high for hard math and debugging.
• API pricing is $1.25 per million input tokens and $10 per million output tokens.
• Retrieval beats pasting huge contexts — it is cheaper and more accurate.
• Verify any factual claim GPT-5 makes without web search, because it can still hallucinate sources.