GDriveSync icon GDriveSync Google Drive -> local files
VS Code extension + agent-friendly CLI

Pull Google Drive documents into Markdown, CSV, and clean local assets.

GDriveSync is a Google Drive bridge for humans and agents. It turns Docs, Slides, Sheets, DOCX, PPTX, and XLSX into normal local files, then keeps them in sync with a deliberate one-way model where Google Drive remains the source of truth.

Read the docs Privacy policy View on GitHub
Docs -> Markdown Slides -> Marp Sheets -> CSV Each image asset as its own file

Built for the exact handoff agents actually need

Most automation wants stable local files, not opaque remote APIs. GDriveSync gives you a repeatable bridge from Google Drive into Markdown, Marp-flavored Markdown, CSV, and extracted image assets that normal tools can read immediately.

VS Code extension

Link the current file, sync on demand, use CodeLens and status UI, and keep Google content flowing into a normal workspace without leaving your editor.

CLI for agents

Inspect, export, link, status, sync, and unlink through a JSON-capable CLI designed for automation and agent workflows rather than fragile browser scraping.

Deliberate one-way sync

GDriveSync does not pretend to be a collaborative round-trip editor. Google Drive is the source of truth, and the local side is optimized for clean consumption.

What actually lands on disk

The output shapes are predictable, workspace-native, and easy to version or hand to another tool.

Google Docs and DOCX

Normal Markdown, with extracted local images instead of giant embedded blobs.

Google Slides and PPTX

Marp-flavored Markdown tuned for slide text, extracted assets, and practical downstream editing.

Google Sheets and XLSX

CSV output, including a directory-of-CSVs shape when there are multiple visible sheets.

Manifest-aware sync

A local .gdrivesync.json manifest stores file bindings and sync state without turning your workspace into a black box.

Privacy and hosting model

This domain exists for product identity, privacy policy, and the hosted Google Picker fallback flow. The sync product itself is local-first.

Local auth and state

OAuth tokens stay in local secret or auth storage. File mappings and sync metadata stay in your workspace-side manifest.

No hosted sync backend

GDriveSync does not proxy linked file contents through a hosted service. Optional cloud image enrichment calls provider APIs directly from the user’s machine.