Markdown logo with text that reads, Markdown Viewers.

Markdown Viewers for the Linux Command Line

  • Adam Douglas

Though Markdown files are text based, at times it would be handy to have syntax highlighting or rendering of the document for ease of reading in the Linux terminal. Viewers usually solve this by providing a simple, light weight and fast user experience. Let’s find out what these solutions have to offer.


The software application here is not directly intended as a markdown viewer, but rather as cat clone with syntax highlighting and Git integration. However, it does work quite well. The project is primarily written in Rust and describes Bat as “A cat clone with wings”. When launching the application, you are presented with a nice clean interface, with filename at the top and a column on the left showing the line numbers, and on the right the document content. Syntax highlighting is definitely Bat’s strong suite with over 166 supported language as of this post. On top of that when viewing files there are indicators shown beside the line numbers which lines have been altered according to the git index. Another nice feature of this viewer is the fact that it can be told to show non-printable characters, which is always handy when trying to locate that problem character. The pager used is less by default, but can be changed to the desired command. One last feature that I have to say can be nice to use, is the ability to view multiple files at once. Each file is shown in the viewer one after another. I would suggest looking at the command line help, as there is quite a lot that can be done.

Screenshot of the Bat rendering a Markdown document within the Kitty terminal.


The command line Markdown browser as it is described achieves a polished look and feel utilizing the Textual Python framework within a text user interface (TUI) that allows for ease of navigation with the use of a keyboard or mouse. The interface supports both a light and dark mode theme. Markdown documents can be opened directly from the command line, through its own local file browser or by using the address bar. While viewing Markdown documents one can easily scroll with the mouse or use the keyboard to page up and down. It is nice to see that links are clickable, though I could not figure how to navigate the document itself to open a link using the keyboard. Additional features include a document table of contents shown within the navigation bar under “Contents” along with a local file browser, bookmarks, and history. From what I’ve tested Markdown rendering seems to handle basic syntax along with some extended syntax, such as headings, bold, italic, blockquote, ordered lists, unordered lists, code with syntax highlighting, horizontal rule, links, tables, task list and more. The application configuration settings, bookmarks and history are all stored in JSON (JavaScript Object Notation) format in their applicable location. On Linux the configuration is stored within the user’s home directory at “~/.config/textualize/frogmouth/” and the bookmarks along with history is stored at “~/.local/share/textualize/frogmouth/”. With the use of Python this makes the application quite portable for support of running on Linux, macOS, and Windows operating systems.

Screenshot of the Frogmouth rendering a Markdown document within the Kitty terminal.

  • Project: GitHub
  • License: MIT
  • Tested version: 0.5.0


This colorful Go language based viewer is definitely the one with the most pizzazz as the project describes it. It works directly from the command line, but also provides a text user interface (TUI) with optional mouse support. To use TUI-mode simply run the command without providing a filename and once loaded all the markdown files are shown in a list for ease of browsing. The app can be configured to set styles (dark, light, auto), show local files only (TUI-mode only), mouse support (TUI-mode only), pager, word-wrap width. An added feature called stash provides the ability to store markdown files into your own private encrypted collection. To top this all off the viewer also is able to edit local files and copy file contents.

Screenshot of the Glow rendering a Markdown document within the Kitty terminal.

  • Project: GitHub
  • License: MIT
  • Tested version: 1.5.1


A Rust based browserless markdown viewer powered by the GPU (graphics processing unit) that doesn’t require the use of Electron or Chrome. This slim viewer handles basic HTML rendering with the power of detecting live file modifications along with optional mouse support and clickable links. A handy feature to use alongside your favorite text editor. Presently Inlyne supports tables, sizable images, code blocks, lists, check/task lists, links, hidden details, alignment of text/image, quote blocks, and text styles (bold, italics, underline, small). If you want something fast with basic support this viewer maybe for you.

Screenshot of the Inlyne rendering a Markdown document within the Kitty terminal.

  • Project: GitHub
  • Licnese: MIT
  • Tested version: 0.3.0


Command line application mdcat is refereed to as a fancy cat for Markdown and is intended to be used with Kitty or iTerm2 terminals with a good font that has italic characters. When opening a document the rendering shows the title at the top with modified front matter and then the body. Code blocks have syntax highlighting using syntect. Links within the document a rendered nicely hiding the link address and making the link clickable to view. If images are present they will be loaded inline in supported terminals only. One observation I noticed is, the viewer by default does not use a pager. The pager though can be enabled with the parameter -p.

Screenshot of the mdcat rendering a Markdown document within the Kitty terminal.

Closing Thoughts

There were a few areas that I was disappointed in, mdcat doesn’t support rendering tables, not all viewers have the ability to search within a document, Frogmouth opens up the last viewed document and Frogmouth doesn’t allow for disabling the history feature. Overall I feel each viewer has its strong points and anyone of them could easily do the job. It really comes down to an individual of what is preferred, and how it can all work together in one’s workflow.

This is post 61 of 100, and is round 2 of the 100 Days To Offload challenge.

    • change topic
    • change 100DaysToOffload message
    • add viewer inlyne
    • add new glow features
    • change bat version
    • change mdcat version
    • add viewer frogmouth
    • add software license
    • change glow version
    • change last paragraph