How to Disable Scan After Download in Chrome

Google Chrome includes a built-in security feature that automatically scans files after they finish downloading. For most users, this runs silently in the background. But if you've noticed slowdowns after downloads complete, or you're running a managed environment where third-party scanning already handles this job, you may be looking for a way to turn it off.

Here's what's actually happening — and what your options realistically are.

What Is Chrome's Post-Download Scan?

When Chrome finishes downloading a file, it can trigger a Safe Browsing scan to check the file against known malware signatures and suspicious patterns. On Windows, Chrome also integrates with Windows Defender and can hand files off to the operating system's built-in antivirus for a secondary check.

This process happens in two layers:

• Chrome's own Safe Browsing check — compares file metadata and content against Google's threat database
• Windows Security (Windows Defender) scan — triggered when Chrome writes the file to disk and Windows flags it for inspection

These are separate mechanisms, which matters when you're deciding what to disable and how.

Why People Want to Disable It

The most common reasons include:

• Slow post-download behavior — large files or slower drives can make the scan feel like a hang
• Conflicts with enterprise security tools — organizations running endpoint detection software may see redundant or conflicting scans
• Developer workflows — frequent downloads of known-safe build artifacts or packages where scanning adds friction
• Power users with existing AV coverage — those confident their standalone antivirus handles the job

The tradeoff is real: disabling any scan reduces a layer of protection. How much that matters depends entirely on what you download, how often, and what else is protecting your system.

How to Disable Chrome's Safe Browsing Scan

Chrome doesn't offer a single "disable post-download scan" toggle in its standard settings. What you can adjust is the Safe Browsing level, which controls how aggressively Chrome inspects downloads.

Steps:

1. Open Chrome and go to chrome://settings/security
2. Under Safe Browsing, you'll see three options:
   • Enhanced protection — most aggressive, includes real-time scanning
   • Standard protection — balanced, scans known threats
   • No protection (not recommended) — disables Safe Browsing entirely

Selecting No protection stops Chrome from performing its own download threat checks. Google displays a clear warning here for good reason — this removes phishing and malware URL blocking as well, not just download scanning.

If your goal is only to reduce scan friction rather than remove all protection, staying on Standard protection is a meaningful middle ground.

How to Reduce Windows Defender's Post-Download Scanning

If Chrome's Safe Browsing is already off and you're still seeing delays, Windows Defender is likely the source. When Chrome saves a file to your Downloads folder, Windows flags it and Defender scans it automatically.

You have a few options here:

Option 1: Add an Exclusion for the Downloads Folder

1. Open Windows Security → Virus & threat protection
2. Scroll to Virus & threat protection settings → click Manage settings
3. Scroll to Exclusions → Add or remove exclusions
4. Add your Downloads folder as an excluded path

⚠️ This tells Defender to skip scanning anything saved there — including genuinely malicious files. This approach works well in controlled environments (developer machines, sandboxed systems) but is a meaningful risk on a general-use machine.

Option 2: Exclude Specific File Types

Instead of excluding the whole folder, you can exclude specific extensions (like .zip, .dmg, or .iso) if those are the files causing the slowdown. This is a more targeted approach.

Option 3: Disable Real-Time Protection (Not Recommended for Most)

Turning off Defender's real-time protection entirely removes all automatic scanning — including downloads. This is rarely appropriate unless another enterprise-grade solution is actively running in its place.

The Chrome Flag Route 🔧

Some users reference a Chrome flag (chrome://flags) for controlling download scanning behavior. Flags are experimental settings that Google adds, modifies, or removes between versions without notice. Any flag-based workaround that worked in one Chrome version may be gone in the next update.

If you find a relevant flag in your current version, treat it as temporary — not a stable configuration.

Factors That Shape the Right Approach

macOS and Linux Differences

On macOS, Chrome integrates with Apple's Gatekeeper and XProtect rather than Defender. Post-download behavior is shaped by macOS's own security stack, and Chrome's Safe Browsing toggle is still the primary lever available within the browser itself.

On Linux, system-level scanning depends on whatever security tooling is installed — most desktop Linux setups don't have an equivalent to Defender running by default, so Chrome's Safe Browsing is often the only active layer.

What You're Actually Trading Off

Disabling these scans doesn't make Chrome faster at downloading — it only removes what happens after the file lands on disk. The performance difference is most noticeable with large files on machines where Defender's real-time scan creates I/O contention.

The right configuration comes down to how your system is already protected, what you regularly download, and how much friction is actually worth removing given your risk tolerance. Those variables don't have a universal answer — they're specific to your setup. 🔐