Typora Themes: Install, Customize and Write Your Own
November 11, 2026 · 11 min read
Typora Themes: Install, Choose, and Write Your Own CSS
Typora themes are plain CSS files in one folder. To add one, open Preferences, click Open Theme Folder, copy in the theme's .css file and its asset folder, restart Typora, and pick it from the Themes menu. This guide also covers safe tweaks with base.user.css, a starter theme, and export styling.
How Typora Themes Work Under the Hood
Typora draws its whole window as a web page, so a theme is just a stylesheet. Each entry in the Themes menu maps to one .css file in Typora's theme folder, and the app ships with six built-in themes, among them GitHub, Newsprint and Night. Night is the only dark one of the defaults.
That design has two consequences. First, anything CSS can do, a theme can do: fonts, colours, line length, table borders, even the sidebar. Second, the built-in files aren't yours to edit. Typora replaces them when it updates, and your changes vanish. You'll see the safe alternative in the base.user.css section below.
If what you want is a stylesheet for Markdown that's already been converted to HTML, outside Typora, that's a different job, covered in our guide to Markdown CSS themes.
How Do I Install a Typora Theme?
Most themes in the Typora theme gallery install the same way:
- Open the theme folder. On macOS, open Preferences, go to the Appearance section and click Open Theme Folder. On Windows and Linux, choose File → Preferences first, then click the same button.
- Copy the theme's
.cssfile into that folder, plus any folder of fonts or images that came with it. - Restart Typora.
- Open the Themes menu and select the new entry.
On macOS the folder usually lives at /Users/<you>/Library/Application Support/abnerworks.Typora/themes/. Clicking the button is still the quickest route, because it opens the right folder on every platform.
The asset folder matters more than people expect. Lapis, for example, ships lapis.css, lapis-dark.css and a lapis folder of fonts. Copy only the CSS and the theme still loads, but with fallback fonts, so it looks wrong. A few gallery listings also offer a one-line install script. We'd rather copy files by hand, since you see every file that lands in the folder.
Best Typora Themes by Use Case
There's no single best theme, because the right one depends on what you write and where it ends up. This table maps common needs to themes that are listed in the gallery as of November 2026.
| You mostly write | Look for | Examples in the gallery |
|---|---|---|
| Long-form prose | A serif body font and a narrow measure | LaTeX Typora V2 (light and dark, styled like a LaTeX paper) |
| At night | A dark variant, or automatic light and dark switching | Night (built in), Typora Themeable (light, dark and auto variants) |
| Documents you print | Small type and page-break rules | Print (A4) and Print Letter (US Letter), both with 9pt body text |
| Code-heavy notes | A clear monospace font and readable code colours | Lapis (JetBrains Mono, code colours inspired by a VS Code theme), Dracula |
Before you commit to any Typora theme, check three things on its gallery page or repository:
- Last update. The gallery shows a date on every listing. A theme untouched for years may not match the variables newer Typora versions use.
- Platforms tested. Dracula's author designed and tested it on macOS and says Windows and Linux aren't fully tested, while Nord lists Windows 10 and macOS Big Sur. If you're on Linux, look for a theme that says it supports all platforms, as Typora Themeable does.
- License. Read it in the repository before you fork or redistribute a theme, because terms vary between authors. Lapis, for one, uses the MIT License, and our MIT License guide explains what that permits.
If you're still choosing the editor itself, our roundups of Markdown editors for Mac and the best Markdown editors compare Typora with the alternatives.
Setting Separate Light and Dark Typora Themes
On macOS and Windows, Typora lets you set one theme for light mode and another for dark mode. When your system switches colour scheme, Typora swaps to the matching theme on its own. That's the easiest way to pair, say, Lapis with Lapis Dark.
The other route is a single file that handles both modes with the prefers-color-scheme media query. Typora's docs list it as a supported way to write a responsive theme. You'll see it in the starter theme further down. One file is easier to maintain, while two files let you mix themes from different authors.
Tweaking a Typora Theme With base.user.css
You rarely need a whole new theme. To change a font or widen the writing area, add a small override file to the theme folder instead. Typora loads CSS in this order:
- Typora's basic styles
- The CSS of the current theme
base.user.cssin the theme folder{current-theme}.user.cssin the theme folder
Later files win, so your rules sit on top of whatever theme is active. Create the files yourself if they don't exist. Here's a base.user.css that applies to every theme:
/* base.user.css: loads after any theme */
:root {
--monospace: "JetBrains Mono", Menlo, Consolas, monospace;
}
#write {
max-width: 820px;
font-family: Charter, Georgia, serif;
}
This sets the code font for every theme through Typora's --monospace variable, widens the writing column to 820 pixels, and switches body text to a serif font.
To target one theme only, name the file after that theme's CSS file. The name is case-sensitive: the GitHub theme's file is github.css, so its override is github.user.css, not Github.user.css.
/* github.user.css: loads only while the GitHub theme is active */
#write blockquote {
border-left-color: #0969da;
}
We prefer this approach over editing any theme file you didn't write. Your overrides survive Typora updates, and when a theme author ships a new version, you drop it in and your tweaks still apply. The details are in Typora's Add Custom CSS page. Override files are also where you set the CSS variables that style Mermaid diagrams in Typora.
Writing Your Own Typora Theme From Scratch
A custom theme is one CSS file with a lowercase name. Use only letters and hyphens, and Typora turns the name into a menu label: my-first-typora-theme.css appears as My First Typora Theme. Window-wide rules such as background and base font size go on html. Rules for your writing go under #write, the element that holds the document.
Typora's guide to writing a custom theme recommends overriding its CSS variables for colours and fonts. Here's a compact starting point:
/* paperlight.css: shows as Paperlight in the Themes menu */
:root {
--bg-color: #fbfaf7;
--text-color: #2b2b2b;
--side-bar-bg-color: #f1efe9;
--primary-color: #2f6f9f;
--monospace: Menlo, Consolas, monospace;
}
html {
font-size: 16px;
}
#write {
max-width: 760px;
font-family: Georgia, serif;
line-height: 1.7;
}
#write h1 { font-size: 2rem; }
#write h2 { font-size: 1.5rem; border-bottom: 1px solid #ddd; }
#write blockquote { border-left: 4px solid var(--primary-color); padding-left: 1em; }
@media (prefers-color-scheme: dark) {
:root {
--bg-color: #1e1f22;
--text-color: #d8d6d0;
--side-bar-bg-color: #26272b;
}
}
Two rules from the docs are easy to miss. Set the default font size on html and size headings in rem, or the custom font size in Preferences stops working. And prefer plain tag selectors like #write h3 over Typora's internal classes, because Typora outputs the same h3, table and blockquote tags other Markdown renderers do.
One honest limitation: the variable names aren't a frozen API. Typora's docs say they may change, so check them in DevTools against the version you run.
Testing a Typora Theme Against Every Markdown Element
A theme that looks good on two paragraphs can still break on a table or a task list. Keep a test document that uses every element you care about, and open it each time you change the CSS.
The document below is a decent start. Use the Export HTML button and the HTML you get uses the plain tags your selectors target: h1, blockquote, table, list items and the checkbox input of a task list. It's a full HTML document, but it doesn't apply Typora themes or any CSS of yours.
To inspect live styles inside Typora, open its DevTools. On Windows and Linux, use View → Toggle DevTools. On macOS, the Add Custom CSS page says to turn on Help → Enable Debug and then right-click and choose Inspect Elements. The newer About Themes page points macOS users to Safari's Develop menu instead. If one route is missing in your version, try the other.
The official typora-theme-toolkit repository still exists, but its README marks it deprecated and recommends testing inside Typora directly.
Do Typora Themes Apply to PDF and HTML Export?
Yes, by default. Typora uses the current theme for HTML, PDF and image export. In Preferences, under Export, you can pick a different theme per format, which is handy if you write in a dark theme but send light PDFs.
A few details from Typora's export documentation are worth knowing:
- Light themes only on Windows and Linux. On those platforms, PDF export and printing support light themes only.
- Small print tweaks don't need a new theme. Wrap rules in
@media printin your custom CSS, and they affect only print and PDF output. The.typora-exportclass lets you target exported content. - HTML (without styles) gives you clean HTML with no theme, for when you'll add your own stylesheet.
- Word export goes through Pandoc. It takes styles from a reference
.docxyou choose in Preferences, not from your theme CSS.
@media print {
#write { max-width: none; font-size: 11pt; }
#write h2 { break-after: avoid; }
}
This print block removes the screen width limit, sets body text to 11 points on paper, and asks the renderer to keep each H2 with the text that follows it.
Submitting Your Theme to the Typora Theme Gallery
The gallery is a GitHub site, typora/typora-theme-gallery. To list your theme, fork it, add a post to the _posts directory with the YAML fields filled in, and add a 250x200 thumbnail. Then open a pull request. Say which platforms you tested on, because users check that first.
Typora themes reward a small investment: a gallery theme for the look, a base.user.css for your fonts, and an @media print block for paper. If you'd rather see your Markdown render with no theme setup at all, write in the editor, which has a light and a dark mode but no custom CSS. For a full HTML document you can restyle with your own CSS, use the Markdown to HTML converter.