Zoom tells you, in writing, not to record to an external hard drive. Its recording FAQ is blunt: "Do not use external or network storage for computer recordings; for example, an external hard drive or network-attached storage. These storage methods can result in data loss."
If you arrived here with a half-converted meeting, a .zoom file that refuses to open, or an MP4 that stops partway, that sentence is the root of the problem. Here is what Zoom actually documents about it, and what to do with the recording you already have.
What actually breaks
Zoom attaches the risky step to one specific moment. Its troubleshooting article for computer recordings opens with it: "After you end a Zoom meeting, your computer-recorded meeting will convert."
Zoom's page on starting a computer recording names the scenario directly, and widens it well past physical drives:
"Note: Setting the default location to a cloud syncing folder (such as Dropbox, Google Drive, or One Drive), an external drive, or network storage device may cause issues with saving and converting the computer recording. Zoom strongly recommends keeping the default location on a local drive for recordings."
Two things are worth pulling out of that sentence. First, a sync folder counts as the same class of problem. Pointing Zoom at a OneDrive, Dropbox, or Google Drive folder is listed alongside external drives and network storage, even though the bytes sit on your internal disk. Second, the wording is "saving and converting" — both halves of the job, not just the final write.
The client settings page adds the check you can run yourself: "Under Local recording storage, locate the Storage location. The path listed next to the Storage location field is where your computer recordings are saved. If the path shown isn't physically located within your device, such as a network drive, you might encounter issues."
And the troubleshooting article lists the failure under its own heading: "Invalid working path/folder (sometimes, an invalid network connection may appear with this warning too)." That parenthesis matters — Zoom is saying a path complaint and a connection complaint can surface as the same warning.
What Zoom never does is explain which layer gives out. It documents the symptom and the recommendation, and nothing further, so treat any "here is exactly why USB fails" explanation you read elsewhere with suspicion.
Before you start: what is actually recoverable
Set expectations first. Zoom's page on missing meeting recordings says it plainly: "Local recordings exist only on the computer where they were created. Zoom does not retain a copy and cannot recover a lost local recording." There is no support ticket that brings a local recording back.
The severity language also differs across Zoom's own pages, and the gap is worth knowing. The troubleshooting page says a file renamed mid-conversion "may corrupt the file and not convert correctly." The page on starting a computer recording is heavier: "If the meeting unexpectedly shuts down or if the conversion process is interrupted, the recording files could become corrupted and non-recoverable. Restarting or shutting down your computer, putting the hard disk to sleep, or closing your laptop will interrupt the conversion process."
Note what is on that list of interruptions: restarting, shutting down, putting the hard disk to sleep, and closing your laptop.
The fix: point the recording location back at a local drive
Zoom's remedy for the invalid-path case is one line: "Change the recording location in your Zoom client and make sure it is a valid path string/folder." The defaults it ships with are:
Windows: C:\Users\[Username]\Documents\Zoom
Mac: /Users/[Username]/Documents/Zoom
Linux: home/[Username]/Documents/ZoomZoom prints the Linux path two different ways across its own pages — one with a leading slash, one without — so read the Storage location field in your client rather than typing a path from memory.
Before changing anything, Zoom's first-listed suggestion on the troubleshooting page applies: "In addition to the steps below, confirm that you are running the latest version of the Zoom desktop app."
If the files from the failed session are still on the external drive as double_click_to_convert_01.zoom and double_click_to_convert_02.zoom, copy them to a local folder before trying anything. And do not tidy the names up first — Zoom warns: "If you change the name of the double_click_to_convert.zoom file(s) while the recorded meeting is converting, it may corrupt the file and not convert correctly." The full manual procedure is covered in converting a double_click_to_convert.zoom file.
Most people point Zoom at an external drive for one reason: the internal disk is tight. Zoom gives a rough sense of the appetite: "Recording screen sharing uses about 20MB of storage per hour, while recording video uses about 200MB of storage an hour." It immediately qualifies that: "This is an approximation, since the resolution and types of video or screen sharing content can affect the amount of storage used." So plan for headroom, not for the number.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
The workable pattern is: record to the local default, let the conversion finish, then shrink the finished MP4 before you archive it. Compressing in the browser keeps the meeting on your machine — nothing is uploaded — and a smaller file makes keeping recordings on an internal disk realistic. If you would rather start from the tool itself, compress video is the same engine, and all Clapr tools lists the rest.
Zoom does contemplate renaming afterwards, with a caveat: "After the file has completed converting, if you choose to rename the file from the default naming convention, we recommend you use a unique file name. We recommend you do not use the words Zoom, Personal Meeting Room, or My Meeting when saving your meeting files." Zoom does not say why.
Other causes worth ruling out
Low disk space. The one case Zoom attaches an error code to: "You may have low disk space on your computer at that time. [Error Code 614]" The fix is exactly what it sounds like — "Check your disk space and try and free up some space if it is low." That code is documented for this situation only, not as a general conversion failure. See Zoom Error Code 614.
An interrupted conversion. Zoom: "If you close your laptop or turn off your computer while the recording is converting, it will stop the conversion process."
Everything else. Zoom groups the remainder as "Abnormal errors such as internal errors (bad data stream), invalid commands, or logic issues," without elaborating.
How to tell it worked
Check the Storage location field first — it should show a path physically on your device. Then let a short test meeting end on its own and look in that folder. Zoom's default names are video[random number].mp4 for audio/video and audio[random number].m4a for audio-only, so a folder holding those is a folder where conversion completed.
In the desktop app there is a second tell: "Recordings not yet converted will display Convert next to the meeting topic." If nothing says Convert, nothing is stuck.
FAQ
Can I set Zoom to record straight to an external hard drive? The client will let you choose the path, but Zoom advises against it: external storage and network-attached storage "can result in data loss," and the separate note on recording locations says an external drive "may cause issues with saving and converting the computer recording."
Is a OneDrive or Google Drive folder safer than a USB drive? Zoom lists them in the same sentence as external drives and network storage — "a cloud syncing folder (such as Dropbox, Google Drive, or One Drive), an external drive, or network storage device" — and recommends a local drive over all of them.
Can Zoom support recover my corrupted local recording? No. Zoom states that local recordings exist only on the computer where they were created, that it does not retain a copy, and that it cannot recover a lost local recording.
Is it safe to move the finished MP4 to an external drive afterwards? Zoom's documentation doesn't state this either way — its storage warning is about the recording location you set in the client, not about copies made after conversion, so check the official documentation before relying on anything more. The one nearby constraint Zoom does state is about devices, not drives: "To play a computer recording, you must be accessing it from the same device on which it was recorded," repeated elsewhere as "To access a computer recording file, you must be on the same device where the recording was made." That is the sentence that explains why a Zoom folder copied to a second computer won't play.
Why does Zoom warn about network connections in a path error? Its troubleshooting page pairs them — "Invalid working path/folder (sometimes, an invalid network connection may appear with this warning too)" — but does not explain the relationship. The documented action either way is to set a valid local path.
Recording somewhere else and still landing on a broken file? More recording fixes covers the neighbouring failures. All quotations above are from Zoom's support articles on computer recording, recording FAQs, and missing recordings, checked 19 September 2026 — verify against the official documentation before relying on them.
