<param>: The PARAM Element
Last updated: 2026-10-13
<param>The PARAM Element
Passes parameters (e.g. autoplay, loop) to a plugin embedded by object; must be a child of object.
| Category | Scripts & Embedding |
|---|---|
| Content Model | Flow content |
| Allowed Parents | Any element that accepts flow content |
| Content Tag | Self-closing — no closing tag needed |
| Status | Standard |
📝 Syntax
<param name="autoplay" value="true">
⚙️ Attributes
This element supports the global attributes plus the following:
| Attribute | Value | Description |
|---|---|---|
name | Parameter name. | |
value | Parameter value. |
▶ Example
Edit the code below and see the live result in the playground:
🌐 Browser Support
| Browser | |||||
|---|---|---|---|---|---|
| <param> | ✓ v1 | ✓ v12 | ✓ v1 | ✓ v1 | ✓ v1 |
| Supported in all major browsers | |||||
Tip: param is a void element valid only inside object; rarely used in HTML5 plugin contexts.
❓ FAQ
QIs the param tag still in use?
ANo.
<param> passed parameters to plugins inside <object> — mostly Flash — and was marked obsolete as the plugin era ended; modern browsers basically ignore it.QWhat replaced param?
ADifferent scenarios, different replacements: media options became attributes of
<video>/<audio> (autoplay, controls); Flash itself was replaced by HTML5 standards; iframe parameters moved to URL query strings or postMessage.QShould legacy param tags be cleaned up?
AYes — the
<object> Flash scenes they serve cannot run in modern browsers, making the whole block dead code. When migrating, check whether the Flash asset has an HTML5 replacement, then delete the object+param block together.🏷️ Related Tags
💡 Related Cases
More case studies coming soon — check back later.