HTML Entity Renderer

approvedunreviewed

by Reggie Fluker

Renders HTML character entities such as `©` and `©` as characters in Live Preview while preserving the Markdown source.

Updated todayMIT

Install in Obsidian View on GitHub

HTML Entity Renderer for Obsidian

Renders HTML character entities in Live Preview without changing the Markdown source.

Examples:

© displays as ©
& displays as &
— displays as —
© displays as ©
© displays as ©

When the cursor enters an entity, the original source is revealed so it can be edited.

Entities are only rendered in Live Preview. Source mode, inline code, code blocks, and backslash-escaped entities (\©) are left as written, matching Reading view.

Entities that would display as nothing or as a line break (&NewLine;, &Tab;, , &zwj;, ) and invalid numeric references (, &#xD800;) are also left as source, so they stay visible and editable.

Screenshots

A note with HTML entities, shown before and after the plugin

Mobile

Before and after	Real note

Install

From Community plugins

In Obsidian, open Settings → Community plugins.
Turn off Restricted mode.
Click Browse, search for HTML Entity Renderer, then select Install and Enable.

Manually

Close Obsidian, or leave it open and reload after installation.
Open your vault folder.
Open .obsidian/plugins/.
Create a folder named html-entity-renderer.
Put main.js, manifest.json, and styles.css in that folder.
In Obsidian, go to Settings → Community plugins.
If prompted, turn off Restricted mode.
Click the refresh/reload button if the plugin is not listed, or restart Obsidian.
Enable HTML Entity Renderer.

Try it

Test with:

Copyright &copy; 2026
Fish &amp; Chips
A&nbsp;B
&#169; and &#xA9;

The file itself remains unchanged; only the Live Preview display is decorated.

Development

package.json and tests/ are only needed for development; don't copy them into the vault. To run the unit tests (Node.js 18 or later):

npm install
npm test

Similar Plugins

HTML Live Editor

approvedunreviewed58% similar

by elijahchan2019

Click to edit text in HTML blocks directly within Live Preview mode.

↓ 3052mo agoMIT

Smart Punctuation on Rendering

approvedunreviewed58% similar

by ile-24556

Renders ASCII punctuation characters in typographic forms, so you don’t have to struggle to enter desired characters in different editors anymore, for a better reading view.

↓ 2811mo agoMIT

Special Characters Panel

approvedunreviewed57% similar

by ronsayshello

A searchable, categorized panel of special characters (arrows, math, currency, bullets, dingbats, accented Latin, Greek, punctuation). Click to copy and insert.

↓ 493d agoMIT

HTML Viewer

approvedunreviewed57% similar

by jialinzhang24

Render .html files in a sandboxed view. Toggle scripts ON for games, visualizations, and interactive documents.

★ 2↓ 4,4235mo agoMIT

Borrax HTML

approvedunreviewed57% similar

by dogukansahil

View HTML files inside your vault with working links, CSS and scripts.

↓ 6963mo agoGPL-3.0

Highlight Non-ASCII

approvedunreviewed57% similar

by saltyfireball

Highlights non-ASCII characters in your notes with a red background in both Edit and Reading views.

★ 1↓ 9874mo agoMIT

HTML Direct Reader

approvedunreviewed57% similar

by conquert

Bypass cross-origin limits to render in-vault .html in Obsidian by inlining CSS/images/scripts. In-vault .html/.md link interception with back/forward, in-page search, zoom, outline, fullscreen, scroll restore. Desktop & mobile.

↓ 4831mo agoMIT

Artifacts

unlisted57% similar

by tj19961229

Render interactive HTML, CSS, and JS content directly in your notes via html-render code blocks.

★ 16mo agoMIT

HTML Table Math

approvedunreviewed57% similar

by timeofmei

Render LaTeX math inside raw HTML table cells.

↓ 1982mo agoMIT

HTML Renderer

unlisted57% similar

by Obsidian

Renders HTML code blocks (including CSS and JS) inside an isolated iframe.

2mo ago0BSD

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.