# A “charset” attribute on a “meta” element found after the first 1024 bytes.
> Canonical HTML version: https://rocketvalidator.com/html-validation/a-charset-attribute-on-a-meta-element-found-after-the-first-1024-bytes
> Attribution: Rocket Validator (https://rocketvalidator.com)
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
A character encoding declaration tells the browser how to interpret the raw bytes of your document into readable characters. For HTML documents, the standard way to declare this is with ``. The HTML specification requires that this element be **serialized completely within the first 1024 bytes** of the document. This means that everything from the start of the file—including the doctype, the `` tag, the `` tag, and the `` element itself—must fit within that 1024-byte window.
If the `` element appears after the first 1024 bytes, the browser must use other heuristics or fallback encodings to guess how to decode the document. This can cause several problems:
- **Garbled or broken text**: Characters outside the ASCII range (such as accented letters, CJK characters, or emoji) may render incorrectly.
- **Security vulnerabilities**: Certain encoding-sniffing behaviors have historically been exploited for cross-site scripting (XSS) attacks, which is one reason the spec enforces this strict limit.
- **Inconsistent rendering**: Different browsers may fall back to different default encodings, meaning your page could look different depending on the user's browser or system locale.
This issue typically occurs when a large number of `` tags, inline `
My Page
Hello world
```
### ✅ Correct: `` as the first element in ``
Move the charset declaration to the very first position inside ``:
```html
My Page
Hello world
```
### ✅ Minimal correct example
For simpler documents, the pattern is straightforward—just keep `` first:
```html
My Page
Hello world
```
As a general rule of thumb, always make `` the very first thing after the opening `` tag. This guarantees it falls well within the 1024-byte limit regardless of what follows, and it ensures the browser knows the correct encoding before it encounters any other content.