CRDOWNLOAD File Troubleshooting: How to Resume, Recover, or Safely Delete Chrome Partial Downloads (Plus eDiscovery Tips)

Takeaway: A .crdownload file is Chrome’s “download in progress” placeholder. Usually, you just need to let the download finish or resume it. If it’s stuck, you can troubleshoot it, clean up leftovers, and if you see CRDOWNLOAD files in a legal dataset, remove them so you’re not reviewing incomplete junk.

Quick fixes (start here)

If you’re staring at a .crdownload file and thinking, “Great… what now?”, here are the fastest answers.

If the download is still running

Do nothing. Chrome will automatically rename the file when the download completes.

If the download failed or is stuck

1. Open Chrome’s downloads page:
   • Windows: Ctrl + J
   • Mac: Command + Shift + J
2. Find the download and click Resume (or Retry).

If you only need what’s already downloaded

Sometimes, especially with audio/video—you can try removing the .crdownload extension and opening the file. It won’t always work, but it’s a quick test when you’re in a pinch.

If you’re seeing lots of CRDOWNLOAD files that never finish

That usually points to a bigger problem: an unstable internet connection, low disk space, permission issues, or a Chrome hiccup. The sections below walk through the common fixes.

What a .crdownload file means (quick definition)

A .crdownload file is the temporary “download in progress” version Chrome creates while it’s still pulling a file onto your computer. It’s basically Chrome’s way of saying: “Not done yet”.

You’ll usually spot it in your Downloads folder as:

• filename.pdf.crdownload
• or sometimes filename.crdownload

Once the download finishes, Chrome automatically renames it to the correct file type (PDF, DOCX, MP3, ZIP, etc.).

If you want a deeper understanding of these files, what triggers them, why they get stuck, and how they behave, check out our detailed post on CRDOWNLOAD files here.

How to resume a stalled download in Chrome (Windows + Mac)

Step 1: Open the download manager

• Windows: Ctrl + J
• Mac: Command + Shift + J

Step 2: Resume or retry

• Click Resume if it’s available.
• If you only see Retry, Chrome needs to restart the download.

Step 3: If it keeps failing, check the usual suspects

This is where most “stuck CRDOWNLOAD” problems come from:

• Not enough disk space (large files fail silently more often than you’d expect)
• Unstable internet (especially with big downloads)
• Folder permissions (Chrome can’t write to the Downloads folder)
• Outdated Chrome (updating fixes a surprising number of download issues)

Can you open or convert a CRDOWNLOAD file?

Most of the time, no, because a CRDOWNLOAD file is incomplete by definition.

That said, there are a couple of practical things you can try.

Option 1: Rename it (works sometimes)

If you have demo.mp3.crdownload, try renaming it to demo.mp3 and opening it. If enough of the file is downloaded, it might open—maybe fully, maybe partially.

Option 2: Open it in the target app (hit-or-miss)

Some apps can open partially downloaded media or archives, but it’s not something you can rely on for documents.

Option 3: Conversion isn’t really the solution

Because the file isn’t complete, “converting” it won’t fix the core issue. The reliable path is still:

• Resume the download, or
• Re-download the original file

What does “Unconfirmed ####.crdownload” mean?

Chrome sometimes assigns temporary names, such as “Unconfirmed 12345.crdownload”, while a download is in progress.

Same idea, different label:

• It’s still a partial download
• If it completes, it should rename itself to the correct filename

If it never completes, you’ll typically see it stick around as an “Unconfirmed” CRDOWNLOAD file.

When it’s safe to delete CRDOWNLOAD files (and how)

Safe to delete when:

• You cancelled the download
• The download failed, and you’re going to re-download
• You’re cleaning up old leftovers you don’t need
• The file contains something sensitive and shouldn’t remain on disk

How to delete them cleanly

1. Cancel the download in Chrome (or close it).
2. If your computer says the file is “in use”, Chrome is still holding it—close Chrome and try again.
3. Delete the .crdownload file from your Downloads folder.

CRDOWNLOAD files in eDiscovery: what to do before review

CRDOWNLOAD files show up in eDiscovery collections more often than you’d think—usually because someone swept up their Downloads folder during collection or preservation.

Why CRDOWNLOAD files are a problem in review

They’re rarely helpful. In most cases:

• The content is incomplete
• The file is just an artifact of a failed or unfinished download
• You end up spending time and storage on something that isn’t the “real” document

What to do instead (practical + defensible)

1. Treat CRDOWNLOAD files as artifacts, not primary evidence.
2. Identify what the actual intended file was (the finished PDF/DOCX/ZIP/media file).
3. If it matters to the case, re-collect the completed file from the source.
4. Exclude or tag CRDOWNLOAD artifacts during QC to keep your review set clean.

Where GoldFynch fits in

Once you’ve got the right files (not half-downloaded leftovers), you want a workflow that makes it easy to:

• search and filter quickly
• tag and organize by issue or custodian
• redact, QC, and produce defensibly

That’s precisely where GoldFynch helps—especially when you want a clean, review-ready dataset.

Try GoldFynch for free or schedule a demo to see how review and production should feel when the data is actually ready.

FAQ

What is a CRDOWNLOAD file?

A temporary placeholder file Chrome creates while a download is in progress. When it finishes, Chrome renames it to the final file extension.

How do I remove .crdownload files?

Let the download finish (Chrome removes it automatically) or cancel the download and delete the leftover CRDOWNLOAD file.

Can I open a CRDOWNLOAD file?

Not usually. Sometimes, renaming it works when the file is mostly downloaded, especially for media files.

Why do CRDOWNLOAD files keep showing up and never finish?

Common causes include an unstable internet connection, insufficient disk space, Chrome permissions, or a browser issue that can be fixed by updating Chrome.