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 Name | Name of the browser. For example, Chrome or Firefox. |
| Browser Version | The version of the browser. 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:
|
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.