Markdown Checklist Generator
Runs 100% in your browserBuild GitHub-compatible Markdown checklists visually — add tasks, indent subtasks, group under headings, import plain text or existing GFM, mark progress, preview, and download .md or .html. Free, 100% browser-local, no upload.
Start from plain tasks or an existing GFM checklist
Checked markers, headings, bullet styles, and two-space nesting are detected locally. Plain lines become unchecked tasks.
Edit, check, reorder, and nest tasks
Add a task or load the sample to begin.
Use ? ? to outdent/indent (up to 3 levels), ? ? to reorder, — to delete. Ctrl+Enter copies the Markdown output.
Copy-ready GFM task list
Rendered task list
Your checklist preview appears here.
Progress and diagnostics
Recent checklists — click to restore
No history yet — generated checklists appear here.
- [ ] and - [x] task-list syntax. GitHub, GitLab, Jira, Notion, and other Markdown renderers each apply their own rules — rendering, nesting depth, and interactive checkbox behavior can differ across platforms. Always preview in the destination before publishing.
Frequently asked questions
A Markdown Checklist Generator turns ordinary task lines or plain text into GitHub Flavored Markdown task-list syntax. It produces unchecked `- [ ]` items and completed `- [x]` items that can be pasted directly into GitHub README files, issues, pull requests, changelogs, project plans, wikis, Notion pages, and any Markdown-compatible document — without hand-formatting a single marker.
Open the generator, click "+ Task" to add rows or paste existing tasks into the Import area, edit each task text and mark completed items with the checkbox, indent subtasks using the → button, group sections with headings, and click "Copy Markdown" or "↓ .md" when the checklist is ready. The Load sample button shows a complete example with headings, nested subtasks, and checked items.
The GitHub Flavored Markdown syntax for an unchecked task is a list marker, a space, an opening bracket, a space, a closing bracket, and the task text: `- [ ] Task name`. The generator writes this structure automatically for every unchecked row. Asterisk (*) or plus (+) can also be used as the list marker instead of a hyphen.
A completed GFM task uses a lowercase x between the brackets: `- [x] Completed task`. The generator marks rows as complete when you tick the checkbox on a task row. Lowercase x is used because it is the most widely accepted form across GitHub, GitLab, Jira, and other GFM-compatible renderers.
Yes. Paste existing GFM lines such as `- [ ] Plan release`, `- [x] Review tests`, or nested items with two-space indentation into the Import area and click "Import checklist". Checked states, heading markers, bullet types (-, *, +), and two-space nesting are detected automatically. The imported rows load into the visual editor ready for editing.
Yes. Paste one task description per line without any checkbox markers. The generator converts each non-empty line into an unchecked task. Empty lines are ignored, headings starting with # markers are preserved as section headings, and ordinary bullet lines (- item, * item) are converted to unchecked tasks with their nesting preserved.
Use the → button on any task row to indent it one level, up to a maximum of three levels. The generator serializes each indent level as two spaces, which is the standard representation for nested GFM task lists. Use the ← button to reduce nesting. The indent level badge (L1, L2, L3) shows the current nesting depth so you can see it at a glance.
Yes. Click "+ Heading" to add a section heading row and choose H2, H3, or H4. Heading rows are emitted as standard Markdown headings (## Section, ### Sub-section) and separate task groups. Common uses include grouping a checklist into Setup, Build, Test, and Deploy phases, or Plan, In Progress, and Done sections in a release checklist.
Yes. Each row has ↑ (move up), ↓ (move down), and × (delete) controls. Reordering updates the generated Markdown output in real time. "Clear checked" removes all completed task rows while keeping headings and open tasks intact — useful for preparing a clean next-run checklist. "Clear all" resets the entire editor.
When "Include progress comment" is enabled, the generator adds an HTML comment at the top of the output: `<!-- Progress: 2/5 complete -->`. This comment is invisible when the Markdown is rendered but readable in the raw source, making it useful for tracking checklist status in version-controlled files without affecting the rendered appearance.
Build your checklist in the editor, copy the generated Markdown, and paste it directly into a GitHub README.md file. GitHub renders `- [ ]` as interactive checkboxes in issues and pull requests, but in README files the checkboxes appear as read-only rendered elements. For an interactive list with clickable checkboxes in a repository, paste the output into an issue body or pull request description.
`- [ ]` creates an unchecked (open) task. `- [x]` creates a checked (completed) task. The space inside the brackets is required for the unchecked form — `- []` without the space is not valid GFM task-list syntax and will not render as a checkbox. The generator always writes the correct form based on the checkbox state of each row.
The generated syntax is standard GFM-style Markdown, but each platform applies its own rendering rules. GitLab renders `- [ ]` and `- [x]` as interactive checkboxes in issues and merge requests. Jira Markdown editor and Notion both support task-list syntax but may differ in nesting depth, interaction behavior, or heading support. Always preview the output in the target platform before publishing.
Yes. Choose hyphen (-), asterisk (*), or plus (+) from the Bullet dropdown. Hyphens are the most common choice for GitHub checklists, but if your surrounding document uses asterisks or plus signs for regular lists, switching the marker keeps the style consistent. All three forms produce valid GFM task-list syntax.
Yes. The "↓ .html" button downloads a complete, styled standalone HTML file containing the rendered checklist with disabled checkboxes. The file includes a clean stylesheet and is suitable for sharing, archiving, or embedding. The "↓ .md" button saves the raw Markdown source. Both export formats are generated entirely in your browser without any server request.
The session history panel records up to 8 recent checklist states generated during the current session. Each entry shows the first task label and a task count. Clicking an entry restores the checklist editor and output to that state. History is stored in browser memory only and is cleared when you close or refresh the tab — it is never written to localStorage or sent to any server.
The Checklist Review panel shows: total tasks, completed tasks, remaining tasks, completion percentage, heading count, nested task count, output byte size, and warning count. Warnings are shown for empty task rows, orphaned nested tasks (nested tasks without a preceding top-level task), very large checklists (50+ tasks), and heading-only states with no tasks. These help you review the structure before copying.
No. All task building, import parsing, preview rendering, and export happens in browser memory on your device. The generator uses no fetch, XMLHttpRequest, sendBeacon, localStorage, sessionStorage, or IndexedDB at any point. Closing the tab clears the working state entirely. You can confirm this in DevTools → Network — zero outbound requests are made during any checklist operation.
No. It generates Markdown source text and a local rendered preview. It does not provide reminders, due-date tracking, calendar integration, collaboration, real-time sync, issue synchronization, or a replacement for a project-management application. If you need task management with reminders and collaboration, use a dedicated product. This tool focuses on generating correct, portable GFM syntax quickly and privately.
MarkdownTools offers a simple add/check/copy workflow for flat lists with no import, nesting, or download. Dillinger is a full Markdown editor with import and nested-list support but no checklist-specific controls, progress summary, or history. ToolsSonic combines a visual row editor, import parser (plain text + GFM round-trip), 3-level nesting, heading groups, progress tracking, 8-stat panel, session history with restore, .md + .html export, full dark mode, and a completely browser-local architecture with no cloud sync or account.
The editor has no hard limit on the number of rows. A warning is shown when a checklist reaches 50 tasks, because very large flat checklists become difficult to review and edit. For long workflows, split tasks into headed sections (H2/H3 groups) so each section remains scannable. The generator serializes all rows within the editor regardless of count.
Yes. ToolsSonic's Markdown Checklist Generator is completely free with no account, no rate limit, no watermark, no file size limit, and no upload. The visual editor, import, nesting, headings, progress tracking, session history, and both download formats (.md and .html) are available at no cost, with no ads or paywalls.
What is Markdown Checklist Generator?
What is a Markdown Checklist Generator?
A Markdown Checklist Generator is a browser tool that converts task lines and plain text into GitHub Flavored Markdown task-list syntax — the - [ ] and - [x] format used in README files, GitHub issues, pull requests, project changelogs, wikis, Notion pages, and any Markdown-capable platform.
Writing GFM task lists by hand is tedious and error-prone. You have to remember the exact format (- [ ] Task with a space inside the brackets), keep nesting consistent with two-space indentation, match heading levels, and remember to escape any special characters. A dedicated generator handles every formatting detail automatically: you build the list visually, mark completed items, set nesting depth, add section headings, and get a valid, copy-ready Markdown checklist instantly.
ToolsSonic's Markdown Checklist Generator runs 100% in your browser. There is no account, no file upload, no cloud sync, and no network request of any kind during checklist generation. You can confirm this by opening DevTools → Network while building a checklist — zero bytes leave your device.
Build Checklists Visually — Features and Workflow
Most tools in this category provide a plain textarea where you type - [ ] manually, or a single "add item" button with no import or export. ToolsSonic's generator goes further on every feature that matters for developers, writers, and project teams:
Visual task row editor — Each row is an editable input with a real checkbox. Checking the box immediately updates the Markdown output from - [ ] to - [x]. You see the checklist as a structured list, not a wall of raw text. New task rows can be added with a single click, and the first task field focuses automatically so you can type immediately.
Three-level nesting — Use the → button to indent any task row up to three levels deep. The generator serializes each indent level as two spaces: - [ ] Subtask, - [ ] Sub-subtask. An indent level badge (L1, L2, L3) on each row shows the current nesting depth at a glance. Use ← to reduce nesting. A warning is shown if nested tasks appear without a preceding top-level task, which can cause unpredictable rendering on some platforms.
Section headings — Click "+ Heading" to add H2, H3, or H4 heading rows. Heading rows are emitted as standard Markdown headings (## Deploy, ### Smoke tests) and group tasks into named phases. Common patterns: Setup / Build / Test / Deploy; Plan / In Progress / Done; Frontend / Backend / Infrastructure.
Plain-text and GFM round-trip import — The import parser accepts plain lines (one task per line, no markers), existing GFM checklists (- [ ] Task, - [x] Done), ordinary bullet lists (- Item), and Markdown headings (## Section). Checked states, heading levels, bullet marker types, and two-space nesting depth are all detected and preserved. This makes it easy to round-trip an existing checklist from a README or issue, edit it, and paste it back.
Progress comment — When "Include progress comment" is enabled, the generator prepends <!-- Progress: 2/5 complete --> to the output. This HTML comment is invisible in rendered Markdown but readable in the raw source — useful for tracking checklist status in version-controlled files or commit messages.
8-stat review panel — The Checklist Review panel reports total tasks, completed tasks, remaining tasks, completion percentage, heading count, nested task count, output byte size, and warning count. Warnings flag empty task rows, orphaned nested tasks, very large checklists, and headings-only states.
Session history with restore — Up to 8 recent checklist states are saved in browser memory during the session. Each history entry shows the first task name and a task count. Clicking an entry restores the full checklist state to the editor and output. History is cleared when the tab closes.
Two export formats — "↓ .md" downloads the raw Markdown source as a .md file. "↓ .html" downloads a complete styled standalone HTML document with the rendered checklist and disabled checkboxes — suitable for sharing, archiving, or embedding. "Copy Markdown" places the output on the clipboard. Ctrl+Enter triggers the copy shortcut.
Bullet marker selection — Choose hyphen (-), asterisk (*), or plus (+) as the list marker. All three produce valid GFM task-list syntax. Switching the marker instantly regenerates the entire output so you can match the surrounding document style.
GFM Task Lists Across Platforms
GitHub Flavored Markdown task lists use a specific syntax defined in the GFM specification: a list item marker, a space, an opening bracket, either a space (unchecked) or a lowercase x (checked), a closing bracket, and the task text. The space inside the brackets is required — - [] without the space is not valid and will not render as a checkbox on any platform.
Rendering and interaction vary significantly across destinations:
GitHub — In issues, pull requests, and discussions, GitHub renders task lists as interactive checkboxes that can be checked and unchecked directly in the UI without editing the Markdown source. Progress counts appear in the issue sidebar. In README.md files, checkboxes are rendered but not interactive (read-only). The generated output is fully compatible with both contexts.
GitLab — Renders - [ ] and - [x] as interactive checkboxes in issues and merge requests. Nested task behavior follows ordinary Markdown list indentation. The ToolsSonic output is fully compatible.
Jira — Jira's built-in Markdown editor supports task lists in some project types and boards. Rendering and nesting support can depend on the Jira version and the specific field type. Test the output in your target Jira project before relying on it for nested subtasks.
Notion — Notion supports - [ ] syntax in its Markdown import flow. Checkboxes become interactive Notion to-do blocks. Nesting may be flattened depending on the import depth and the Notion block type. Preview the import result before sharing.
Obsidian — Obsidian renders GFM task lists in Reading and Live Preview modes and supports plugins for task management. The output from ToolsSonic is compatible with Obsidian's native task-list rendering.
Static site generators (Hugo, Jekyll, MkDocs, Docusaurus) — Most modern static site generators support GFM task lists. Rendering depends on the Markdown processor and theme. Hugo and Jekyll with the GoldMark or kramdown processors render task lists correctly. Check your specific generator's documentation for nesting support.
The ToolsSonic generator gives you portable GFM syntax with clear platform notes so you understand exactly what to expect before pasting the output.
Common use cases
- Creating GitHub README release checklists with headings, tasks, and nested verification steps
- Building issue and pull-request task lists with checked and unchecked states
- Converting a plain-text task list from a meeting or note into a GFM checklist
- Grouping project work under section headings such as Plan, Build, Test, and Deploy
- Importing an existing GFM checklist, clearing completed items, and downloading a fresh copy
- Tracking completion percentage before pasting a checklist into a pull request
- Creating onboarding checklists for README files with nested setup and configuration steps
- Generating private offline Markdown checklists without uploading to a cloud service
Why use ToolsSonic's Markdown Checklist Generator?
ToolsSonic's Markdown Checklist Generator is the only free browser tool that combines a visual row editor, three-level nesting with depth badges, GFM round-trip import, section headings, a progress comment, an 8-stat review panel, session history with restore, .md and .html export, full dark mode, and a completely browser-local architecture. MarkdownTools offers a flat-list generator without import, nesting, or download. Dillinger is a full Markdown editor without checklist-specific controls. Code Beautify processes Markdown but has no dedicated task-row editor. ToolsSonic delivers the focused workflow for GFM checklists without becoming a project-management product.
GFM Task List Syntax Reference
| Syntax | Renders as | Notes |
|---|---|---|
- [ ] Task name | Unchecked checkbox | Space inside brackets required |
- [x] Task name | Checked checkbox | Lowercase x; uppercase X also accepted by most renderers |
* [ ] Task name | Unchecked (asterisk) | All three list markers (-, *, +) are valid |
- [ ] Subtask | Nested (one level) | Two spaces per indent level |
- [ ] Sub-subtask | Nested (two levels) | Four spaces = level 2 |
## Section heading | H2 group heading | H2, H3, H4 all valid for grouping |
<!-- Progress: 2/5 complete --> | Invisible comment | Readable in raw source, invisible in render |
- [] Task | Not a checkbox | Missing space — renders as plain list item |
ToolsSonic vs Competitors — Markdown Checklist Tools
| Feature | ToolsSonic | MarkdownTools | Dillinger | Code Beautify | Checklist.com |
|---|---|---|---|---|---|
| Visual row editor | ✅ | ✅ | ❌ | ❌ | ✅ |
| Import plain text + GFM | ✅ | ❌ | ✅ | ❌ | ❌ |
| Nested subtasks (3 levels) | ✅ | ❌ | ✅ | ❌ | ❌ |
| Section headings (H2–H4) | ✅ | ❌ | ✅ | ❌ | ❌ |
| Progress comment in output | ✅ | ❌ | ❌ | ❌ | ✅ |
| 8-stat review panel | ✅ | ❌ | ❌ | ❌ | partial |
| Session history + restore | ✅ | ❌ | partial | ❌ | ❌ |
| Download .md + .html | ✅ | ❌ | ✅ | ✅ | ❌ |
| Ctrl+Enter shortcut | ✅ | ❌ | ❌ | ❌ | ❌ |
| Full dark mode | ✅ | ❌ | ✅ | ❌ | ❌ |
| 100% browser-local | ✅ | ✅ | partial | partial | ❌ |
| No account required | ✅ | ✅ | ✅ | ✅ | paid |
Related tools
Markdown Formatter
Editor's choiceFormat Markdown locally with consistent headings, lists, blank lines, blockquotes, tables, code fences, GFM task lists, strikethrough, diagnostics, history, preview, copy, and download.
Markdown Preview
Editor's choiceRender Markdown as HTML and preview it live — sanitized, script-free, with a clear source/preview split.
Markdown Table Generator
Editor's choiceCreate aligned GitHub Flavored Markdown pipe-table syntax visually — edit rows and columns, paste from Excel, Google Sheets, CSV, or an existing Markdown table, set per-column alignment, escape pipes, preview the rendered result, and download .md, .html, or .csv. Free, no upload.
Markdown to HTML
Editor's choiceConvert Markdown to clean, structured HTML locally — headings, paragraphs, links, images, lists, tables with column alignment, nested lists, task lists, blockquotes, setext headings, and fenced code with a sanitized preview.
HTML to Markdown
Editor's choiceConvert clean HTML back to Markdown — headings, bold, italic, code, tables, lists, links, images, and blockquotes with full GFM support.
CSV to Markdown Table
Editor's choiceConvert CSV and TSV into aligned GitHub Flavored Markdown tables locally with quote-aware parsing, delimiter detection, safe pipe escaping, per-column alignment, preview, diagnostics, copy, and download.