Create
Import from Google Drive — Docs, Sheets & Slides
Start from a Google Doc, Sheet, or Slides — pick one file and Decks turns it into an on-brand deck or document in minutes.
Pick a file with Google's own picker — a Doc becomes a deck, a Sheet becomes charts and tables.
Decks only ever sees the single file you choose — never your whole Drive, so there's nothing to audit or approve.
The same build pipeline takes over: your brand kit applied, sections written, and every word left editable.
Start from what you have
Bring a Google Drive file straight into a deck
In the build console, choose “Start from Google Drive” and Google’s own Picker opens. You pick a single file — a Google Doc, a Google Sheet, a Google Slides deck, or a PDF or CSV. Decks fetches just that one file server-side and runs it through the same build pipeline as any other source: it extracts the text and tables, applies your brand kit, and normalises it into a deck or an A4 document. A Doc becomes a deck or a document, a Sheet becomes tables and charts, and Slides become a deck. And because it uses Google’s non-sensitive drive.file scope, Decks only ever sees the single file you pick — never the rest of your Drive.
Live preview
One file in, a finished deck out
You pick one file in Google’s Picker — nothing else is shared — and Decks reads it and rebuilds it on your brand: a deck that is ready to edit and export. The drive.file scope means everything but that one file stays completely out of view for Decks.
How it works
From a Drive file to a Decks build
Choose Start from Google Drive
In the build console, pick the Google Drive source and sign in to Google once. Google’s own Picker opens in a window — Decks never sees your password.
Pick exactly one file
Browse your Drive and select a single Google Doc, Sheet, or Slides — or a PDF, CSV, or similar. You choose the one file, and nothing else is ever shared.
Decks fetches just that file
With a short-lived access token, Decks pulls only the file you picked, server-side. It extracts the text and tables and applies your brand kit — the same pipeline every other source runs through.
It becomes a deck or a document
A Doc turns into a deck or an A4 document, a Sheet into tables and charts, and Slides into a deck — normalised, on brand, and ready to refine. Then the access token is discarded, and nothing is stored.
Where teams use it
The file already exists — start there
- Docs & briefs
A Doc into a deck
Turn a written brief, a memo, or meeting notes in Google Docs into a structured deck or A4 document — headings, sections, and bullets mapped onto your brand, not copied across slide by slide.
- Sheets & data
A Sheet into charts
Bring a Google Sheet of numbers straight in and let Decks read the tables into charts and clean summaries — figures on brand, without rebuilding a single table by hand.
- Slides & files
Slides, PDFs & CSVs
Start from an existing Google Slides deck, a PDF, or a CSV — Decks reads the one file you pick and rebuilds it on your brand kit, ready to edit and export.
Why it matters
It sees one file — never your Drive
Most “connect your Drive” integrations ask for sweeping access and drag your workspace admin into a security review. This one does not. Google Drive Import uses Google’s non-sensitive drive.file scope, which grants access to only the single file you explicitly pick in Google’s own Picker — never the rest of your Drive. That means no Google security review, no workspace-admin approval, and nothing to audit. The access token is short-lived and never stored, and saving a finished deck back to Drive is a separate step you opt into on its own. You start from the file you already have, and Decks sees nothing more.