This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
plugin-types directive restricts the set of plugins that
can be embedded into a document by limiting the types of resources which can be loaded.
- the element to load does not declare a valid MIME type,
- the declared type does not match one of specified types in the
- the fetched resource does not match the declared type.
|Directive type||Document directive|
||No. Not setting this allows anything.|
One or more MIME types can
be set for the
Content-Security-Policy: plugin-types <type>/<subtype>; Content-Security-Policy: plugin-types <type>/<subtype> <type>/<subtype>;
- A valid MIME type.
To disallow all plugins, the
object-src directive should be set to
'none' which will disallow plugins. The
is only used if you are allowing plugins with
object-src at all.
<meta http-equiv="Content-Security-Policy" content="object-src 'none'">
The content security policy
Content-Security-Policy: plugin-types application/x-shockwave-flash
will allow to load flash objects:
<object data="https://example.com/flash" type="application/x-shockwave-flash"></object>
To load an
<applet> you must specify
Content-Security-Policy: plugin-types application/x-java-applet
|Content Security Policy Level 2
The definition of 'plugin-types' in that specification.
BCD tables only load in the browser
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.