The links in this guide were checked October 24, 2026. Use the documentation's own navigation and search if a saved page has moved. Feature conditions belong to the specific page, platform, and account described there.
Match the question to a documentation set
| Your question | Start here | What to look for |
|---|---|---|
| How do I use ChatGPT in a browser? | ChatGPT on the web | Product instructions for working in the browser. |
| How should I ask for a useful result? | Prompting | Context, desired output, and boundaries for the task. |
| Which key opens a desktop command? | Commands | Your operating system and the relevant view or feature. |
| How do I build a program that sends requests? | API docs | Developer guides, request concepts, and API reference. |
ChatGPT Learn also includes Work and Codex material. Read the page's product labels rather than assuming every command or tool applies to an ordinary browser conversation. In the command reference, for example, some actions are explicitly marked Codex only or depend on an available feature.
Follow one question through the right guide
Imagine that you have a spreadsheet and want help explaining a discrepancy. You plan to work inside ChatGPT, with no application code. Start with the browser product guide and follow its instructions for working with your material. Check the relevant feature's conditions before relying on a file or tool option.
An API page showing a request body answers a different question: how a program interacts with the API. Copying that request into the ChatGPT message box does not configure a developer integration. Likewise, a product instruction to attach a file does not explain how your own program should upload one through an API.
For the practical file-preparation task, the ChatGPT file-upload guide explains how to give the assistant a bounded question and check its answer against the supplied material. Return to the official feature page for current product conditions.
Read the condition around the instruction
Before following a step, check four details: which product it concerns, which platform it describes, what access or feature conditions it states, and what result the step promises. A paragraph about desktop shortcuts should not become a claim about your phone.
If a command is missing, keep the exact page link and heading beside your app version and a description of what you see. That makes a useful support question:
I am using [product] on [platform/app version].
Official page and section: [LINK AND HEADING]
I expected to find: [CONTROL OR BEHAVIOR]
What I actually see: [BRIEF DESCRIPTION]
Relevant account/workspace condition, if known: [ENTER]
Do not include passwords, access tokens, or private file contents just to explain a missing button. Begin with the product, the documented condition, and the observed difference. Bookmark the page that resolves your actual task so the next search starts from the right documentation set.