v147 · proposed IWA API · member reference

WebPrinter

A printer handle returned by getPrinters(). It exposes an explicit cache read, an asynchronous capability refresh, and asynchronous PDF job submission.

Proposal and implementation differ from the old overviewChromeStatus currently records this API as Proposed, not shipped. This reference follows the current WICG IDL and Chromium source; test in the intended IWA configuration and feature-detect rather than relying on the v147 label.

Syntax

interface WebPrinter {
  WebPrinterAttributes cachedAttributes();
  Promise<WebPrinterAttributes> fetchAttributes();
  Promise<WebPrintJob> submitPrintJob(USVString jobName, Blob documentData,
                                        WebPrintJobTemplateAttributes attributes);
}

Inputs

Instances come only from enumeration; there is no constructor. See the three member routes for parameter shapes.

Outputs

Methods return attributes or a job handle. They do not guarantee a printer has finished printing.

Errors

Member-specific errors are documented locally. Calls after context shutdown can throw NotSupportedError in Chromium.

Context and permission

The IDL requires a secure, isolated context. The specification also defines the web-printing Permissions Policy with default allowlist self; Chromium additionally checks an isolated context and cross-origin isolation before getPrinters(). The current proposal requires express, origin-specific consent triggered by enumeration. The exact chooser scope, persistence, and whether a later operation prompts again remain user-agent UX, not a settled web contract.

Lifecycle, cancellation, and cleanup

Initial cache contains name and opaque ID. fetchAttributes() replaces it. Handles have no specified long-term persistence or reconnect behavior; enumerate again after a configuration change.

Examples

const [printer] = await window.printing.getPrinters();
if (!printer) throw new Error("No printer available");
const attributes = await printer.fetchAttributes();
console.log(attributes.documentFormatSupported);

Browser compatibility

Current public compatibility evidence (checked 2026-07-26)
Runtime	Status	Evidence
Chrome (general)	Proposed and not released. ChromeStatus lists I2S desktop target 147, which is not release proof. Do not infer general desktop Chrome support.	ChromeStatus
Current Chromium service	Implemented only when built with `IS_CHROMEOS && USE_CUPS`; otherwise `getPrinters()` has no service and throws `SecurityError`.	Chromium manager implementation
Android / mobile	ChromeStatus Android is `null`; no public mobile release exists. The current ChromeOS+CUPS-only service path does not expose the service on Android.	ChromeStatus; implementation guard
Firefox	No signal; no BCD member record found.	ChromeStatus position; BCD API data
Safari	No signal; no BCD member record found.	ChromeStatus position; BCD API data
webstatus.dev	No feature entry found for this query; this is not proof of absence from browsers.	webstatus query

Security and privacy

Printer names, IDs, capabilities and state can fingerprint a device and reveal printing activity. A compromised IWA could create unwanted jobs or denial of service. Minimize enumeration and polling, do not expose attributes to untrusted content, validate documents before submitting, and offer an app-level confirmation/audit trail. The spec requires isolation and consent; it does not make printer information non-sensitive.