The short answer nobody leads with
There is no Dropbox URL you can hand to net use. Dropbox's own help centre has an article titled "Do you offer WebDAV, Email Attachments, or FTP support?", and the answer is that WebDAV, email attachments and FTP access are not on the current feature roadmap and are unlikely to be for the foreseeable future. Dropbox ships an API and a sync client. It does not ship a protocol Windows or Finder can mount.
That matters because almost every tutorial for "map Dropbox as a network drive" quietly skips it and describes something else: a synced folder with a drive letter pinned to it, or a third-party product that speaks the Dropbox API and re-publishes it over a protocol your operating system does understand. Both are legitimate. They just are not the same thing, and they cost different amounts of disk.
| Route | Gives you a drive letter | Local disk used | Needs the Dropbox app |
|---|---|---|---|
Dropbox app, then subst over the sync folder | Yes, per session | Whatever is not online-only | Yes |
| Dropbox app with selective sync | No, a folder only | Full copies of synced folders | Yes |
| Local WebDAV bridge, such as AnyStorage | Yes, persistent if mapped at logon | Nothing, files stream | No |
Route one: subst over the sync folder
The Dropbox desktop app keeps a folder in your user profile, by default %USERPROFILE%\Dropbox, and marking content online-only leaves placeholders in place of the bytes. Windows will happily put a drive letter in front of that folder, using a documented command whose entire job is to associate a path with a drive letter:
cmd
subst Z: "%USERPROFILE%\Dropbox"
subst
subst Z: /dUseful to know before you rely on it. subst drives are created for the current session, so the mapping is gone after a reboot unless you re-run it from a logon script or a Task Scheduler task triggered at sign-in. And any process that enumerates the tree, a backup agent or an indexer for example, will hydrate online-only placeholders and pull real bytes down, which defeats the point if the account is larger than the disk.
net use is not an option here. It takes a UNC path or a URL, not a local directory, so a local folder cannot become a network drive no matter how it is quoted.
Route two: what the official client is actually for
Selective sync and online-only files are the supported model, and for a laptop that is mainly a Dropbox laptop they are the right answer: offline access, conflict handling, sharing from the shell. The reason people search for a mount is the cases sync handles badly. An account far bigger than the local disk. A machine that should not hold a full copy of a client's files. A one-off pull of four files out of a 900 GB shared folder. Background sync activity you simply do not want on a render node.
For those, you want browse and transfer on demand, not replication.
Route three: bridge the API to a protocol Windows can mount
This is what AnyStorage does. Dropbox is one connection type in the app, authenticated with OAuth and stored encrypted on the local machine. Then a WebDAV server runs on your own machine and exposes every connection you have open as a folder: Services in the sidebar, the WebDAV tab, Start, endpoint http://127.0.0.1:3211, HTTP Basic auth always on with username anystorage and a 24-character password generated on first use.
Map that endpoint once and one drive letter covers Dropbox alongside an S3 bucket, Cloudflare R2, Backblaze B2, MinIO, Google Cloud Storage, Azure Blob, Alibaba Cloud OSS, Tencent Cloud COS, Google Drive, OneDrive, a WebDAV server, FTP, SFTP and local folders. Nothing is mirrored to disk; reads stream through with HTTP range support.
cmd
reg add "HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters" /v BasicAuthLevel /t REG_DWORD /d 2 /f
net stop WebClient
net start WebClient
net use Z: http://127.0.0.1:3211/ /user:anystorage * /persistent:yesThe registry line is needed because Windows refuses Basic credentials over plain HTTP unless BasicAuthLevel is 2, and the endpoint is HTTP on loopback. If the mapping fails with System error 67 has occurred or Error code: 0x80070043, the WebClient service is the usual culprit; Microsoft deprecated it in November 2023 and it is not started by default. See net use error 67 for the full list.
Two limits stated plainly: the WebDAV mount is read-only on the free tier, with read-write a Pro feature, and the free tier covers two storage connections. Also, a connection shows up under the WebDAV root only once you have opened it in the app during the current session, because connections connect lazily.
On a Mac
No kernel extension, no macFUSE. Press Cmd+K in Finder, enter http://127.0.0.1:3211, supply the same credentials, and the volume mounts under /Volumes. The Dropbox app's own folder lives at ~/Dropbox, and on recent macOS versions its online-only behaviour is implemented through a file provider extension, so the folder is again a folder rather than a volume. AnyStorage needs macOS 11 or newer; release 0.2.24 shipped on 23 September 2026, installable with brew install --cask kilerd/tap/anystorage.
Does Dropbox support WebDAV?
No. Dropbox's help centre states that WebDAV, email attachments and FTP are not on its roadmap. Anything advertising a Dropbox WebDAV URL is a third-party bridge translating the Dropbox API, whether it runs in the cloud or, as with AnyStorage, on your own machine.
Can I just map dropbox.com or a shared link?
No. Shared links are HTTPS web pages, not a filesystem protocol, and the API needs a client that speaks it. A drive letter always comes from something local: the sync folder, or a local server.
Will a mounted Dropbox drive fill up my disk?
Through a WebDAV mount, no, because files are fetched when opened and not retained as a mirror. Through subst over the sync folder, yes, to the extent that content is not online-only.
Is Windows 11 different from Windows 10 here?
The commands are identical. The difference in practice is that the WebClient service, which every WebDAV mapping needs, is deprecated and left on manual start, so a fresh Windows 11 machine usually fails the first mapping attempt until you start it.
Next steps
- The same job for OneDrive: mount OneDrive as a network drive
- The same job for Google Drive: mount Google Drive as a network drive
- When Explorer refuses the mapping: Windows cannot connect to WebDAV