The
<noframes>tag in HTML was used to provide alternative content for browsers that do not support frames.
When a webpage used the<frameset>element to divide the browser window into multiple frames, the<noframes>tag offered fallback content (like a message or simple links) for users whose browsers couldn’t display frames or had frames disabled.
Note: The<noframes>tag is deprecated in HTML5. Modern browsers support frames, and modern webpage structures use<iframe>or responsive layouts instead.
Syntax
<noframes>
Alternative content goes here...
</noframes>Attributes
| Attribute | Description |
|---|---|
| None | The <noframes> tag does not support any specific attributes. However, it may contain regular HTML elements like text, links, or images as fallback content. |
Example
<!DOCTYPE html>
<html>
<head>
<title>Example of noframes Tag</title>
</head>
<frameset cols="50%,50%">
<frame src="https://freethings.org.in">
<frame src="https://hindigems.com">
<noframes>
<body>
<p>Your browser does not support frames. Please visit
<a href="https://freethings.org.in">Frame 1</a> or
<a href="https://hindigems.com">Frame 2</a> manually.</p>
</body>
</noframes>
</frameset>
</html>Output
Browser Output
If the browser supports frames:
- Two frames will display side-by-side showing
https://freethings.org.inandhttps://hindigems.com.
If the browser does not support frames:
- The text inside
<noframes>will appear:
Your browser does not support frames. Please visit Frame 1 or Frame 2 manually.
Browser Support
 Chrome |  Firefox |  Edge |  Safari |  Opera |  IE9+ |
|---|---|---|---|---|---|
| ✅Yes | ✅Yes | ✅Yes | ✅Yes | ✅Yes | ✅Yes |
| Browser | Support | Notes |
|---|---|---|
| Chrome | ✅ Yes | Still rendered for backward compatibility |
| Edge | ✅ Yes | Supported in legacy mode |
| Firefox | ✅ Yes | Supported but deprecated |
| Safari | ✅ Yes | Supported for old content only |
| Opera | ✅ Yes | Supported but obsolete |
| Internet Explorer | ✅ Yes | Originally designed for IE4+ |
Notes
- The
<noframes>tag should always be used inside a<frameset>block. - It is mainly useful for very old browsers that do not support frames.
- Modern web design practices no longer use frames or noframes.
- If you need fallback content, consider using CSS-based layouts and
<iframe>with accessible messaging instead.
Conclusion
The <noframes> tag was introduced as a fallback mechanism for browsers that could not render frames. While it still displays content in some browsers for legacy support, it is obsolete in HTML5.
Developers should use responsive layouts, semantic HTML elements, and <iframe> for embedding content instead of relying on frames or noframes.
