TPToolpazar

Global Araç

Markdown Preview

Önizleme

Markdown Preview

Welcome! This is a live markdown preview. Type on the left, see the rendered result on the right.

Features

  • Headings (H1 to H4)
  • Italic, bold, and inline code
  • Links
  • Lists (ordered and unordered)
  • > Block quotes
  • Horizontal rules
  • Code blocks:
function hello() {
  return "world";
}

That's the common 80% subset of Markdown. Edit the left column to try.

Renders the common Markdown subset (headings, bold, italic, lists, links, code, blockquotes, hr) client-side. No server roundtrip. For full CommonMark / GFM features (tables, task lists, footnotes), this preview is a starting point — most popular Markdown libraries (markdown-it, marked, remark) cover those edge cases.

Type or paste Markdown into the left pane and see the rendered HTML preview on the right, updating live as you type. The renderer handles the common 80% subset: headings (# - ######), bold / italic / code, ordered and unordered lists, links, blockquotes, horizontal rules, fenced code blocks. Pure browser rendering — no server roundtrip, no upload, instant updates.

Markdown was created by John Gruber and Aaron Swartz in 2004 as a lightweight markup language designed to be readable as plain text while transforming to HTML. The original syntax (now called “Markdown.pl” flavor) covered the basics; subsequent dialects added features for specific platforms:

  • CommonMark (2014): standardized specification, removed ambiguities of original syntax. The closest thing to a Markdown standard.
  • GitHub Flavored Markdown (GFM): adds tables, task lists, fenced code blocks (now standard in CommonMark), strikethrough, autolinking, mentions (@user, #issue).
  • Markdown Extra / MultiMarkdown: adds footnotes, definition lists, table-of-contents generation.
  • Pandoc Markdown: extends GFM with academic features (citations, math via LaTeX, fenced divs).

Where Markdown is used: GitHub (READMEs, issues, PRs, comments — extensions: GFM); Notion / Obsidian / Roam (note-taking, mostly CommonMark); Substack (newsletters); Reddit (comments, varies); Slack / Discord (messages, partial subset); Static site generators (Gatsby, Next, Hugo, Jekyll). For more advanced Markdown features (tables, footnotes, math, custom directives), use a full library like markdown-it, marked, or remark.

Nasıl Kullanılır

  1. Type or paste Markdown on the left.
  2. Watch the rendered HTML preview update on the right.
  3. Use as a quick syntax check before committing your Markdown to a platform that does or doesn't render certain features.
  4. Copy your Markdown source for pasting into GitHub / Notion / Substack / wherever.
  5. If you need GFM features (tables, task lists, footnotes), the basic renderer here won't show them — paste into the actual destination to confirm.

Ne Zaman Kullanılır

  • Quick syntax check while writing Markdown for an unfamiliar destination.
  • Learning Markdown — see how syntax becomes HTML in real time.
  • Onboarding teammates to Markdown for documentation.
  • Drafting Markdown content offline before pasting into an online tool.

Ne Zaman Kullanılmaz

  • GFM-specific features (tables, task lists, footnotes) — use a fuller renderer like dillinger.io or paste into GitHub directly.
  • Real editing for complex documents — use a dedicated Markdown editor (Typora, Obsidian, iA Writer, VS Code with markdown plugins).
  • Serving Markdown to users — use a server-side library (markdown-it, marked, remark) or a static site generator.

Yaygın Kullanım Senaryoları

  • Educational use — demonstrating the underlying concept
  • Onboarding a colleague who needs the same calculation/conversion
  • Verifying a number or output before passing it on
  • Quick use during a typical workday

Sık Sorulan Sorular

Does it support tables and footnotes?

Not in this minimal renderer. For full GitHub Flavored Markdown (tables, task lists, footnotes, strikethrough, autolinking), use markdown-it (npm), marked (npm), or remark (npm). Most online Markdown editors support GFM out of the box.

What's the difference between Markdown and HTML?

Markdown is a lightweight markup language that compiles to HTML. The Markdown source is intended to be readable as plain text (so you can write notes that look fine without rendering). HTML is more verbose and explicit but can do everything Markdown can plus much more (custom attributes, JavaScript, complex layouts). Markdown is great for content; HTML for specific layouts.

Why is my Markdown rendered differently across platforms?

Because each platform implements its own dialect with its own rules. GitHub renders tables; Reddit doesn't. Notion does footnotes; Slack doesn't. Slack uses a similar-but-distinct mrkdwn (with a 'k') that doesn't recognize standard Markdown. Always test on the destination platform.

Can I include HTML in Markdown?

Yes, by spec — Markdown allows raw HTML inline. Useful for things Markdown can't do (videos, custom attributes, divs with classes). Some platforms restrict which HTML is allowed (GitHub strips <script>, <iframe>, <style>, etc. for security). Plain Markdown features are universally supported; HTML embedding is platform-specific.

What's CommonMark?

A standardized Markdown specification (2014) that resolves the ambiguities of original Markdown.pl. It's the closest thing to an official spec; most modern Markdown libraries implement CommonMark plus GFM extensions. Reference: https://spec.commonmark.org

Should I use Markdown or rich-text editor?

Markdown for: technical documentation, blog posts (especially when version-controlled), code-heavy content, anywhere you'll likely paste between platforms. Rich-text for: marketing copy, complex layouts, authors who don't know Markdown, content where formatting needs to be exact (corporate documents, presentations). Many modern tools (Notion) blur the line — they look like rich-text but support Markdown shortcuts.