DEV Community

疏影
疏影

Posted on

Two tiny Windows utilities that turn any folder or cloud drive into a real drive letter

If you work on Windows long enough, two recurring annoyances come up:

  1. Deep folder paths you have to click through over and over (D:\Projects\client-x\modules\src\components\);
  2. Cloud drives you can only reach through a client or a web UI, never directly from the command line or your editor.

Windows ships with subst, which maps a folder to a drive letter, but it dies on reboot and has no GUI. Here are the two tools I use to solve these for good.

ScsSubst — any local folder becomes a drive letter

ScsSubst is a lightweight Windows tool that maps any folder to a drive letter:

  • No file copies — it just gives the existing folder a drive-letter entry point;
  • No extra disk space, read/write speed is the same as the source folder;
  • Persistent across reboots, mounts on login;
  • Available directly in Explorer, Command Prompt, and any tool that reads drive letters.

I map D:\Work\projects to Z: and E:\Data\archive to Y:. cd Z: beats typing a long path every time. It is $9.99 as a one-time purchase — a lifetime license, not a subscription — with a free trial.

ScsDrive — cloud drives and WebDAV become a local drive

If you want OneDrive, Aliyun Drive, WebDAV, or S3 mounted as a local drive letter, that is what ScsDrive does:

  • Supports WebDAV/S3 and major cloud providers;
  • Local caching so large files don't stutter, auto-reconnect on drop;
  • Mounts on login and behaves like a local disk.

It is $5.50 as a one-time purchase — a lifetime license, not a subscription — plus a 7-day full-feature trial.

Which one do you need?

  • Just want faster access to deep local folders → ScsSubst;
  • Want cloud storage mounted locally → ScsDrive;
  • Use both and your drive-letter layout stays tidy.

Full disclosure: I work on ScsSubst and ScsDrive, and everything above comes from using them daily.

Top comments (1)

Collapse
 
rensu1114 profile image
Ren •

Curious how ScsDrive handles cache invalidation when the same remote files are modified by another client. Making remote storage behave like a local drive is convenient, but keeping cached data consistent across multiple writers is where things can get complicated.