Working in Clio

Clio Drive not working?

Clio Drive mounts your Clio documents like a network drive on your desktop — and because it is a live, internet-dependent sync, the ways it breaks are specific and recognizable. This guide walks the symptoms people actually hit — Drive that shows empty after syncing, a white X on the taskbar icon, a 'something went wrong with Drive' error, Drive that won't run on a Windows Server, and the connection dropping after every restart — and the documented fix for each. Where a fix touches Clio's own behavior, confirm the current steps in Clio's help center, since the desktop app changes over time.

By Lucas Barnes, Founder · Last updated July 9, 2026

Why it breaks the way it does

A live sync, not a local folder

Almost every Clio Drive problem traces back to one fact: Drive is a network drive, not a folder of files sitting on your hard disk. It streams documents to and from Clio's cloud and stays in active sync with Clio Manage, so it needs a stable internet connection to show or open anything. The local Drive folder is a cache, not the source of truth — your documents live in Clio Manage. That is why the standard fixes below are safe: deleting the local Drive cache folder (the Clio Launcher app folder, not the mounted drive itself), reinstalling the app, or toggling the connection rebuilds the cache without touching anything in Clio. Deleting or moving files inside the mounted Clio Drive is a different action entirely — because the drive syncs both ways, that removes them from Clio Manage as well (recoverable from Clio Manage's trash for up to 30 days).

One check before you start: if what's failing is Clio's Microsoft document source rather than Clio Drive — a OneDrive or SharePoint connection that won't authorize, or files that never appear from it — none of the fixes below apply, and deleting a Drive cache folder won't touch it. Otherwise, find your symptom in the table, then read the matching detail. Where a step references Clio's own menus or folder paths, confirm the current wording in Clio's help center — the desktop app changes, and the exact path matters when you're deleting a folder.

Find your symptom

Symptom, cause, and fix

Symptom	Likely cause	Documented fix
Drive appears but opens empty	Local Drive cache is stale or half-built	Close the desktop app, delete the Clio Drive cache folder (`%APPDATA%\Clio Launcher` on Windows; the Clio folder(s) under `~/Library/Application Support` on Mac — not the whole directory), reopen
White X on the Clio taskbar icon	Sync connection dropped	Toggle Drive access off, then on, to re-establish the sync
Folders/files still not visible	Drive component didn't install or mount cleanly	Uninstall and reinstall the Clio desktop app
"Something went wrong with Drive" / "Letter could not be changed"	Drive failed to start or mount the drive letter	Restart the Clio desktop app; if it persists, reinstall
Drive won't run on a Windows Server / RDS host	WebClient service not installed by default on Windows Server	Have IT install and start the WebClient service first
Drive won't run or install on this machine at all	Unsupported OS — Windows S mode is not supported; requires Windows 10/11 or macOS 11 Big Sur or later	Use a supported OS — a machine in Windows S mode can't run Drive; move to standard Windows 10/11, or macOS 11 Big Sur or later
Disconnects after every restart	Expected network-drive behavior — needs a live connection	Reconnect after restart/shutdown; confirm a stable internet connection

Before escalating, confirm the Clio desktop app is updated to the current required version. Clio enforces a mandatory security update (app version v3.5.3073) and prompts all Clio Drive users to update; an out-of-date app can fail to mount or sync. If none of these clear it, the Clio desktop app has a built-in support path — open it, select Drive, then Settings, then Support — which sends diagnostics to Clio's team. That is the right escalation once the self-serve fixes are exhausted.

The most common one

Empty after syncing

The drive mounts, the app says it's syncing, and the folder is empty. Before treating this as a fault, rule out the first sync: when you initially connect Drive, Clio syncs your data from Clio Manage before files become browsable, and for a firm with a lot of documents that pass can take several minutes to an hour. An empty drive during the very first sync is normal.

If it has clearly finished and the drive is still empty, the local cache is stale. Fully quit the Clio desktop app, delete the local Drive cache folder — the Clio Launcher folder under %APPDATA% on Windows (%APPDATA%\Clio Launcher), or the Clio folder(s) under ~/Library/Application Support on Mac (the Clio-specific folders, not the whole directory) — then reopen the app so it rebuilds the cache from Clio Manage. Because Drive streams from the cloud and your documents live in Clio Manage, deleting this cache folder — the Clio Launcher app folder, not the mounted drive itself — removes only the cache; nothing leaves Clio. Deleting or moving a file inside the mounted Clio Drive is the opposite: the two-way sync removes it from Clio Manage as well, though you can recover it from Clio Manage's trash for up to 30 days.

If the rebuild still shows nothing, escalate to a reinstall of the desktop app, which replaces the Drive component itself. Confirm the current folder paths in Clio's help center before deleting anything, since the desktop app's layout changes between versions.

The dependable fallback

When you just need the file in Clio

