<noscript>: The NOSCRIPT Element
Last updated: 2026-10-13
<noscript>The NOSCRIPT Element
Shows its content when JavaScript is disabled or unsupported, for graceful degradation.
| Category | Scripts & Embedding |
|---|---|
| Content Model | Flow content |
| Allowed Parents | Any element that accepts flow content |
| Content Tag | Yes — requires closing </noscript> tag |
| Status | Standard |
📝 Syntax
<noscript>fallback content</noscript>▶ Example
Edit the code below and see the live result in the playground:
🌐 Browser Support
| Browser |  Chrome |
 Edge |
 Firefox |
 Safari |
 Opera |
|---|---|---|---|---|---|
| <noscript> | ✓ v1 | ✓ v12 | ✓ v1 | ✓ v1 | ✓ v1 |
| Supported in all major browsers | |||||
Tip： noscript is hidden when JS works; it may contain any flow content.
❓ FAQ
QWhen does noscript content show?
AOnly when scripting is disabled or unsupported; with JS working, its content is fully ignored (no layout impact). Typical uses: a degraded hint when JS is off, analytics fallbacks, and no-JS navigation links.
QCan noscript go inside body?
AYes. In head it may only contain link/style/meta; in body it may contain any flow content. Placing it early in body (e.g. right after the opening tag) makes the notice visible to no-JS users immediately.
QDo modern sites still need noscript?
ADepends: sites with server-rendered core content hardly need more than a courtesy; heavily JS-dependent apps still benefit from a basic this site requires JavaScript notice. It costs almost nothing — keeping one is a good habit.
🏷️ Related Tags
💡 Related Cases
More case studies coming soon — check back later.
📚 Related Tutorials
