Files and reviewable results: transfers, cloud drives, and artifacts
The official design intent for Grok Bot files and results comes down to one sentence: attach materials to your request, and get back results you can check, edit, and hand off. The previous lesson covered "talking to it" thoroughly; this lesson covers the flow of materials: how to attach files, how to give links, how to transfer via cloud drives, how to review results, and how to retrieve outputs.
The whole thing takes about 10 minutes, with not a single command to run—every operation is "talking to it" plus a few clicks.
What you'll be able to do after this lesson
- Hand over all materials in one message: use attachments, pasting, and the mobile share panel, know the count and size limits, and clearly state each file's purpose
- After connecting cloud drives, have the Bot move files between its cloud computer and Google Drive, OneDrive, SharePoint, Gmail, and Outlook, without pasting content into the chat
- Ask for "reviewable artifacts" by name: specify the format and acceptance criteria, and have the Bot list facts, assumptions, completed, pending approval, and unresolved separately
- Preview and save the Bot's outputs in conversation cards, and have it revise the same result rather than starting from scratch
- Use the Library to find pages and files the Bot has made, plus images, videos, and links it has sent
Your current predicament
- Moving files back and forth relies on "download—upload": the cloud drive looks one way, the chat tool another, shuffling between the two and easily sending the wrong version
- You ask the Bot for a report and get back a wall of text—which parts it looked up and which it guessed are impossible to verify
- The spreadsheet it made last week, the images it sent—when you want to reuse them today, you can't find them by scrolling through the chat history
When to use this technique
When you need to:
- Hand PDFs, spreadsheets, and screenshots to the Bot in one go along with your instructions, clearly stating what each file is and how to use it
- Have the Bot directly read and write collaborative files in cloud drives, instead of copying the content into the chat
- Get results you can check, edit, and hand off, rather than an unverifiable block of text
And you don't want to:
- Have large files rejected at the door, leaving you to guess what limit was exceeded
- Have facts and assumptions mixed together, so when something goes wrong you don't know which half to trust
- End up with a new copy every time the Bot revises, versions flying everywhere
🎒 Preparation before you start
- Completed 2.1 Messages and conversations: you can send messages and attach files—this lesson builds on that to cover the flow of files thoroughly
- Have at least one Bot on hand and have assigned work once (see 1.5 First Bot)
- To use cloud drive transfers: have connected at least one of Google Drive / OneDrive / SharePoint / Gmail / Outlook; for connection steps see 2.5 Connect apps
- A cup of water ☕—this lesson has no commands to run; every operation is "talking to it"
Core idea
Grok Bot file exchange follows one main thread: materials go from your hands into its cloud computer, results come back from its cloud computer to your hands, checkable the whole way.
- Input has boundaries. Attachments have explicit count and size limits; the composer tells you plainly when a file exceeds them, it doesn't silently drop it.
- The middle happens in the cloud computer. The Bot processes files on its persistent cloud computer; once cloud drives are connected, it moves files directly between the drives and the computer, without the content passing through the chat.
- Output must be reviewable. Results aren't just "a paragraph of text"—officially they're called artifacts: outputs you can open and preview, save, and keep having it revise. The format and acceptance criteria are specified by you when assigning the work.
Three ways to hand over materials, switch by scenario:
| Method | When it's suitable | What to watch out for |
|---|---|---|
| Direct attachment | Local files, screenshots, use-and-toss | Subject to count and size limits (see Step 1) |
| Paste a link | Web pages, online documents | Only works if the Bot can access it; private pages require cloud computer login or connecting an app |
| Cloud drive transfer | Collaborative files read and written repeatedly | Requires connecting an app first; each cloud drive has different same-name rules (see Step 3) |
Follow along
Step 1: Check Grok Bot file upload limits: attachments, pasting, and mobile sharing
Why: Grok Bot file upload limits are hard boundaries—know them up front so you can hand over all materials in one go without being blocked by the composer.
Desktop attachment limits per message:
| Limit | Value |
|---|---|
| Attachments per message | 20 |
| Images | 25 MB each; 200 MB in total per message |
| Documents, audio, and other files | 250 MB each |
| Videos | 1 GB each |
How to access it:
- Attachment control, or simply drag files into the composer; images and links can be pasted directly
- Commonly supported inputs: images, audio, video; PDF and plain-text documents; Word, Excel, PowerPoint; CSV, JSON, YAML, and source code files; HTML and email files; Jupyter notebooks
- File exceeds the limit: the composer will say it's too large and leave it behind—send any left-behind files in a separate message
- iPhone: open the system share sheet in another app → select Grok Bot → pick a chat → Attach; photos, files, links, and text can all be sent into that conversation's composer
- Android: the share sheet currently accepts only text
You should see: the attachment appears in the composer; files that exceed the limit are clearly flagged as "too large" and are not silently dropped.
💡 State clearly what each attachment is
The official guidance recommends explaining each file's purpose in your message. Follow the style of the official example sentence:
This PDF is the signed policy, and this spreadsheet is this month's transaction records. Please check the records against the policy, cite the corresponding policy clause for each exception, and return a new spreadsheet plus a brief summary. Do not modify the originals.
State "what it is, how to use it, and whether the originals may be changed" all at once, and the Bot won't need to ask you back.
- Sent the Bot a message with attachments and explained each file's purpose
Step 2: Paste links to the Bot: it can only read pages it can access
Why: a lot of material lives on the web—docs, reports, issues. When the Bot can access a page from its cloud computer or connected apps, a link is far easier than "download then re-upload."
- Ask before pasting: can the Bot open it? Paste public pages directly; for private pages, have it log in via the cloud computer (sensitive steps that require login will ask you to Take over, see 1.5 First Bot), or connect the corresponding app first (see 2.5 Connect Apps)
- Links in messages and results open in your system browser; hovering over a link card shows a preview first
- Before entering credentials or approving external actions, check where the link leads
You should see: the link turns into a card; the Bot opens the page from its cloud computer, reads the content, and gets to work, instead of making you copy the text to it.
Step 3: Cloud drive transfers: move files between the cloud computer and Google Drive, OneDrive
Why: collaborative files live in cloud drives. Once connected, the Bot's reads and writes on Google Drive and OneDrive happen between its cloud computer and your account—content isn't pasted into the chat, and you don't need to download and re-upload.
Prerequisite: Google Drive, OneDrive, SharePoint, Gmail, or Outlook is already connected (see 2.5 Connect Apps).
Files can be moved in both directions:
- Save out: save files it created or downloaded to Google Drive, OneDrive, or SharePoint, or attach files to a Gmail / Outlook draft
- Bring in: take files or email attachments from Drive, OneDrive, or SharePoint onto its cloud computer for processing
Automatic format conversion: Google Docs, Sheets, Slides, and Drawings become .docx, .xlsx, .pptx, and .png files once they arrive on the cloud computer.
The rules for same-name files are spelled out officially, and the two behave differently:
| When a file with the same name already exists in the cloud drive | |
|---|---|
| Google Drive | always creates a new file, even if the same name already exists |
| OneDrive / SharePoint | rejects an existing same name, unless you tell the Bot to overwrite |
You should see: after you state clearly "where the file goes," the file appears at the cloud drive location you specified, or is already attached to a Gmail / Outlook draft—the content is never pasted into the chat.
- Had the Bot save a file to a cloud drive, or fetch a file from a cloud drive to the cloud computer for processing
Step 4: Ask for a reviewable artifact by name: form and acceptance criteria
Why: the quality of the result is decided the moment you assign the task. Only by specifying the artifact (the form of the result) and acceptance criteria does the Bot know what "done" looks like—this is also the foundation of reviewing Grok Bot results: with clear standards, checking has a basis.
Official artifact examples—specify the one you want:
- A document with headings and source links
- A spreadsheet with clearly defined columns and formulas
- Slides with speaker notes
- A folder containing screenshots and logs
- A draft message that has not been sent yet
- A brief recommendation followed by the underlying evidence
For important work, add a "five-way separation"—have the Bot list these separately:
- Facts found in the source systems
- Assumptions and inferences
- Actions completed
- Actions awaiting approval
- Unresolved questions
You should see: what the Bot delivers is no longer a paragraph of text, but a file or draft you can open and inspect, plus a sorted checklist—which parts you can trust as-is and which parts need your sign-off, clear at a glance.
💡 Strong results must be "independently reviewable"
The official guidance recommends asking the Bot for evidence by task: direct source links, screenshots showing the relevant state, timestamps with time zones, input and output file names, a concise action log, and a list of "things the Bot could not verify."
For fast-changing data, don't rely on screenshots alone—keep the source system's link or export whenever possible.
- Specified the artifact's form and acceptance criteria when assigning a task
Step 5: Preview and revision: have the Bot revise the same result, not start over from scratch
Why: The Bot's output appears in the conversation as cards—files, images, links, and tool results all count. You can preview, save, and keep giving feedback on a card; when making changes, have it revise the existing artifact rather than adding a broken-off copy every time.
- Open a card: preview the supported formats, then save the file, open the source link, or keep the conversation going from it
- To make changes: just say so. Follow the wording of the official example sentence:
Update the report you just created: add source links to the first two claims, and replace the final table with a CSV attachment.
You should see: the Bot edits the same artifact, without the conversation littered with "report v1, report v2, final report".
💡 Report-type results can be built as Pages
For results meant for long-form reading, with charts and controls, that can be shared with others (reports, dashboards, trackers), have the Bot build them as Pages—see C2 Delivering reports and content dashboards with Pages.
Step 6: Use Library to retrieve files and pages the Bot has made
Why: Pages, files, and apps the Bot has made, plus the images, videos, and links it has sent in your conversation, are all stored together in its Library—no need to dig through chat history.
- Desktop: click the Bot's name at the top of the chat (View conversation details) → open the Library tab
- Mobile: tap the Bot's name at the top of the chat to open its profile → tap Library
- The list is grouped by Today / This week / Older, newest first; each group shows 5 items at a time—tap Show more to see more
- The row menu (More actions, three dots): Pin pins frequently used items to the top under Pinned, and Unpin undoes it; the menu for pages also has Open, and pages you own also have Share…
- There's also a shortcut for finding pages: on desktop press
Cmd/Ctrl+Kand type the page title
You should see: the Library lists the Bot's output—click a page to open it, an image or video for fullscreen, a file to preview, a link to open in the browser; pages that have been shared carry a marker on the row.
⚠️ Library does not include what you send
Officially stated: content you send (including images you upload) is not in the Library; files returned by Cloud Agent are not listed either. The Library only records what the Bot makes and what it sends.
- Opened the Bot's Library and found a file or page it made
Checkpoint ✅
- Sent a message with attachments: delivered everything at once within the limits, and stated each file's purpose clearly
- Pasted a link for the Bot to read, or know that private pages require cloud PC login / connected apps
- Had the Bot move a file between cloud drive and cloud PC; know that Drive always creates a new file with the same name, while OneDrive / SharePoint rejects duplicate names
- Specified the artifact form when assigning work, and had the Bot separate facts / assumptions / completed / pending approval / unresolved
- Opened the Bot's Library to retrieve its output
Pitfall reminders
❌ Attachment won't send, composer says the file is too large
Symptom: the attachment won't go through, and the composer says it's too large.
Cause: it exceeds the limits from Step 1—20 per message; images 25 MB each and 200 MB total per message; documents and the like 250 MB each; videos 1 GB each.
What to do: send the file that got left out in another message. The composer only blocks the one that exceeds the limit; the rest go through as usual.
❌ Attachment sent, but the Bot says it can't read it
Symptom: the file was sent successfully, but the Bot says it can't open or read it.
Cause: common cases listed officially—the file is too large, encrypted, corrupted, or in a rare format.
What to do: export rare formats as PDF, CSV, plain text, or an image and resend. For more troubleshooting, see Error quick reference.
❌ Saving to cloud drive: duplicate-name files pile up in Drive, while OneDrive just errors out
Symptom: saving a file to Google Drive adds another same-named copy every time; saving to OneDrive / SharePoint, the Bot says the name already exists and can't save it.
Cause: the two have different rules. Officially stated: saving to Google Drive always creates a new file, even if the same name already exists; OneDrive / SharePoint rejects an existing duplicate name.
What to do: settle on naming before saving to Drive, or have the Bot tidy up old versions first; when saving to OneDrive / SharePoint, tell the Bot explicitly whether to overwrite or rename.
❌ Android share sheet can't send files
Symptom: on Android, using the system share sheet to send a file to Grok Bot doesn't go through.
Cause: officially stated—Android's share sheet currently accepts text only.
What to do: send files as desktop attachments instead; the iPhone share sheet supports photos, files, links, and text and is not subject to this limit (see 1.6 Mobile).
Advanced tips (optional)
Cloud Agent results flow back on their own. The Bot can hand coding work to a Cloud Agent; once done, it copies the images, videos, and other files referenced in the Cloud Agent's final report to its own cloud computer and attaches them to its reply. The Cloud Agent card on desktop shows the same files; on mobile they appear after the run changes to Done / Error / Expired—images first, then videos, then other files. If a file fails to load, tap Retry; for runs that opened a pull request and haven't expired, tap View PR.
Multiple Bots share /workspace. Bots can read files other Bots stored in /workspace—use project folders and descriptive file names so handoffs are reliable. The shared workspace is good for intermediate materials; final results should still appear in the conversation, or with a clear link. For cloud computer persistence and recovery, see 5.1 Cloud Computer Care.
Image and video generation parameters are in the next lesson. For the parameters and limits for having a Bot generate images and videos—aspect ratio, duration, resolution, and more—see 2.3 Image and Video Generation. Every image and video it creates is sent to the conversation and can later be found again in the Library.
Lesson Summary
✅ Grok Bot file flow in one line: materials go from you into its cloud computer, results come back from its cloud computer to you, and it's inspectable the whole way.
✅ Inputs have limits: 20 attachments per message; images 25 MB each, 200 MB combined; documents and the like 250 MB each; videos 1 GB each; state the purpose of every attachment.
✅ Links depend on access: paste public pages directly; for private pages, use cloud computer login or connect an app first.
✅ Cloud drive transfers don't paste content: Google Docs become .docx and similar formats on the cloud computer; Drive always creates a new file with the same name, while OneDrive / SharePoint reject duplicates.
✅ Results must be reviewable: specify artifacts and acceptance criteria; for important work, have the Bot separate facts, assumptions, completed items, items pending approval, and unresolved items.
✅ Output is centralized in the Library: pages, files, and apps the Bot made, plus the images, videos, and links it sent, are all there; Cmd/Ctrl+K to find a page directly.
Key limits and entry points at a glance:
| Item | Value / Entry point |
|---|---|
| Attachments per message | 20 |
| Images | 25 MB each; 200 MB combined per message |
| Documents, audio, etc. | 250 MB each |
| Videos | 1 GB each |
| Library | Bot name → View conversation details → Library (mobile: Bot name → profile → Library) |
| Find a page | Cmd/Ctrl+K Type the page title |
| Cloud drive transfer prerequisite | One of Drive / OneDrive / SharePoint / Gmail / Outlook connected |
Next Lesson Preview
With materials moving in and out sorted, the next step is seeing how it creates something from nothing. Next lesson: 2.3 Image and Video Generation.
You will learn:
- The 5 aspect ratios for image generation, and why charts and tables belong in Pages rather than generated images
- Video generation limits on duration, resolution, and reference images: 1–15 seconds, 480p or 720p, up to 14 reference images
- Which requests get blocked by content rules and how the Bot tells you
- Where the images and videos it makes are stored, and how to save and forward them