Typora 1.14.10 Mac

Typora 1.14 now shows hidden files and folders in the sidebar and introduces a floating editor toolbar for quicker formatting access. Keyboard navigation in the file tree also arrived in this release, alongside options to display non-Markdown files directly in the sidebar, according to developer appmakes.

A typical session starts with a blank page that behaves more like a word processor than a code editor. Typing a hash and a space turns the line into a heading instantly, and asterisks bold text right where the cursor sits. For a longer document — say, a project readme — adding a table of contents is a single bracket-wrapped command, and a Markdown table expands columns as you type. Code fences light up with syntax highlighting for nearly three dozen languages, and LaTeX blocks render math notation inline without a separate preview pane. The new floating toolbar puts common styles a click away, which helps when muscle memory for Markdown syntax hasn't kicked in yet.

Switch the theme before your first file

A clean install ships with sensible defaults, but three adjustments make the editor feel more like a tool you own. Head into Preferences via the menu bar before creating your first file.

Switch the default theme under Appearance. The stock themes ship with tight line spacing that some writers find cramped; Newsprint opens the leading and adds a subtle serif face that mirrors a typeset page. Dark-mode users gravitate toward Night or the third-party Pixyll theme, both of which dim the chrome without washing out code blocks. Themes are plain CSS files stored in the application bundle, so tweaking font size or link color is a matter of opening one in a text editor.

Next, disable Smart quotes and Smart dashes under the Editor section if you write technical documentation or any prose destined for a codebase. Curly quotes break JSON keys and YAML strings, and Typora’s substitution is aggressive by default. While you are there, check Show line numbers only for source-heavy work; the margin adds visual noise during draft composition.

Finally, set a custom export folder under Export. Typora can write HTML, PDF, and Word files alongside the Markdown source, but scattering exports across your Documents folder gets messy fast. Pointing output to a _exports directory inside each project keeps finished files from mixing with working notes. The app remembers the preference per file tree, so a docs folder and a blog folder each stay tidy.

One way a documentation lead uses it

A technical writer maintaining an internal knowledge base for a forty-person engineering team opens Typora each morning to the same sidebar: a repository of thirty Markdown files organized by feature area. Hidden files are now visible in the file tree as of version 1.14, so configuration templates prefixed with a dot sit alongside readme guides without switching to Finder.

Monday’s task is updating the authentication-service runbook after a breaking API change. The writer drops a collapsible <details> block below the new endpoint table — raw HTML passes through Typora’s parser without escape — and wraps the deprecated flow in a fenced block titled “Removed in v4.” A colleague on Windows opens the same file in their own editor; the Markdown source stays portable, and the live preview confirms the rendered hierarchy. The floating toolbar gets one click for a strikethrough on the old SLA paragraph, then the writer exports a PDF with a single File menu action and attaches it to the sprint ticket. No preview window to toggle, no raw syntax to scan for errors.

Writers who hate the left-right eye flicker

Mac users who split their day between prose and lightweight markup stand to gain the most. The WYSIWYG model suits anyone who finds split-pane Markdown editors jarring — the constant left-to-right eye flicker breaks rhythm during long writing sessions. Students assembling lecture notes with inline LaTeX equations see formulas render as they type, which matters more when the material is unfamiliar and every keystroke needs immediate visual confirmation.

Software developers writing readme files, changelogs, and documentation benefit from the native code-fence handling and pandoc export path. The 1.14.10 release fixed a pandoc export bug from source mode, so command-line fans who toggle into raw Markdown view for bulk edits can trust the output pipeline again. Bloggers who publish static-site content value the frontmatter support and the ability to ship a post as clean HTML without a build step.

People who need a reading-mode markup parser without an editor attached — journalists reviewing submitted copy, editors skimming contributor drafts — use Typora as a lightweight Markdown viewer. The app opens .md files in rendered view by default, so scanning headers and pull quotes feels closer to reading a formatted page than inspecting source text. For anyone whose workflow touches Markdown more than twice a week, the removal of the preview-window paradigm alone reshapes how quickly ideas hit the page.

Version 1.14 fixes clipped content in the welcome panel and resolves a pandoc export issue that occurred when exporting from source mode.

• macOS 10.13.6 or later
• Apple Silicon or Intel processor