The zip file won't open after downloading a CAD block

Start by checking the file actually finished downloading

I've had this happen to me more times than I'd like to admit, you click download, the progress bar looks like it's moving, and then you go to open the zip and Windows or macOS just shrugs at you with some version of "this archive is invalid" or "unable to expand." Nine times out of ten the file simply never finished downloading, and the browser wrote a partial file to disk anyway instead of failing cleanly.

The first thing to check is the file size. A typical block zip on a library like this one is a few hundred kilobytes to a couple of megabytes, so if your downloaded file is sitting at 0KB, or at some oddly small size like 4KB, that's your answer right there, the download got interrupted and you're holding a stub, not a real archive. Delete it and download again, ideally on a stable connection rather than a flaky hotel wifi, because that's where I see this most often.

Match your unzip tool to your operating system

The second most common cause isn't the file at all, it's the tool trying to open it. macOS's built-in Archive Utility is usually reliable, but I've seen it choke on zips that were built with certain Windows compression settings, particularly ones using newer compression methods that older extraction libraries don't recognize. If you're on a Mac and Archive Utility refuses the file, try The Unarchiver, it's free and handles a much wider range of zip variants without complaint.

On Windows it's usually the reverse problem, the built-in "Extract All" is fine for standard zips but can be fussy about long file paths, especially if your Downloads folder is buried several folders deep with a long username. If you're getting a path length error rather than a corruption error, that's not actually a bad file, it's Windows hitting its old 260 character path limit. Moving the zip to somewhere shallow like your Desktop before extracting fixes that instantly.

Try a second tool before assuming the download is bad

Before you conclude the download itself is corrupted, run it through a different extraction tool entirely. 7-Zip on Windows and Keka on Mac are both free and, in my experience, more forgiving than the built-in options, they'll often open a zip that the native tool flatly refuses. If the second tool also fails with the same error, and the file size looks right, then you're probably dealing with a genuinely interrupted or corrupted download rather than a tool compatibility issue, and re-downloading is the fix.

It's also worth checking whether your browser silently appended something to the filename, like .zip.download or .crdownload, which happens when Chrome or Firefox thinks the download is still in progress even though it's finished. Rename the file back to a clean .zip extension and try again before writing it off as broken.

Antivirus and browser security settings can quietly block extraction

Some antivirus tools, and some corporate network filters, will silently strip or quarantine files inside a zip during extraction without telling you clearly what happened, you just end up with an empty folder or a folder missing the DWG file specifically. If you extract the archive and see an image preview but no DWG, or the extracted folder is empty, check your antivirus quarantine or activity log before assuming the download itself was faulty. This is more common on managed work laptops than home machines, so if it only fails on your office computer and works fine at home, that's a strong signal it's a security policy issue rather than the file.

What to do once the zip is open

Once you're in, a typical block zip from this site contains the DWG file itself plus, depending on the product, a preview image and sometimes a DXF alongside it. If you open the folder and see files but the DWG specifically won't open in AutoCAD, that's a separate issue from the zip not extracting, and it usually points to a version mismatch rather than a bad download. For most people though, the zip problem and the DWG-won't-open problem are two different things that get conflated, so it's worth isolating which one you're actually facing before you spend time on the wrong fix, and browsing the furniture and doors sections here shows you the mix of DWG and DXF pairings most products ship with.

A quick isolation test that saves you guesswork

If you want to know for certain whether the problem is your machine or the download itself, the fastest test is trying the same download on a second device, or asking a colleague on a different network to grab the same file and see if it opens for them. If it opens cleanly somewhere else, the fault is local, your antivirus, your extraction tool, or your network connection, and you can rule out the source file entirely.

I'd also flag one thing that trips people up specifically with laptops on a company VPN, some corporate VPNs proxy and rewrite downloads in ways that quietly corrupt binary files like zips and DWGs mid-transfer, without throwing any visible error. If nothing else on this list explains it and you're on a VPN, disconnect it temporarily and try the download again on your normal connection, that fixes it more often than you'd expect, and it's a five second thing to rule out before you go digging any deeper into extraction tools or antivirus logs.

One more macOS specific wrinkle worth knowing about, files downloaded through Safari or Chrome get tagged with a quarantine attribute, com.apple.quarantine, and on rare occasions an aggressively configured Gatekeeper setting will flag an archive built with an unusual compression method as untrusted and quietly refuse to expand it rather than showing you a clear error message. Right clicking the zip and choosing Open, rather than double clicking it, sometimes gets past this because it triggers an explicit user consent prompt instead of a silent refusal, and if that still doesn't help, opening Terminal and running xattr -d com.apple.quarantine followed by the file's path strips the flag entirely, though I'd only reach for that after the simpler fixes above have already come up empty.

If you want a definitive yes or no answer on whether a zip is structurally sound before you even try extracting it properly, both macOS and Linux have a built-in integrity check, open Terminal, navigate to the folder with cd, and run unzip -t followed by the filename, which tests every entry in the archive without actually extracting anything and reports cleanly whether the zip's internal structure is intact. On Windows, 7-Zip's own Test Archive option under the right click menu does the same job, and running that check first saves you from cycling through several extraction tools on a file that a two second integrity test would have told you outright was genuinely broken.