Google Chrome Plug-ins: 5 Built-in Tools Explained

The Evolution of Browser Plug-ins in Chrome

Google has expressed a desire to reduce reliance on traditional browser plug-ins. However, Chrome itself incorporates several plug-ins directly into its framework.

A fresh installation of the Chrome browser typically includes at least five distinct plug-ins. These range from the Widevine Content Decryption Module to Native Client.

Chrome's PPAPI Architecture

All of these integrated plug-ins leverage Chrome’s PPAPI (Pepper API) plug-in architecture. This system is designed to be more secure and isolated than older methods.

PPAPI provides a more modern and sandboxed environment for plug-ins to operate within. This enhances the overall security of the browser.

The Phase-Out of NPAPI

The older NPAPI plug-in architecture, which is still supported by browsers like Firefox, is being removed from Chrome.

Google completed the removal of NPAPI support by September 2015. This transition signifies a move towards a more streamlined and secure browsing experience.

This change aimed to improve browser stability and security by eliminating a potential source of vulnerabilities.

Widevine Content Decryption Module

Widevine is a component integrated directly with Chrome, despite its appearance as a third-party installation.

Its primary function is to enable the playback of DRM-protected HTML5 video and audio content within the Chrome browser.

Functionality and DRM Protection

For instance, accessing Netflix’s HTML5 videos through Chrome necessitates the presence of this module.

Disabling Widevine and attempting to stream Netflix content will result in an error message indicating an issue with the Widevine component.

This behavior stems from the operation of HTML5’s “Encrypted Media Extensions” (EME).

EME allows web pages to mandate a small plug-in specifically for DRM handling.

Controversy and Browser Implementation

The implementation of EME has been a subject of debate, notably causing Mozilla Firefox to delay its adoption.

However, a focused plug-in for DRM management is generally preferable to larger, all-encompassing plug-ins.

Consider alternatives like Adobe Flash or Microsoft Silverlight, which handle both DRM and playback.

Activation and Usage

The Widevine module is only activated when encountering a DRM-protected media stream requiring it, such as when viewing Netflix.

Users have the option to disable the module, but doing so will restrict access to DRM-protected media files.

Essentially, it provides a secure pathway for content providers to protect their media while allowing users to enjoy streaming services within Chrome.

Native Client represents a technology developed by Google, designed to empower developers to execute C or C++ code directly within a web browser environment.

This compilation process results in architecture-independent code, capable of functioning on both ARM and conventional Intel x64/x86 processors.

A crucial aspect of Native Client is its inherent security; all code execution occurs within a sandboxed environment.

Key Features and Potential

Theoretically, Native Client facilitates the execution of desktop-level applications, crafted using native code, directly within a web browser.

Performance is a key benefit, with applications expected to run at speeds comparable to their native, non-sandboxed counterparts.

Practical Usage and Examples

Despite its potential, Native Client hasn't achieved widespread adoption, even after several years of availability.

Its most notable applications are found within more sophisticated games available on the Chrome Web Store.

A prime example is the port of the acclaimed game "Bastion" to the Chrome platform, leveraging Native Client technology.

Users can experience Native Client firsthand by installing and launching "Bastion" directly from the Chrome Web Store.

Adobe Flash Player is often discussed in relation to security vulnerabilities. Protecting oneself from these 0-day exploits is a significant concern for many users.

Google Chrome integrates the Adobe Flash Player plug-in directly within the browser. This integration facilitates automatic updates, ensuring users consistently benefit from the newest Flash version through Chrome’s update mechanism.

However, this Flash implementation differs from standalone versions. Google collaborated with Adobe to transition the legacy NPAPI Flash code to the more contemporary PPAPI framework.

This PPAPI version is sandboxed, providing a heightened level of security compared to the conventional NPAPI Flash plug-in commonly found in browsers like Mozilla Firefox. Adobe also provides PPAPI Flash plug-ins for download with Chromium and Opera.

Users of Chrome do not require separate installation, as the browser includes a current, sandboxed Flash version and maintains its updates automatically.

Despite these improvements, enabling click-to-play for Flash is still advisable. This practice enhances browser security and conserves laptop battery life by preventing automatic loading of Flash content.

Furthermore, users retain the option to completely disable Flash within Chrome’s plug-ins settings if they prefer not to utilize it.

This functionality is linked to the Chrome Remote Desktop app, as detailed in a guide for beginners on accessing desktops remotely. The Chrome Remote Desktop Viewer plug-in is a component of the Chrome browser.

It facilitates remote access to your computer from any location. Without installing and configuring the full Chrome Remote Desktop application, this plug-in remains dormant and provides no functionality.

For users concerned about security, the plug-in can be disabled through the chrome://plugins page, though complete removal from the system isn't possible.

Setting Up Remote Access

To enable remote access, install the Chrome Remote Desktop application directly from the Chrome Web Store. This installation establishes a background service on your computer.

This service allows you to connect remotely using the Chrome Remote Desktop app on another Chrome browser, or via dedicated applications available for Android and iOS devices.

This solution offers a user-friendly remote desktop experience, eliminating the need for complex configurations like port forwarding or firewall adjustments.

Chrome PDF Viewer

Related: Discover how to electronically sign PDF documents without the need for printing and scanning.

Google Chrome incorporates an integrated PDF viewing plugin. Upon clicking a PDF link within a webpage, Chrome initiates its streamlined PDF plugin, rendering the PDF directly within your browser tab. This eliminates the necessity for external PDF viewers or the installation of resource-intensive software like Adobe Reader, alongside its associated security updates.

This native viewer also supports the display of PDFs stored locally on your computer. Simply drag and drop a PDF file into Chrome to open it. Alternatively, you can configure Windows to consistently open PDF files using Chrome via a right-click context menu option.

Chrome’s integrated PDF viewer provides essential viewing functionalities. However, more complex operations, such as digitally signing a document, may necessitate a dedicated PDF viewer like Adobe Reader for Windows or Preview on macOS. Consider foregoing Adobe Reader installation if Chrome’s built-in viewer adequately meets your needs.

If you prefer to download PDFs and utilize them within separate applications consistently, the Chrome PDF viewer plugin can be disabled.

Additional plugins may be pre-installed depending on your operating system. These typically originate from the OS or other installed software, rather than Chrome itself.

For instance, macOS versions of Chrome include a "Default Browser Helper" plugin. This component is part of macOS and enables Apple to suggest Safari as your default browser while you are using Chrome – a feature some may find counterintuitive.