You have a Google Drive with 800 GB of stuff in it. Your laptop has 256 GB of SSD. You want all of it accessible — open any file from Finder or Explorer, drag things in and out, run grep across a folder of PDFs. You don't want to sync 800 GB you mostly don't touch, and you definitely don't want Google's "Drive for Desktop" app eating CPU because it's reconciling deltas every five minutes. You ask the obvious question: why isn't Google Drive just a drive letter?
It can be. This post is the answer for Mac, Windows, and Linux — how to mount Google Drive as network drive shape on any desktop OS, what to expect, and where the limits are. We make a tool that does this, so call this opinionated — but the architectural framing is real and worth reading whether you end up using ExpanDrive or not.
What "map Google Drive as a network drive" actually means
A Google Drive network drive makes the cloud storage appear as a drive in your file manager — G: (or whichever letter you assign) on Windows, a mounted volume in Finder on Mac, a folder in your Linux file manager. Open a file from the mount; your default app opens it. The file downloads in the background on demand, gets cached, and uploads back to Google Drive when you save. Files-On-Demand semantics: zero local disk at rest, instant access to any file in the library, native filesystem behavior. That's all "map Google Drive as network drive" really is — a thin filesystem layer in front of the Google Drive API.
This is one of three ways to interact with Google Drive on a desktop:
- The browser. drive.google.com is fine for reading a doc and walking away. Painful when you want to open files in native apps, search inside file contents, batch-rename, or treat Google Drive like a real filesystem.
- Google's own "Drive for Desktop" (the consolidated app that replaced Backup and Sync and Drive File Stream). It has a streaming mode that does mount-as-drive, which is a real improvement over the old sync-only behavior. It works on Mac and Windows but not on Linux — Google has never shipped a Linux Drive client and shows no signs of doing so.
- Mount-as-drive via a third-party client like ExpanDrive. Same Files-On-Demand semantics as Google's app on Mac/Windows, plus Linux support, plus the ability to connect multiple accounts simultaneously in a single client. Same UI everywhere.
Why a third-party Google Drive network drive client
Two reasons Google's own Drive for Desktop won't be enough for some readers of this post:
-
You're on Linux. Google's client doesn't run there. The OSS option is
google-drive-ocamlfuse(single-maintainer FUSE driver, Linux-only). The polished paid option is ExpanDrive or Insync. -
You need multiple Google accounts in one client. Google's app supports up to four accounts but the management UI is awkward and per-account streaming behavior isn't unified. ExpanDrive treats every connection — Google personal, Google Workspace, OneDrive, Dropbox, S3, SharePoint — the same way: a connection in a list, with its own mount point.
If you only have one Google account and you're on Mac or Windows, Google's own Drive for Desktop is a fine choice and free. We're not trying to convince single-account Mac/Windows users to use ExpanDrive. We're trying to be useful to the Linux user, the multi-account user, the mixed-OS team, and the IT admin who needs Google Drive to show up as a drive letter that survives reboot on a server.
What ExpanDrive does
ExpanDrive is a Google Drive network drive client for Mac, Windows, and Linux. Free for individuals and teams under 10 users since the 2025 Files.com acquisition — paid licenses only required for larger commercial, academic, and government teams.
What you get:
- Map Google Drive as network drive on Windows 10 and Windows 11. Drive letter assigned in Explorer; Word, Excel, Photoshop, and every other Windows app sees Google Drive like any local drive. Survives reboot, runs as a service in the Server Edition for unattended deployments.
- Map Google Drive as a network drive on Mac. Mounted volume in Finder; behaves identically to any other connected drive. Works under Intel and Apple Silicon.
- Google Drive on Linux. The story Google never shipped — Ubuntu, Linux Mint, Fedora, RHEL, CentOS, Debian, Arch, OpenSUSE. Add Google Drive as network location, files appear under
~/Cloud Drives(or wherever you configure), terminal apps and IDEs treat it as a normal directory. - Personal, Workspace, and Shared Drives. ExpanDrive mounts personal Google Drives, Workspace organizational drives, and the Shared Drives (formerly Team Drives) that show up under "Shared drives" in the web UI. Pick which you want mounted; switch between them per connection.
- Multiple accounts at once. Add your personal Google account, your work Workspace account, and a client's account as three separate connections. Each gets its own mount point. No re-authentication every time you switch.
- OAuth + 2FA respected. Authentication goes through Google's normal flow, so your 2FA / security key / Google Workspace SSO requirements all apply. ExpanDrive never sees your password.
How to map Google Drive as a network drive
This is the click-by-click setup for anyone searching "how to map google drive to windows," "map network drive to google drive," or "google drive map network drive" — same steps on every supported OS.
The first time you connect, the path is short:
- Download ExpanDrive for Mac, Windows, or Linux. Install.
- Open ExpanDrive — it sits in the system tray (Windows) or menu bar (Mac) or app drawer (Linux).
- Click Add Connection and pick Google Drive.
- ExpanDrive opens Google's authentication flow in your browser. Log in, complete 2FA if your account has it, grant ExpanDrive read/write access.
- Pick which drive to mount (your personal My Drive, or any Shared Drive in your Workspace). Pick the mount point.
- Click Connect. The drive shows up immediately in Finder / Explorer / your Linux file manager.
That's the whole setup. About 90 seconds end-to-end. The same flow works whether you're on Windows 11, macOS, or any supported Linux distro.
Files-On-Demand semantics and the Google Docs quirk
When you double-click a file from your mounted Google Drive, ExpanDrive transparently downloads it in the background and caches it locally. The cache evicts least-recently-used content as it fills, so disk usage stays bounded regardless of library size.
There's one Google-specific quirk worth knowing: native Google Docs, Sheets, and Slides files don't have a downloadable binary representation. They live entirely as Google's internal document format. In your mounted Google Drive, those appear as small .gdoc / .gsheet / .gslide shortcut files. Double-click one and your browser opens the document in docs.google.com — that's the only way to edit them. This is a Google product decision, not an ExpanDrive limitation; the same shortcut behavior happens with Google's own Drive for Desktop.
Files in conventional formats (.docx, .xlsx, .pdf, .psd, anything binary) open directly in their native app from the mount and behave like local files.
When ExpanDrive isn't the right answer for Google Drive
Three real tradeoffs:
- No offline mode. If you fly a lot and need Google Drive files on the plane, mount semantics are the wrong shape. Google's own Drive for Desktop has "available offline" pinning that handles this; use it if offline use is a primary need.
- Bandwidth-bound for large reads. Opening a 2 GB video over hotel Wi-Fi is gated by your downlink, not your SSD. Local sync wins for files you'll open repeatedly on a slow network.
- You're past 10 users in a commercial / academic / government org — a paid ExpanDrive license is required. Pricing on the download page. The free tier covers most readers of this post — individuals, small teams, anyone working solo across multiple machines.
Where mount wins is everywhere else: large Drive libraries that don't fit on a laptop, multiple Google accounts in one client, mixed-OS teams that want a Google Drive client behaving identically on Mac and Linux, and anyone who needs Google Drive to show up as a drive letter on a Windows server at boot.
System requirements
ExpanDrive runs on currently-supported versions of:
- macOS — Intel and Apple Silicon
- Windows 10 / 11, Windows Server 2016+, Terminal Services / RDP environments
- Linux — Ubuntu, Linux Mint, Fedora, RHEL, CentOS, Debian, Arch, OpenSUSE (any distro with a working FUSE 2.9+ should work; these are the ones we test)
Per-user mount isolation on multi-user Windows machines — each logged-in user sees their own Google Drive connections.
Full install docs and per-OS specifics: docs.expandrive.com.
Try it
Download ExpanDrive. Free for individuals and teams under 10 users. No trial cliff, no credit card.
You'll have Google Drive mounted as a network drive on Mac, Windows, or Linux — personal account, Workspace account, Shared Drives, multiple accounts at once — in about 90 seconds. If you've been wrestling Google's Drive for Desktop limitations, or you're on Linux where Google ships nothing at all, this is the answer.