pluginhost64.exe

Plugin Host 64-bit (Chrome/Chromium)

CPU Usage

N/A

Memory

N/A

Location

N/A

Publisher

N/A

Best Practices

Keep Chrome updated, monitor plugin usage, and avoid terminating pluginhost64.exe unless Chrome is closed. Use Chrome Task Manager to identify heavy plugin activity and disable plugins you do not need.

Recommended Actions

[object Object],[object Object],[object Object],[object Object]

What is pluginhost64.exe?

Pluginhost64.exe is a 64-bit Windows process used by Chrome/Chromium-based browsers to host plugin content in a separate process. This isolation helps improve stability and security by containing plugin crashes and reducing cross-tab interference. It typically resides inside the Chrome application folder and starts on-demand when a page requires plugin content.

Pluginhost64.exe runs a dedicated 64‑bit plugin host within Chrome, isolating plugin code from the main browser process. It supports PPAPI/NPAPI plugins and launches only when a page requires plugin content, helping stability and security during plugin-heavy sessions.

Is pluginhost64-exe Safe?

pluginhost64.exe is a legitimate Windows process used by Chrome to host 64-bit plugins. When located in the official Chrome installation directory and signed by Google, it is considered safe and integral to the browser’s plugin handling. Misplaced copies or unsigned variants can indicate tampering, so verify the path and signature before relying on it.

Is pluginhost64-exe a Virus?

While pluginhost64.exe is normally safe, cybercriminals may disguise malware as a plugin host file to trick users. If you observe unusual CPU usage, a suspicious location outside the Chrome folder, or a very large or mismatched file size, treat it as a potential threat and perform a full malware scan. Always verify the digital signature and source before acting.

How to Verify Legitimacy

Check File Location: Confirm the executable is within a Chrome application folder (for example, C:\Program Files\Google\Chrome\Application).
Verify Digital Signature: Open Properties -> Digital Signatures and ensure the signer is Google Inc. with a valid certificate.
Check File Hash: Compute the SHA-256 hash of pluginhost64.exe and compare it against the official Chrome release hash from Google.
Scan for Malware: Run a malware scan with Windows Defender or another reputable antivirus to rule out tampering or infection.

Red Flags: If pluginhost64.exe is outside the Chrome folder, unsigned, renamed, or unusually large/malformed, stop using Chrome and run a malware check. Do not ignore repeated crashes or suspicious network activity linked to the process.

Why is it Running?

Reasons it's running:

Hosts 64-bit plugins on demand: Chrome loads 64-bit plugins in a dedicated host (pluginhost64.exe) only when a page requires plugin content, reducing unnecessary overhead in empty tabs.
Improves stability through isolation: Separating plugin code from the main browser process prevents a plugin crash from taking down the entire tab or browser session.
Supports NPAPI/PPAPI plugin ecosystems: The host supports legacy NPAPI and PPAPI plugins, enabling features like embedded multimedia and document viewers when those plugins are active.
Memory management and sandboxing: Pluginhost64.exe helps enforce sandbox boundaries, limiting plugin access to system resources and protecting the rest of Chrome from exploits.
Lifecycle tied to plugin usage: The process is spawned and terminated as plugin content is loaded or unloaded, aligning resource use with actual browsing activity.

Can I disable pluginhost64-exe?

Common Problems

Common Causes & Solutions

Active plugins (e.g., embedded viewers) are being processed by the host.: Update Chrome to the latest version and disable the plugin in use, or reload the page with plugins disabled via chrome://settings.
A plugin within Chrome is unstable or incompatible with the current browser version.: Update Chrome, disable the problematic plugin, or reset Chrome flags if specific plugins are no longer needed.
Corrupted Chrome installation or partial update.: Repair or reinstall Google Chrome from the official site; ensure the file exists in C:\Program Files\Google\Chrome\Application.
False positive or detection of a modified binary.: Update antivirus definitions, verify the signature of pluginhost64.exe, and consider whitelisting the Chrome application folder after verification.
Background plugin activity or scheduled plugin loads.: Check Chrome task manager, review extensions, and ensure no pages triggering plugins are open in background sessions.
Malicious file renamed to pluginhost64.exe in non-Chrome directories.: Run full system scan, verify digital signature, and locate the executable within the Chrome directory before trusting it.

Frequently Asked Questions

What is pluginhost64.exe and why is it running on my PC?

Pluginhost64.exe is Chrome's 64‑bit plugin host process. It starts when a web page requires a plugin (PDF viewer, embedded media, etc.) to run in isolation from the main browser tab, improving stability and security.

Is pluginhost64.exe safe to end task?

You can end the process through Task Manager if Chrome is unresponsive, but doing so will close all Chrome tabs and potentially lose data. It is safer to close Chrome completely so the host terminates gracefully.

Why does pluginhost64.exe use CPU when nothing is loaded?

Occasional activity can occur due to background plugin checks, preloading resources, or extensions using plugins. If it stays high without tabs open, run a malware scan and review installed plugins.

Where is pluginhost64.exe located?

The legitimate file typically resides in C:\Program Files\Google\Chrome\Application and is signed by Google. If you see it elsewhere, verify the signature and update or reinstall Chrome.

How can I reduce plugin usage in Chrome to lower resource use?

Disable NPAPI/PPAPI plugins in Chrome settings (chrome://settings/content/plugins) or use extensions that block plugins. This reduces the need for pluginhost64.exe and can improve performance.

Can pluginhost64.exe be a virus and how to verify?

Yes, malware can masquerade as a plugin host. Verify the file path, signature, and hash, and run a full system scan. If verification fails, remove the file and reinstall Chrome from the official source.