Previews, downloads & sharing
Most files never need to leave Drive — you can look at them, play them, and read them in place, and grab a download when you do need the bytes.
Thumbnails
Section titled “Thumbnails”Image files show a square thumbnail on their card instead of a generic icon. Thumbnails are generated automatically shortly after an image finishes uploading, so a fresh upload may show the icon for a moment before its thumbnail appears.
The in-app viewer
Section titled “The in-app viewer”Click any file card to open it in the viewer:
| File type | What you get |
|---|---|
| Images | Full-size view |
| Video | Inline player with controls |
| Audio | Inline player |
| Page-by-page reader | |
| Everything else | Name, type, and size — plus the download |
The viewer’s footer always shows the file’s type and size, with a Download button on the right.
Downloads
Section titled “Downloads”Click Download in the viewer to fetch the original file. Downloads use short-lived, signed links minted for you at that moment — there is no permanent public URL to a Drive file, so a link can’t leak access after the fact.
Who can access a file
Section titled “Who can access a file”Drive files and folders follow the workspace-wide access model — private by default, shared on purpose:
- A file you upload is yours; being in the same workspace doesn’t expose it to others.
- Folder access flows down: someone with access to a folder can reach the files inside it, so organizing by folder is also organizing by audience.
- Workspace owners and admins can always reach workspace content.
The access levels, how grants combine, and what viewers experience are covered in Sharing & access.
Files also travel through the other apps without their access changing underneath you: attaching a Drive file to a chat message lets the channel’s readers fetch it through the channel, without granting them standing access to the file itself. To get a file to someone outside your workspace, attach it to a mail message.
Automating downloads or access checks? See the API reference.