In Google Chrome, plugins and extensions are accessed through the extensions page at chrome://extensions, where each item can be toggled on or off, configured further options, or removed. This guide explains how to open the extensions page, enable developer mode for sideloading unpacked extensions, manage individual plugins, and understand enterprise-managed restrictions that can hide or control access. The steps below remain reliable for Chrome versions released around 2018 and continue to apply to current stable channels, helping you verify installed items and adjust settings with confidence.
Open the Chrome extensions page
The central place to manage nearly all plugins and extensions is the Chrome extensions page. To open it, type chrome://extensions directly into the address bar and press Enter. This page lists all installed extensions, showing their enabled status, icons, and version numbers. On this page you can toggle extensions on or off, click details for per-site permissions, and use bulk management utilities. If the address bar obscures the page, click the address bar or press Ctrl+L (Windows/Linux) or Command+L (Mac) to focus it. The extensions page is the primary control panel for plugins added from the Chrome Web Store as well as sideloaded items.
Understand extension types and terminology
Clarifying terminology reduces confusion when you learn how to access chrome plugins 2018 style and beyond. Chrome distinguishes between extensions, which primarily modify functionality and UI, and plugins, a term often used for NPAPI/Pepper-based content such as Flash or PDF viewers that run separate processes. As of 2018, NPAPI support was largely removed except for specific enterprise-managed plugins, and Pepper-based plugins remained limited. Most user-installed items are extensions loaded from the Chrome Web Store or unpacked from a developer directory. Knowing whether you are working with an extension or a legacy plugin influences where and how you access its settings.
Types comparison
| Item | Definition (2018) | Access method |
|---|---|---|
| Extension (from Web Store) | Signed package distributed by Google, installed from chrome.google.com/webstore | chrome://extensions, with per-site exceptions under the extension’s details |
| Unpacked extension | Developer folder loaded for testing; changes reflect on reload | chrome://extensions > Load unpacked, managed via the extensions page |
| Plugin (Pepper/PPAPI) | MIME-handler such as built-in Flash or PDF viewer; runs in a separate process | chrome://plugins (deprecated in later versions), handled through chrome://settings/content or enterprise policies |
| Legacy NPAPI | Older plugin API deprecated after Chrome 45; allowed via enterprise policy until late 2018 | chrome://flags or enterprise policy, generally not recommended |
Access by URL and shortcuts
Use chrome://extensions to reach the extensions page directly. For convenience, you can also open it from the Chrome menu: More tools > Extensions. On that page, the interface includes a toggle for Developer mode; turning it on unlocks controls for loading unpacked extensions and inspecting background pages. If you manage devices, note that certain URLs such as chrome://management handle enterprise add-ons, while chrome://settings manages content settings like camera and microphone access that some plugins control.
Quick access methods
- Type chrome://extensions in the address bar and press Enter.
- Open the Chrome menu (three vertical dots) > More tools > Extensions.
- Pin the Extensions page to your taskbar or shelf for frequent access.
- Use a custom search engine shortcut (e.g., chromeext://) if configured.
Load unpacked extensions (Developer mode)
Developer mode on the extensions page allows you to load unpacked extensions for testing or using local builds. To use it, open chrome://extensions, toggle Developer mode in the top-right, then click Load unpacked and select the extension folder. This method is common in 2018 workflows for developers who want immediate feedback without publishing to the Web Store. Extensions loaded this way display the same toggles and options as store-installed items, but they are not sandboxed as strictly and may require additional permissions scrutiny.
Sideloading risks
Loading unpacked extensions bypasses the Web Store review, so only load items you trust. Potential risks include overly broad permissions, telemetry, or ad injection. Confirm the source, review the permission list on install, and keep developer mode off when not in use to prevent accidental changes. If you are in an enterprise, consult policies before sideloading, since admin settings can restrict this capability.
Manage permissions and details
On the extensions page, each entry can expand to show Site access and additional options. Site access determines whether the extension can read and change data on all sites, on specific sites, or on no sites depending on its needs. You can also remove an extension, view its storage usage, and reset site access per domain. For plugins handled as content handlers (e.g., Flash or PDF), adjust behavior via chrome://settings/content, where you set defaults for PDF downloads and camera/microphone usage by site.
Handle managed policies and restrictions
Organizations using Chrome Enterprise or device-managed profiles can restrict how to access chrome plugins 2018 settings. Policies can hide the extensions page, block installation of non-whitelisted extensions, or enforce specific plugin behavior. To inspect policy settings, open chrome://policy while signed in as the managed user. Common entries related to extensions include ExtensionInstallForcelist, ExtensionBlocklist, and PluginAllowedSources. If a policy restricts your access, contact your administrator; locally toggling Developer mode or installing extensions may be prevented until the policy is updated or removed.
Policy checklist
- Visit chrome://policy to see active policies affecting extensions.
- Check with your admin before forcing local installs in managed devices.
- Understand that user-level changes can be overridden by device policies on shared machines.
Troubleshooting and verification
When verifying that an extension is active or diagnosing issues, use these steps. First, confirm the extension appears on chrome://extensions and is toggled on. If it is missing, check whether it was removed, disabled by policy, or failed to install due to version incompatibility. Clear extension data cautiously via the trash bin on the extensions page, and avoid enabling developer mode unless necessary. For plugin-related problems, such as Flash not running, visit chrome://settings/content, verify the plugin is allowed, and ensure it is enabled in the browser’s content settings. Keep Chrome updated; security and stability updates frequently change how plugins and extensions are handled.
Troubleshooting steps
- Open chrome://extensions and verify the item is enabled.
- Check chrome://policy for restrictions if installation is blocked.
- For content plugins, review chrome://settings/content handling.
- Update Chrome and retry; if issues persist, collect version info from chrome://version.
- When in doubt, create a new Chrome profile to test if the issue is profile-specific.
Conclusion and best practices
Accessing and managing Chrome plugins in 2018 centers on chrome://extensions for most extensions and chrome://settings/content for plugin-related behaviors. Stay cautious with Developer mode, prefer Web Store items when possible, verify sources before loading unpacked extensions, and respect enterprise policies that may limit your ability to change settings. These evergreen practices help you maintain control over your browser’s plugin ecosystem safely and consistently across Chrome versions.