What ChatGPT actually receives from a .docx upload
A 10-page Word document looks like 4-5K words to you. To ChatGPT, the same upload is closer to 8-12K tokens once the XML overhead is counted — paragraph IDs, revision markers, font definitions, list numbering schemes, theme references. The model has to mentally strip all of that before it can reason about your content. Sometimes it gets confused and quotes back fragments of metadata as if they were body text.
A pre-converted Markdown version is the same prose with the structural cues ChatGPT was trained on — H1/H2/H3 for sections, bullets for lists, bold/italic for emphasis. Token count drops, response quality goes up, and the model never accidentally paraphrases a style ID.
The workflow
Open Word to Markdown, upload your .docx, click Convert, download the .md. Drop the .md into ChatGPT instead of the original Word file. For documents you reference often (a company SOP, a product spec, a contract template), convert once and store the Markdown in a custom GPT's knowledge base — every conversation in that GPT then has clean access to the document.
Building a multi-source workflow? Combine with PDF for ChatGPT, URL for ChatGPT, Audio for ChatGPT, and Video for ChatGPT — every input becomes the same kind of structured context.