Preview Markdown in Sublime Text with a parser you choose

Install the MarkdownPreview package through Package Control, open your .md file, and run Markdown Preview: Preview in Browser from the Command Palette. Choose the local Markdown parser when you want local conversion. The package also offers GitHub and GitLab API parsers, which send the source to those services. Installation, parser choices

This guide uses MarkdownPreview by facelessuser. Other Sublime packages have similar names and different controls, so check the installed package before following a command name.

Install the package and open a small file

With Package Control installed, open Tools > Command Palette, run Package Control: Install Package, and select MarkdownPreview. The package's author recommends that installation route. Package installation

Save this original practice note as arrival-note.md in a folder you control:

# Workshop arrival

Please arrive through the courtyard entrance.

## Bring with you

- Your booking reference
- A printed or downloaded agenda

The arrival code is `COURT-2`.

```text
Ask at reception if the courtyard gate is closed.
```

The note is a fictional fixture. Replace its directions before using it for a real event. Its purpose is to give the preview four things to distinguish: a title, a subheading, a list, and literal code.

Choose the preview command and parser

Clear any active text selection to preview the whole document, then run Markdown Preview: Preview in Browser. The command can convert a selection when one is active. Choose the intended parser when prompted. Package settings are under Preferences > Package Settings > MarkdownPreview. Preview commands and settings

In the rendered result, check that both list items are separate and that COURT-2 stays literal. If the rest of a document unexpectedly becomes code, return to the source and check the opening and closing fences around the first affected block.

A local conversion choice does not mean every resource in a document is local. A remote image or added stylesheet can still require a network request. Keep private notes in the tools and parsers your organization permits, and inspect linked assets separately.

Diagnose a preview that appears stale

Save the file and run the preview again first. Automatic browser refresh requires additional setup: the package documents LiveReload installation, an autoreload setting, and a reload plugin choice. A browser tab that has not refreshed is a different problem from Markdown syntax that parses incorrectly. LiveReload setup

For a simple stale-output check, change the fictional code from COURT-2 to COURT-3, save, and preview again. Confirm that the new code appears. Restore the intended value afterward. Do not rewrite the whole note to diagnose a refresh failure.

Keep local preview separate from the destination

MarkdownPreview can also export HTML into Sublime Text. Save and inspect an output file if that is your deliverable; a browser preview alone does not establish that a recipient has a durable copy. Preview and export targets

If the destination is GitHub, review the file there before publishing. Its processing and supported features can differ from your local parser; GitHub Markdown checks cover that destination. Keep the .md source and verify the actual headings, links, and code at the place readers will use them.

Keep reading