Can Grok read PDFs? Chat uploads, 150 MB limits, API Files, 512 MB files, and document search
Updated: Nov 1
Grok can read PDFs in both the consumer product and the xAI API, but the limits are different. Grok chat currently documents up to 150 MB for most uploaded files, while the developer Files workflow supports files up to 512 MB each.
The old Grok 4.1 framing is obsolete. Current document workflows use newer agentic models such as Grok 4.5 and Grok 4.6, with automatic attachment search in the API and broader multimodal file handling in grok.com and the mobile apps.
··········
GROK CHAT SUPPORTS PDFS AND MANY OTHER FILE TYPES
The consumer product accepts PDF, DOCX, TXT, CSV, XLSX, PPTX, HTML, XML, JSON, Markdown, LaTeX and other formats, plus images, audio and video. The web app supports roughly 100 attachments at once, Android documents up to 20, and iOS supports multiple attachments.
........
Surface | Published file limit | How PDFs are handled |
|---|---|---|
Grok web/app | Most files up to 150 MB | Direct chat upload, extraction, visual reasoning and summarization |
Web attachment count | Up to ~100 files | Multiple files can be analyzed together |
Android | Up to 20 files per message | Platform-specific attachment workflow |
xAI Files API | 512 MB per file | Agentic attachment_search over uploaded or public files |
........
··········
THE CONSUMER FILE LIMIT IS NOT THE API FILE LIMIT
For grok.com and the apps, xAI documents most documents, images, code and audio files at up to 150 MB each. The xAI developer Files workflow documents a separate maximum of 512 MB per file. These numbers refer to different products and should not be merged into a single Grok upload limit.
··········
PDF VISUALS CAN BE ANALYZED, BUT LARGE DOCUMENTS ARE SELECTIVE
Grok can reason over text and visuals inside PDFs. xAI advises that very long files may be summarized or processed in sections, and for PDFs above roughly 100 pages users should reference exact page numbers when they need specific visual or textual details.
··········
THE API TURNS FILE ATTACHMENTS INTO AN AGENTIC SEARCH WORKFLOW
When a file is attached to an API request, xAI automatically activates attachment_search. Grok can search across multiple attached documents, retain that file context across follow-up turns and combine document search with code execution for analysis and transformation.
··········
[[ADPLUS_300x250_1]]
ATTACHMENT SEARCH HAS ITS OWN TOOL COST
File-enabled API requests are billed for model tokens plus the attachment-search tool. xAI currently lists File Attachments at $10 per 1,000 attachment_search calls. Persistent collections use a separate collections-search mechanism and pricing.
··········
VERY LARGE PDFS STILL BENEFIT FROM TARGETED QUESTIONS
A file being accepted does not mean every page and visual receives equal attention in one response. For long contracts, reports or books, page-specific questions, section-by-section extraction and structured follow-ups reduce the risk that relevant details are compressed during summarization.
··········
GROK 4.1 IS NOW A HISTORICAL REFERENCE FOR THIS WORKFLOW
Earlier Grok 4.1 API model slugs were retired in May 2026 and redirected toward newer models. Current file-search documentation names agentic models including Grok 4.5 and Grok 4.6, so a 2026 PDF guide should describe the file system and current model family rather than presenting Grok 4.1 as the active document engine.
··········
FOLLOW US FOR MORE
··········
DATA STUDIOS
··········
