{"slug": "glow", "name": "glow", "category": "terminal", "category_name": "Terminal and shell", "description": "", "recommenders": 4, "commenters": 6, "warners": 0, "score": 4.034, "rising": 1.35, "first": "2026-02-10", "latest": "2026-09-11", "why": "I mostly use TUI markdown viewers that render the document via ANSI escape codes beautifully. Check out glow project.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 0, "compare": 2, "warn": 0}, "spark": [0, 0, 0, 1, 0, 1, 0, 0, 0, 1, 1, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "I mostly use TUI markdown viewers that render the document via ANSI escape codes beautifully. Check out glow project.", "icon": true, "domain": null, "github_repo": "github.com/charmbracelet/glow", "official_url": "https://github.com/charmbracelet/glow", "pricing": "", "aliases": ["glow", "Glow"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 794521184, "item_id": 49657574, "url": "https://news.ycombinator.com/item?id=49657574", "by": "snehesht", "date": "2026-09-11", "stance": "recommend", "quote": "For anyone looking for a more general renderer, https://github.com/charmbracelet/glow.", "excerpt": "This looks neat, congrats. For anyone looking for a more general renderer, https://github.com/charmbracelet/glow.", "context": "", "use_case": "rendering Markdown in terminal", "switched_from": "", "story": "Show HN: Beautiful Markdown rendering in your terminal"}, {"id": 790415974, "item_id": 49400998, "url": "https://news.ycombinator.com/item?id=49400998", "by": "folkrav", "date": "2026-08-22", "stance": "recommend", "quote": "glow for markdown reading", "excerpt": "Not OP but, I regularly use : - yazi as a file explorer - lazygit for git - tmux/zellij as multiplexers - fzf left and right for a bunch of utils (terminal history, switching between projects in zellij/tmux when working in multi-project workspaces, etc) - neovim as a text editor - glow for markdown reading - currently on pi for my home harness, CC at work I'm probably missing a few but those are the ones I use more o", "context": "", "use_case": "reading markdown", "switched_from": "", "story": "Stop Making TUIs"}, {"id": 762151888, "item_id": 47634493, "url": "https://news.ycombinator.com/item?id=47634493", "by": "jdefr89", "date": "2026-04-03", "stance": "recommend", "quote": "I mostly use TUI markdown viewers that render the document via ANSI escape codes beautifully. Check out glow project.", "excerpt": "A few things here. 1. Use a proper Markdown parser. The grammar is easy to define EBNF style most implementations I see now days use some recursive descent parser, etc\u2026 Regex implementation was used in original authors parser when it became popular. 2. You can resolve ambiguities and define more consistent symbols that make sense. Most markdown implementations are decent and follow common sense best practice syntax. ", "context": "", "use_case": "terminal markdown viewing", "switched_from": "", "story": "Why the heck are we still using Markdown?"}, {"id": 751517600, "item_id": 46969850, "url": "https://news.ycombinator.com/item?id=46969850", "by": "smoyer", "date": "2026-02-10", "stance": "recommend", "quote": "Here's the one I use a lot", "excerpt": "Here's the one I use a lot ... And the underlying `glamour` library is great for programmatic markdown display: https://github.com/charmbracelet/glow.", "context": "", "use_case": "markdown CLI viewer", "switched_from": "", "story": "Markdown CLI viewer with VI keybindings"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["rendering markdown in terminal", "terminal markdown previewing", "markdown rendering", "reading markdown", "terminal markdown viewing", "markdown cli viewer"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49655403", "title": "Show HN: Beautiful Markdown rendering in your terminal", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49649351", "title": "Show HN: Shine \u2013 a terminal Markdown previewer and docs linter", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49546657", "title": "Show HN: Tiny Markdown CLI renderer \u2013 Streaming, 10x faster, 2MB flat RAM", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49384210", "title": "Stop Making TUIs", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47629903", "title": "Why the heck are we still using Markdown?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46963865", "title": "Markdown CLI viewer with VI keybindings", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {"recommend": 1}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {"compare": 2, "recommend": 1}, "2026-10": {}}, "quotes": [{"id": 794521184, "item_id": 49657574, "url": "https://news.ycombinator.com/item?id=49657574", "by": "snehesht", "date": "2026-09-11", "stance": "recommend", "quote": "For anyone looking for a more general renderer, https://github.com/charmbracelet/glow.", "excerpt": "This looks neat, congrats. For anyone looking for a more general renderer, https://github.com/charmbracelet/glow.", "context": "", "use_case": "rendering Markdown in terminal", "switched_from": "", "story": "Show HN: Beautiful Markdown rendering in your terminal"}, {"id": 794407760, "item_id": 49650485, "url": "https://news.ycombinator.com/item?id=49650485", "by": "camelfarmer", "date": "2026-09-10", "stance": "compare", "quote": "I assume from the name that Shine is inspired by [Glow](https://github.com/charmbracelet/glow), how is this different?", "excerpt": "I assume from the name that Shine is inspired by [Glow](https://github.com/charmbracelet/glow), how is this different?", "context": "", "use_case": "terminal Markdown previewing", "switched_from": "", "story": "Show HN: Shine \u2013 a terminal Markdown previewer and docs linter"}, {"id": 792746769, "item_id": 49546673, "url": "https://news.ycombinator.com/item?id=49546673", "by": "cjcj", "date": "2026-09-03", "stance": "compare", "quote": "glow - the most popular cli renderer, was about 100x slower and used about 100x more RAM", "excerpt": "Hi HN, Most terminal Markdown renderers, such as glow and mdcat, buffer the entire document before rendering. This makes them poorly suited to live LLM output and can result in unnecessary CPU and memory usage. I built mdflow, a true real-time streaming Markdown cli renderer that is super fast and lightweight. I started with MD4C, written in C, like others it also buffers the whole document, but its flat-buffer desig", "context": "", "use_case": "Markdown rendering", "switched_from": "", "story": "Show HN: Tiny Markdown CLI renderer \u2013 Streaming, 10x faster, 2MB flat RAM"}, {"id": 790415974, "item_id": 49400998, "url": "https://news.ycombinator.com/item?id=49400998", "by": "folkrav", "date": "2026-08-22", "stance": "recommend", "quote": "glow for markdown reading", "excerpt": "Not OP but, I regularly use : - yazi as a file explorer - lazygit for git - tmux/zellij as multiplexers - fzf left and right for a bunch of utils (terminal history, switching between projects in zellij/tmux when working in multi-project workspaces, etc) - neovim as a text editor - glow for markdown reading - currently on pi for my home harness, CC at work I'm probably missing a few but those are the ones I use more o", "context": "", "use_case": "reading markdown", "switched_from": "", "story": "Stop Making TUIs"}, {"id": 762151888, "item_id": 47634493, "url": "https://news.ycombinator.com/item?id=47634493", "by": "jdefr89", "date": "2026-04-03", "stance": "recommend", "quote": "I mostly use TUI markdown viewers that render the document via ANSI escape codes beautifully. Check out glow project.", "excerpt": "A few things here. 1. Use a proper Markdown parser. The grammar is easy to define EBNF style most implementations I see now days use some recursive descent parser, etc\u2026 Regex implementation was used in original authors parser when it became popular. 2. You can resolve ambiguities and define more consistent symbols that make sense. Most markdown implementations are decent and follow common sense best practice syntax. ", "context": "", "use_case": "terminal markdown viewing", "switched_from": "", "story": "Why the heck are we still using Markdown?"}, {"id": 751517600, "item_id": 46969850, "url": "https://news.ycombinator.com/item?id=46969850", "by": "smoyer", "date": "2026-02-10", "stance": "recommend", "quote": "Here's the one I use a lot", "excerpt": "Here's the one I use a lot ... And the underlying `glamour` library is great for programmatic markdown display: https://github.com/charmbracelet/glow.", "context": "", "use_case": "markdown CLI viewer", "switched_from": "", "story": "Markdown CLI viewer with VI keybindings"}]}