No overrides. Every markdown element falls through to its built-in renderer — clean baseline for comparison.
Svelte 5 snippets let you customize rendering directly in your template. No separate files needed for simple tweaks.
Check out the documentation for the full guide.
Tip: Snippets take precedence over component renderers. Use them for quick, one-off overrides.
Here is a feature comparison:
| Approach | Files | Reusable | Best For |
|---|---|---|---|
| Snippets | 0 | No | Quick tweaks |
| Components | 1+ | Yes | Complex logic |
// Snippet overrides are this simple:
<SvelteMarkdown source={md}>
{#snippet paragraph({ children })}
<p class="custom">{@render children?.()}</p>
{/snippet}
</SvelteMarkdown>Inline Svelte 5 snippets customize paragraphs, headings, links, blockquotes, list items, code blocks, and table cells — all in one template, no separate component files.
{#snippet paragraph}…{/snippet} overrides happen inline inside <SvelteMarkdown> — no separate component files.Svelte 5 snippets let you customize rendering directly in your template. No separate files needed for simple tweaks.
Check out the documentation for the full guide.
Here is a feature comparison:
| Approach | Files | Reusable | Best For |
|---|---|---|---|
| Snippets | 0 | No | Quick tweaks |
| Components | 1+ | Yes | Complex logic |
// Snippet overrides are this simple:
<SvelteMarkdown source={md}>
{#snippet paragraph({ children })}
<p class="custom">{@render children?.()}</p>
{/snippet}
</SvelteMarkdown>