Chrome Native Messaging lets a Chrome extension exchange messages with a separately installed native application on Windows. The extension does not run Windows commands itself: Chrome launches a registered host process and carries messages between the extension and that host over stdin and stdout. For an MV3 extension, a popup or service worker can initiate the native connection; a content script must relay its request through the service worker.
This guide uses Spec-Driven Development (SDD) to define that integration before implementing it. It lays out the extension, host, host manifest, and Windows registration contracts, then explains the protocol and the choices to make before writing a Node.js host. Chrome’s documentation establishes the Native Messaging contract, but the sources cited here do not provide a verified Node.js host implementation, so no untested code is presented as working.
What you are building
The integration has two separately installed parts: an MV3 extension and a local native host. Chrome brokers communication between them after the host has been registered with Windows and its manifest authorizes the extension’s exact origin. The documented interface is Native Messaging, which Chrome describes as allowing extensions to exchange messages with native applications through an API similar to its other message-passing APIs. Chrome’s Native Messaging documentation
- The user triggers an action in the extension’s popup, options page, or another extension page.
- If the action begins on a website, a content script sends an internal message to the extension service worker.
- The service worker calls Chrome’s Native Messaging API. It needs the
nativeMessagingpermission. - Chrome finds the registered host manifest, checks that the extension origin is allowed, and launches the host as a separate process.
- The extension and host exchange length-prefixed JSON messages over stdin and stdout.
The host is not a general-purpose command channel. Specify a small set of permitted actions, validate every request, and have the host return structured success or error responses. Do not accept arbitrary commands from extension messages.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- Spacious Design: Measuring 21.1" wide and 14.1" deep, our lap desk comfortably fits most laptops up to 15.6". Extra room for accessories ensures convenience.
- Enhanced Functionality: Packed with handy features, including a 5x9" precision tracking mouse pad and a built-in phone slot for seamless work or video calls. Plus, enjoy ergonomic support with the integrated cushioned wrist rest.
- Cool Comfort: Enjoy a stable surface with our lap desk's dual bolster cushion, designed for comfort and airflow, keeping your lap cool during extended use.
- Durable Surface: Work with confidence on our lap desk's solid surface, featuring a sleek black carbon color, ensuring optimal air circulation to prevent your laptop from overheating.
- On-the-Go Convenience: With an integrated handle and lightweight design (2.8 lbs), our lap desk is portable for travel or moving around the house, offering flexibility in any space.
Turn the integration into SDD artifacts
Spec-Driven Development makes the contract and intended behavior reviewable before implementation. GitHub Spec Kit presents a workflow of Specification → Plan → Tasks → Implement; its quickstart separates establishing principles, describing what to build, and subsequent stages, with review between steps. Spec Kit is one concrete example, not the only way to practice SDD. GitHub Spec Kit documentation GitHub Spec Kit quickstart
1. Set principles and boundaries
Write down the rules the implementation must preserve. For a local integration, useful principles include minimum necessary permissions, validation of every message, a narrow allowlist of local actions, and error diagnostics that do not expose sensitive data. Treat these as project-specific guardrails, not as a normative Spec Kit checklist.
2. Specify observable behavior
Describe the user action and the request/response contract before choosing implementation details. For each supported action, record its fields and types, expected response, possible errors, and what the user sees when the host is missing or cannot be reached. Specify which extension context initiates the message and how a content script, if involved, relays it to the service worker. State whether the application needs a persistent connection or a one-off request.
Rank #2
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
3. Plan the components and installation
Break the design into the MV3 extension, Node.js host, independent Native Messaging host manifest, Windows registration, packaging, and install/uninstall behavior. Decide whether registration is for the current Windows user or all users. Make the origin authorization and executable location explicit in the installation plan.
4. Create testable tasks, then implement
Turn each part of the contract into reviewable work. Tasks should cover message framing, the exact allowed extension origin, missing host registration, malformed JSON, host termination, and the expected response. Implement against the approved artifacts, check that behavior still matches them, and update the specification when a deliberate design change alters the contract. These steps apply Spec Kit’s documented phases to Native Messaging; they are practical project guidance, not a checklist published verbatim by GitHub.
Choose the extension’s Native Messaging API
Chrome provides two approaches. Select based on whether a connection should stay open or each action should be a separate request. Chrome documents both Native Messaging methods and their process behavior.
Rank #3
- Note: Not suitable for MacBooks released after 2023 or devices with a protruding front camera; Not applicable to full-screen or notch-style tempered glass screen protectors; Do not use on the rear camera of the phone.
- 💻 Why Do You Need a Webcam Cover Slide? — Safeguard your privacy by covering your webcam with our reliable webcam cover when not in use. Don't let anyone secretly watch you. Stay protected!
- ✅ Thin & Stylish — Enhance your laptop's functionality and aesthetics with our 0.027" ultra-thin webcam covers. Seamlessly close your laptop while adding a touch of sophistication.
- ✅ Fits Most Devices — Compatible with laptops, phones, tablets, desktops! Keep your privacy intact on Ap/ple, Mac/Book, iPh/one, iP/ad, H/P, L/novo, De/ll, Ac/er, As/us, Sa/msung devices.
- ✅ 365 Days Protection — Our upgraded 3.0 adhesive ensures a strong hold that won't damage your equipment. Experience reliable, long-term privacy protection day in and day out.
| Method | Process behavior | Use when |
|---|---|---|
runtime.connectNative() |
Chrome starts the host and keeps it running while the returned port remains open. | The extension needs an ongoing two-way conversation or multiple messages over one connection. Account for the host’s lifetime and close the port when the connection is no longer needed. |
runtime.sendNativeMessage() |
Chrome starts a new host process for each message; the first host response is used for that call. | The interaction is a discrete request and response rather than a continuing session. |
In MV3, the native call must originate in an extension page or the service worker, not directly from a content script. If a web page interaction triggers the request, pass a narrowly defined internal message to the service worker and validate it there before contacting the host.
Keep the two manifests distinct
The extension’s MV3 manifest.json and the native host manifest are different files with different jobs. The extension manifest declares its Native Messaging permission. The host manifest tells Chrome which local executable to launch and which extension origins may use it. Chrome documents the host manifest fields as name, description, path, type, and allowed_origins. Native host manifest requirements
Recommended Free Tools
nameis the host name used by the extension when connecting and in the Windows registration path.descriptiondescribes the host.pathidentifies the executable. On Windows, Chrome permits a path relative to the manifest’s directory; an installer should nevertheless make the executable location unambiguous and verify it.typemust bestdio.allowed_originslists authorized extension origins. Use the extension’s exact origin; wildcards are not supported.
Keep the host name identical in the extension API call and the registry key. Do not copy an extension ID from a sample: authorize the ID for the extension you actually distribute.
Rank #4
- Anti-Slip Surface - Transform your laptop into a mobile workstation with the AboveTEK portable laptop lap desk. The anti-slip surface provides a strong grip for laptops up to 15.6 inches(Diagonal), while the double rubber strip on the bottom ensures a stable display or typing experience on your lap, couch, or bed.
- Retractable Mouse Pad - Retractable laptop mouse pad extends on both directions for the left/right handed with elevation along the edges for stopping mouse from falling off. The size of laptop tray is 14" X 9.7" and the size of mouse pad is 7.4" X 6.1".
- Effective Heat Shield - The effective heat shield made of sturdy and thick material protects your laptop from overheating. Prioritizes your comfort and safety, an ideal lap pad or board for working anywhere.
- EASY to Carry and Store - With an ergonomic and simplistic design, the lap desk is portable to store in a backpack. Only 15" in size, 2.2 lb of weight and with slim 0.6 inch thickness, it is ready to be easily carried around.
- Widely Applicable - The smooth platform accommodates laptops and tablets up to 15.6 inches(Diagonal), making it a versatile accessory and one of the best gifts for mom, dad, students and professionals. Perfect for use as a laptop bed tray or tablet holder anywhere at home, library, or park.
Register the native host on Windows
Chrome locates a native host through a Windows registry key named for the host. The key’s default value points to the full path of the host manifest JSON file, not directly to the executable. Chrome documents registration for the current user under HKEY_CURRENT_USERSoftwareGoogleChromeNativeMessagingHosts<host_name> and system-wide registration under the equivalent HKEY_LOCAL_MACHINE path. Chrome’s Windows registration guidance
| Registry scope | Effect | Installer consideration |
|---|---|---|
HKCU |
Registers the host for the current Windows user. | Chrome’s official sample uses this scope. The sample’s Python requirement belongs to that example, not to Native Messaging generally or to a Node.js host. Official Chrome Native Messaging sample |
HKLM |
Registers the host for all users. | Choose this only if the installer is designed for system-wide installation and has the corresponding permissions. |
Installation should place the executable and host manifest at known paths, write the selected registry entry with its default value pointing to the manifest, and ensure the manifest’s path resolves to the executable. Uninstallation should remove the registration and files installed by that product, without deleting unrelated host entries.
Implement and protect the message protocol
Native Messaging is not newline-delimited JSON. Chrome’s protocol uses JSON encoded as UTF-8, preceded by a 32-bit message length in the native byte order. Chrome allows a maximum of 1 MB for a message from the host to Chrome and 64 MiB for a message from Chrome to the host. These are protocol limits, not recommended payload sizes. Chrome protocol and message-size limits
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBest Value
- Spacious Design: Measuring 21.1" wide and 12" deep, our lap desk comfortably fits most laptops up to 15.6". Extra room for accessories ensures convenience.
- Enhanced Functionality: Packed with handy features, including a 5x9" precision tracking mouse pad and a built-in phone slot for seamless work or video calls. Plus, enjoy laptop support with the integrated device ledge.
- Cool Comfort: Enjoy a stable surface with our lap desk's dual bolster cushion, designed for comfort and airflow, keeping your lap cool during extended use.
- Durable Surface: Work with confidence on our lap desk's solid surface, featuring a blush pink color, ensuring optimal air circulation to prevent your laptop from overheating.
- On-the-Go Convenience: With an integrated handle and lightweight design (2.14 lbs), our lap desk is portable for travel or moving around the house, offering flexibility in any space.
- Reserve stdout for protocol frames. A log line or other unexpected output can be interpreted as protocol data and break communication. Send diagnostics to stderr.
- Validate at both boundaries. The extension should validate incoming host responses; the host should parse and validate each request, reject unsupported actions and fields, and avoid exposing arbitrary local capabilities.
- Handle failures explicitly. Cover an unregistered host, an origin that is not authorized, an invalid manifest or executable path, malformed messages, a process that exits unexpectedly, and a connection that closes before a response arrives.
- Keep user-facing errors actionable. Distinguish “host not installed or registered” from “request failed” where the extension can do so, while keeping sensitive implementation details in stderr diagnostics rather than user-visible messages.
Validate the installation and troubleshoot failures
When connection setup or messaging fails, check the values that join the extension, manifest, and registry together before debugging application logic.
- Confirm the host name passed to
connectNative()orsendNativeMessage()exactly matches the host manifest name and the Windows registry subkey. - Confirm
allowed_originscontains the exact origin for the installed extension. A different ID or wildcard will not authorize it. - Confirm the registry key is under the intended user or machine scope and its default value points to the actual host manifest JSON file.
- Validate that the host manifest is valid JSON, uses
stdio, and has apaththat resolves to the intended executable. - Check that the host reads and writes the documented length-prefixed protocol, and that stdout contains no diagnostics.
- Reproduce the failure for the selected lifecycle: a persistent port for
connectNative(), or a fresh host process per call forsendNativeMessage().
Chrome identifies an unregistered host name, an unauthorized origin, and protocol errors among common Native Messaging failures. Chrome troubleshooting notes
What this establishes for a Node.js host
The documented Chrome contract tells a Node.js process what it must interoperate with: host registration, an authorized origin, a separate process, and length-prefixed UTF-8 JSON on standard input and output. It does not, by itself, supply a Node.js implementation, explain Node-specific binary stream handling, or define a Windows installer. The official Chrome sample is an installation example that uses Python; that runtime is not a general Native Messaging requirement. Consequently, treat Node.js framing and Windows packaging as implementation work that must be checked against current Node.js documentation and tested on the Windows versions you support before shipping. Do not assume that newline-based JSON or ordinary console logging is compatible with Chrome’s framing rules.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
