The <ins> & <del> elements
The <ins> and <del> tags record edits to a document. <del> marks text that has been removed, shown with a line through it, and <ins> marks text that has been added, shown underlined. Their datetime attribute records when the change happened and cite can link to an explanation.
Last updated: October 3, 2026
Quick facts
| Category | Phrasing content (and flow content when they wrap blocks) |
| Content model | Transparent — whatever their parent allows, so they can wrap inline text or whole blocks |
| Tag omission | Neither the start nor the end tag can be omitted |
| Permitted parents | Any element that accepts phrasing content |
| DOM interface | HTMLModElement (both) |
Syntax
Live example
Edit the code below and watch the preview update instantly.
Attributes
| Attribute | Description |
|---|---|
| cite | A URL to a page explaining the change, such as a changelog. Not displayed |
| datetime | When the change was made, e.g. 2026-10-03 or 2026-10-03T14:30 |
Common examples
A corrected article
Show what changed and when, with the datetime attribute.
A to-do list
Crossed-off items can be marked as removed from the list.
Linking to the reason for a change
The cite attribute can point to a page explaining the change.
Accessible change markers
CSS can add hidden words so screen reader users also know what was removed and added.
<del> vs CSS line-through
<del> means “this was removed from the document”. CSS text-decoration: line-through only draws a line through text without any meaning, which is fine for a visual effect such as a completed checklist item in an app.
If the strike-through records an actual edit — a correction, a changed date, updated terms — use <del>, ideally with <ins> for the new text. If it’s only styling, use CSS.
| <del> | line-through | |
|---|---|---|
| Meaning | Removed content | None |
| Change date | datetime attribute | No |
| Best for | Corrections, edit history | Visual effects |
Common mistakes to avoid
- Using del for an old price. A price that is no longer accurate (but wasn’t an edit) is better as <s>.
- Keeping every change forever. Long trails of deleted text make pages hard to read; summarise old changes in a changelog.
- Assuming screen readers announce them. Most don’t by default, so explain important changes in words.
- Writing dates in the wrong format.
datetimeneeds ISO format, such as2026-10-01.
Accessibility & SEO tips
- Visible corrections on articles build trust with readers and show that your content is maintained.
- Update the page’s “last updated” date when you make real changes, so search engines and readers know the content is current.
- Underlined
<ins>text can look like a link; consider a different style such as a light green background. - Keep corrections short and clear — strike out only the wrong part, so readers can see exactly what changed.
Browser support
Supported in every browser, including Chrome, Edge, Firefox, Safari and their mobile versions — it has been part of HTML since the very first versions.