Version: Unity 6.7 Alpha (6000.7)
Language : English
Configure WebGPU API usage
WebGPU Device Filter features and limits

WebGPU Device Filter asset reference

The WebGPU Device Filter asset includes filter lists each consisting of the following set of parameters. Specify values for these parameters to define WebGPU API usage for a browser or set of browsers.

Property Description
Browser Engine The browser engine that implements WebGPU, independent of the browser brand. This is the recommended way to filter, because a single entry matches every browser built on that engine. Select Chromium-based (Chromium/Blink, such as Chrome, Edge, or Opera), Safari-based (WebKit, including all browsers on iOS/iPadOS), Firefox-based (Gecko), or Do Not Care to ignore the engine.
Engine Version The engine version to compare against. Use the same format as Browser Version. This compares against the underlying engine version, not the browser’s brand version - for a Chromium browser this is the Chromium version.
Browser Name A specific browser brand name, matched with a regular expression. For example, Chrome, Firefox, or Edge. Browser Name rules take precedence over Browser Engine rules, so you can allow a whole engine and still make an exception for a specific brand.
Browser Version The version of the browser brand (used with Browser Name). Enter the version number in the following format:
MajorVersion.MinorVersion.PatchVersion.MinorPatchVersion where MinorVersion, PatchVersion, and MinorPatchVersion are optional. For example, 135.0.13044.
Note: You can’t use regular expressions for this parameter.
Device Type The type of device, such as Mobile or Desktop. You can use this parameter to limit the use of WebGPU on mobile devices. However, note that this value is loosely defined by browsers so it’s not an entirely reliable metric. Select Mobile, Desktop, or Do Not Care. Select the Do Not Care option to tell the filter to ignore the Device Type parameter.
Required Features A list of WebGPU extension features your device must support to use WebGPU. To add a required feature, select Add Feature, then expand the dropdown and select your preferred feature. Select - to remove a feature from the list. For a full list of features, refer to WebGPU Device Filter features and limits.
Limits A list of required capability limits for WebGPU. Select Add Limit to add a new limit to the list. For a full list of limit types, refer to WebGPU Device Filter features and limits. When you add a new limit to the list, you get the following options:
  • Limit: Choose a limit type, for example MaxSampledTexturesPerShaderStage.
  • Comparator: The type of comparison to make between the limit type and the value. For example, Less Than Or Equal To.
  • Value: The number to check against. For example a value of 16.
In those examples, the filter is applied if WebGPU has a MaxSampledTexturesPerShaderStage limit of 16 or less.

Note: Regular expressions use ECMAScript format for the supported properties. However, the Unity Editor and runtime use different regex engines that both support ECMAScript. The Unity Editor uses the .NET regular expression engine with the RegexOptions.ECMAScript flag, while the runtime uses the C++ modified ECMAScript by default. The Editor validation confirms valid regular expression syntax, but the expression might produce different filtering behavior between the Editor and runtime. To verify runtime behavior, test the device filtering on actual devices.

Additional resources

Configure WebGPU API usage
WebGPU Device Filter features and limits