Drive is built for daily editing — opening and saving matter files from Word or your file explorer as if they were local. But when the sync is misbehaving and you simply need to get documents into a matter, you don't have to wait for Drive to recover. The web Documents area accepts drag-and-drop and bulk uploads directly in the browser, with no desktop app in the path — which means none of the sync problems on this page can block an upload.

For high-volume or recurring inbound files, bulk upload and Clio's official integrations file documents into matters without the desktop sync layer at all. Keep working the Drive issue separately, but don't let a desktop-sync problem hold up a filing — the browser path is the reliable way through. And if the browser upload is the thing failing — stalls, "Something Went Wrong" errors, oversized files — that's a different problem with its own fixes, covered in the upload troubleshooting guide.

Clio Drive troubleshooting FAQ

Got more? Email [email protected].

Q.01

Why does Clio Drive show empty after it finishes syncing?

This is one of the most common Clio Drive symptoms: the drive mounts and the app reports syncing, but the folder opens empty. The documented fix is to fully close the Clio desktop app and delete the local Drive folder so the app rebuilds it on next launch — on Windows that's the Clio Launcher folder under %APPDATA% (%APPDATA%\Clio Launcher), and on Mac it's the Clio folder(s) under ~/Library/Application Support — the Clio-specific folders, not the whole directory. Reopen the app and let it re-sync from Clio Manage. Because Clio Drive streams files rather than keeping full local copies, this app cache/config folder — the Clio Launcher folder, not the mounted drive itself — can be safely rebuilt; your documents live in Clio Manage, so deleting that cache folder does not delete anything from Clio. Deleting or moving a file inside the mounted Clio Drive itself is a different action entirely: because the drive is in two-way sync, doing so also deletes the document from Clio Manage (recoverable from Clio Manage's trash for up to 30 days). Confirm the exact folder path in Clio's help center if your setup differs.

Q.02

What does the white X on the Clio taskbar icon mean?

A white X on the Clio taskbar (or menu-bar) icon indicates the Drive sync connection has dropped. The documented fix is to toggle the Drive access setting off and then back on, which forces the app to re-establish the sync connection. If toggling does not clear the X, treat it like a full disconnect: confirm you have a stable internet connection, then restart the Clio desktop app. The X is a connection-state indicator, not a data-loss indicator — once the connection re-establishes, your files reappear.

Q.03

Does Clio Drive work offline?

No. Clio Drive is a network drive: it streams files to and from Clio's cloud and is in active sync with Clio Manage, so it needs a stable internet connection to show and open your documents. You may have to reconnect to Clio Drive each time the computer is restarted or shut down, or any time the connection has been unstable. If you need a file available without a connection, open it while online so it is cached locally, or keep a working copy outside the drive. For getting files into Clio when the desktop app is unreliable on a given machine, a browser-based upload path avoids the desktop sync layer entirely.

Q.04

Why won't Clio Drive run on a Windows Server?

Windows Server installations do not include the WebClient service by default, and Clio Drive depends on that service to operate as a network drive. On a server (or a server-based remote-desktop environment), the WebClient service has to be installed and running before Clio Drive will mount at all. This is the usual reason Drive works on staff laptops but fails on a Terminal Server or RDS host. Your IT administrator can add the WebClient feature; confirm the current requirement in Clio's help center, as server support details change.

Q.05

How long should the initial Clio Drive sync take?

When you first connect Clio Drive, it syncs your data from Clio Manage before the files are browsable in File Explorer or Finder, and that initial pass can take anywhere from several minutes to an hour depending on how many documents your firm has in Clio. An empty-looking drive during this first sync is expected, not a fault. If it has clearly finished syncing and the drive is still empty, that is the empty-after-sync case above (close the app, delete the local Drive folder, reopen). Give the very first sync time before treating slowness as a bug.

Q.06

What do I do about 'Something went wrong with Drive' or 'Letter could not be changed' errors?

These errors mean the desktop app's Drive component failed to start or to mount the drive letter cleanly. The first documented step is to restart the Clio desktop app, which re-runs the mount. If the error persists, escalate the same way you would a stuck sync: confirm internet connectivity, and if folders still do not appear, uninstall and reinstall the Clio desktop app so the Drive component is reinstalled fresh. The Clio desktop app also has a built-in support path — open it, select Drive, then Settings, then Support — to send diagnostics to Clio's team.

Q.07

Is there a way to get files into Clio that does not depend on the desktop app?

Yes. Clio Drive is one way to work with documents, but it is not the only way to get files into a matter. The web Documents area accepts drag-and-drop and bulk uploads directly in the browser with no desktop app involved, which sidesteps every Drive sync problem on this page. For high-volume or recurring inbound files — court filings, signed agreements, email attachments — browser-based upload tools and Clio's official integrations file documents into matters without the desktop sync layer. If Drive is unreliable on a particular machine, routing uploads through the browser is the dependable fallback while you work the sync issue separately.

Related guides