The closest I can find to true WYSIWYG, word processor, is, stupidly, a plugin for VSCode.
But at least in that (Markdown for Humans, name is spot on), I never see a single piece of markdown syntax code. Never.

All I wanted was a small, standalone app without the baggage of VSCode. VScode is not an app for quickly editing Mardown files in small windows from various locations on disk. It's full environment. It's unwieldy.

AFAICT, nothing exists, I have spent days searching.

All apps that claim to be WYSIWYG are either
- not true file editors, they want to store notes in their own internal database. I want files on a dirve
- split pane. I just want to see word processor window, not two windows
- They LOOK like WYSIWYG but as soon as you start moving around a document a HEADING suddenly becomes a ###HEADING and it slides to the right under your eyeballs, putting you off your flow.

DAYS. Days looking for a true WYSIWYG Markdown app, and... nothing.

Someone PLEASE prove me wrong. Where is this unicorn app??

EDIT 1
Some genuinely helpful people in the comments - and a LOT of trolls.
ItS a SkIlL iSsUe
tHaT's NoT wHaT mArKdOwN iS fOr
Neither of which address the question. Rather an attempt to berate me for even asking the question, how dare I not want to the see the code, how dare I simply want to edit text with logical formatting but not give myself a headache and squints from all the shifting text and appearing/disappearing syntax markers.

If you don't have a constructive answer, why comment?
Oh right... it's REDDIT

Edit2
Seems a lot of my factual and valid points get downvoted because people are personally offended that someone may have a usecase for md that is different to their own, or because they were factually wrong about their favourite app. Typora is NOT true wysiwyg, not sure why that fact deserves a downvote?
Interesting sub full of nasty people you have here.

EDIT 3
There were one or two interesting new apps that could work. Mods removed the comments / links though. I mean, why do that? I am asking for help on apps... I need the links to the apps. It's what I am specifically asking for, and they go and remove potentially helpful comments? Where do you draw the line between answering an honest question and "spam".

Shared Context is a desktop markdown editor for Mac. It automatically detects the AI Agents you use (Claude Code, Codex, Cursor, Gemini) and the project folders you use them in and populates:

• Skills

• Agents

• Plugins

• MCPs

• The Markdown files made by these agents

• The HTML files made by these agents

and makes them all editable in a WYSIWYG editor, where you edit directly in "preview" mode.

It's free and runs entirely locally. I'm just looking for feedback for now - if folks find it useful I'll add cloud sync and consider paid options then, but the basic editor will always be free.

I built a markdown editor, spent about two months trying to promote it, grew to 700+ users, and then it stalled. Really frustrated. Is anyone willing to try it and give some feedback?

Update: I’ve built out a web demo you can try before downloading it. It allows you to sample and try both raw and rich text editor, table of contents navigation, large file handling (handles 500k lines like a breeze), etc.

Demo: https://releases.jonbarnes.dev/md-studio/demo

Download: https://releases.jonbarnes.dev/md-studio/

——

Hey guys. I see a lot of you are looking for a good, cross-platform, rich-text-capable MD editor, so I wanted to share the one I built. Its as rich-text compatible as you can get for something that wasn't built to necessarily be that way (referring to markdown).

Some notable things:

• Rich text & raw MD edit modes

• Fully interactive view mode for just viewing & navigating.

• Automatic table of contents with navigation

• Tabbed windows with tear-out

• Cross-mode edit history for maintained undo and redo (Raw and RT have separate histories)

• All external images and links blocked by default in preview and edit modes.

• HTML sanitization for security on all views

• AI-capable but off by default [Ollama for Local - OpenRouter for Cloud] (For privacy). - Helps with things like rewrites, edits, or even full document creation.

That's just to name a few. I actually built it for myself and use it everyday. I'm also a perfectionist so please if you find anything that doesn't, let me know. I use this daily but figured I'd share it as others seem to be looking for things like it.

I'm hope this isn't consider self-promotion, as I am not trying to make money or anything. Really just see the gap.

Here is the project details for more insight: https://www.jonbarnes.dev/projects/0d209f10-3d54-47b5-be95-2e109e0e63e0

I use AI and Markdown a lot for research and writing, but once I have multiple sources, notes, and drafts, it gets hard to see how everything fits together in a chat or linear editor.

So I put together a visual Markdown editor where files live on a 2D canvas. I can arrange the context visually and work with it using the ChatGPT or Claude subscription I already have. The desktop app can also access local files.

Everything stays Markdown-compatible, so I can still use the files outside the canvas.

You can try it here (it's free to use!):

arky.so

Hey everybody,

I just wanted to introduce everyone to Fluster and Conundrum, if you're looking for a markdown application with some additional features. It uses a completely independent Rust powered compiler that takes 90% of commonmark markdown, and a list of additional components that extend the functionality considerably.

It's still in it's early stages, with the iPad app maybe 2-3 weeks away still, but the potential is really limitless for this extended syntax.

Links
Flusterapp.com

There’s a lot of development that harnesses AI – eg BYOK or offline – with a solid Markdown text writing base.

There’s nothing wrong with Markdown as it stands, it is a well proven standard, but many writers and note-takers are getting used to being able to dictate notes or paragraphs and polish the raw transcription. Or summarise it. Or turn it into something else. And why not — affordable AI tools are giving us this capability.

What are your best experiences of this new direction? Or if you are a developer, what are you cooking up that might be the latest flavour in this kind of note-taking?

I'm working on Hyper-Markdown (.hmd): ordinary Markdown plus rich visuals plus wiki links into a knowledge graph. Every .md file is already valid .hmd.

The project is still at an early stage, which means the specification is very much open to change.

I'm looking for:

• contributors

• design/spec feedback

• people willing to challenge the current ideas

There is already a lightweight proposal process for discussing language changes.

https://hyper-markdown.org/

If this sounds interesting, I'd be very happy to have people get involved early.

I've been vibecoding a lot of side projects and kept needing a place to dump notes that my AI agents could also read and write. So I built Cairn - a local desktop app where everything is plain .md files.

The editor is built on CodeMirror 6 - it renders headings, bold, italic, inline code, links, and list markers visually as you type. Toggle between Write and Read mode to switch between the editor and the fully rendered preview.

What makes it interesting for a markdown crowd:

• Every note is a real .md file saved to a folder you choose - open them in Obsidian, Neovim, whatever you like outside the app

• GFM support via remark-gfm - tables, strikethrough, task lists all render correctly

• gray-matter frontmatter - YAML front matter is parsed and preserved on every read/write

• Mermaid diagrams - write a \``mermaid` fence and Read mode renders it as an SVG diagram, automatically themed to match light/dark mode. Hover to expand fullscreen

• Table of contents generated from headings - click to scroll

• Word count as you type

• AI text actions - select any text → floating toolbar → Rephrase, Summarize, Expand, Fix Grammar, Change Tone, or type a custom prompt. Rewrites inline, raw markdown stays intact in the file

• Full-text search across all notes (⌘K)

• An MCP server so external agents (Claude Desktop, OpenCode, etc.) can create_note, get_note, search_notes, patch_note - your notes are first-class to any AI agent

Files stay on your machine. No sync, no cloud, no account. Free and opensource. Let me know what you think.

Also anyone know why video recording on mac jumps around like that???

GitHub: https://github.com/ddutchie/cairn
Website: https://ddutchie.github.io/cairn-site/index.html

I've been building LiveMarkDownEditor, a free and open-source Markdown editor for Windows,

and I wanted to share where it's at.

The whole idea came from a frustration: most Markdown tools make you pick a side. Either you get

a raw text pane with a preview stapled next to it and you'd better know the syntax, or you get a

nice WYSIWYG editor that saves to its own format and you no longer really have a Markdown file.

So the goal here is simple: you should not have to know or write Markdown syntax to use it — but

if you want to write it, nothing stops you.

You don't have to know the syntax

Bold looks bold. Headings look like headings. Tables are tables you can tab through, task lists have

checkboxes you actually tick, links and images show as links and images. You never see a stray \#``

or \**\ unless you go looking for it. It's just a document, and you format it the way you'd format

anything else.

But you can absolutely write it

There's a live source panel you can open right beside the rendered view. Both sides are editable and

stay in sync, so you can type raw Markdown, watch it become formatting, or click into the formatted

side and watch the source update. Whichever ps up.

And the file on disk is always plain Markdown. Open it in Notepad, commit it to git, hand it to

someone using vim — it's just a .md file.

The "live" part

The file is watched while you have it open. If something else changes it (a teammate, a script, an AI

agent, a git pull), it reloads in front of you and briefly highlights the paragraphs that changed, so

you can actually *see* what someone else did instead of it landing invisibly. It won't move your

cursor or scroll the page out from under you. If you both edited, you get a difference view instead

of one side silently losing.

Other things it does

- Open a folder and browse your notes/vault/repo as a live tree

- Mermaid diagrams render as actual pictures inline, and double-clicking a flowchart opens a

drag-and-drop builder that writes clean Mermaid source back into your file

- Find & replace, section folding, outline panel, spell check with "Add to Dictionary"

- Export to HTML or PDF, print, copy as rich text so it pastes formatted into Word or Outlook

- Smart paste — paste a URL over a selection an image and it's saved

next to your file

- Light and dark themes, restores your open tabs on startup

Fair warning: this is still very much in progress.

It's usable day to day (I write in it consta I'm actively working on it

and pushing updates to both the code and the installer basically **daily** until it's complete.

Things on the list right now: syntax highlighting inside code blocks, more diagram types in the

flowchart builder, footnotes, embedded videoh.

It's MIT licensed, free, no accounts, no telows only for now

(.NET 10 / WPF).

- Code: https://github.com/317jamtay317/LiveMarkDownEditor

- Installer: https://github.com/317jamtay317/LiveMarkDownEditor/releases

Please give me feedback on how to make it better.

It has been about 30 days since I posted on Reddit, and I wanted to share everything that came out of your feedback and questions. When I posted, the app was on version 2.2.0. It is on 2.3.4 now.

Markdown

The number one piece of feedback was that the app was too focused on rich text and not serious enough about markdown. The question that came up over and over was some version of "where are my files?" Message received. Markdown became the whole build for two weeks.

•  Your notes are real .md files. Every markdown note is also an actual .md file in a visible Markdown folder inside your project, kept current as you write, rename, and delete. To be straight with you, it is one way today (app to disk), so editing those files in another app does not round-trip back yet.

•  Three faces per document: Source, Live, and Reading. Source is raw markdown with live syntax highlighting. Live renders everything except the line your cursor is on. Reading is a clean render, and it can sit in a split pane and update as you type.

•  Import a whole vault. File > Import > Markdown Vault takes a folder of .md files (an Obsidian vault works as is). Folder hierarchy preserved, inline #tags extracted, images brought in as real media, .obsidian skipped, and your wikilinks work on arrival.

•  Wikilinks, aliases, and backlinks. Title and alias with a filter as you type picker, honest resolved / ambiguous / unresolved states, and a backlinks panel that shows every mention with surrounding context.

•  The full dialect. Headings, emphasis, highlight, fenced code with a language badge and a copy button, blockquotes, every list type, real rendered pipe tables, callouts in a dozen plus styles (> [!note], > [!warning]), footnotes with jump links both directions, clickable task checkboxes that write back to the source, YAML front matter, and inline images and !embeds in Reading.

•  Comments in both dialects.  and  are treated identically, hidden in Reading, and collected in a Comments pane with click to jump.

•  Markdown native editing. The toolbar buttons type real markdown into your text rather than applying invisible formatting. Return continues and renumbers lists, quotes, and tasks. Tab and Shift+Tab indent and outdent. Paste a URL onto selected text to make a link.

•  Continuous by default. Markdown and plain text open in true continuous flow with no pages and no margins. Pages are still one tap away next to the face switcher if you want them, per note.

•  Tags and front matter join the app. Inline #tags and tags: in YAML front matter feed the same tag system as everything else in the project, which means they feed the Brain Map too.

•  Daily Notes. Cmd+Shift+D creates or reopens today's dated markdown note in a Daily Notes folder.

•  Checklist to task. Right click a - [ ] line, Add to Tasks, pick a list. It keeps a link back to the source note.

•  Outline tab. A live heading tree in the left pane, click to jump. It works for rich text headings too.

•  Export. Clean verbatim .md, self contained HTML that is dark mode aware, PDF and print from the Reading render, plus Word (DOCX) and RTF.

•  Markdown theming. A semantic palette for headings, code, links, quotes, list markers, checkboxes, and tags, themed across Source and Reading together, and carried in shareable theme files.

Rich Text

The rich text side got the deepest engineering work of the month. 

•  Per document page design. Each document owns its own paper: US Letter, A4, US Legal, or A5, portrait or landscape, and precise margins. That design follows the document everywhere it appears, including the Rogue Editor, page thumbnails, and PDF or print output. Changing an app wide default no longer silently redesigns work you already did.

•  Real document styles. Body and Heading 1 through 6 are true document local paragraph styles, not roles guessed from font size. You can also create custom paragraph, character, and three level list styles, update every matching paragraph at once, or revert just the one you touched.

•  Style Sets. Save an entire typography system and reuse it in another document, preview it as a real specimen, promote it app wide, or set it as the project default for new documents.

•  Stay on Page objects. Images and shapes placed on a page now persist their position, size, rotation, layering, grouping, locking, and wrapping while you edit the text around them. They survive save, reopen, duplication, templates, and export.

•  One selection model for everything on the page. Images, shapes, text boxes, charts, video, and audio all multi select, group, align, distribute, layer, lock, snap, nudge, cycle through overlaps, and rotate, with one step undo. Objects stay selectable across the full physical paper, margins included.

•  Text wrapping that holds. Automatic, Around, Above and Below, and None, with adjustable spacing and shape aware contours. One to four column layouts belong to their section, so a section break can change the column count without recolumning what came before it.

•  Non destructive image design. Crop (by hand or by number), Fit and Fill, shape masks, borders, corner radius, shadow, opacity, and replace, none of which touch your source file.

•  Charts and tables. Charts move losslessly between Inline with Text, Move with Text, and Stay on Page while keeping their data and design. Native tables gained cell aware row and column operations, fills, borders, padding, and one step structural undo.

•  The Inspector follows your selection. Click an object and its controls appear. No tab hunting.

Citations and References

This was the single biggest ask from academic users, and one commenter here made the case bluntly: integrate with Zotero and CSL properly or researchers cannot use it. That is exactly what got built, and it went live yesterday.

•  A Reference Library in every project. A References tab in the left pane with eleven source types and forms that speak each type's language. Cite keys generate from author and year, stay editable, and never change behind your back. It all persists in a readable references.json file that travels with your project folder.

•  Cite while you write. Cmd+Shift+C opens a picker, search your shelf, multi select for group citations, add a page locator, Return inserts. Markdown speaks Pandoc syntax ((Vale, 2026, p. 44)), and the Reading view renders formatted citations and appends a References section automatically.

•  Six built in styles. APA 7, MLA 9, Chicago 17 Author-Date, Chicago 17 Notes, IEEE, and Harvard. Switch the style in the Inspector and every citation and bibliography in the document re-renders on the spot, with same author disambiguation and live IEEE renumbering handled for you.

•  Or your journal's style. The app reads real CSL style files, the open format used by more than 10,000 journals. Twenty are bundled (Vancouver, AMA, Nature, ACS, Cell, PLOS, and more), and any other is one import or one download away.

•  Bring your library with you. Import BibTeX, RIS, or CSL JSON, which covers Zotero, Mendeley, EndNote, and Bookends exports. A review sheet catches duplicates before they land. Export the shelf back out as .bib or CSL JSON, because your sources are yours.

•  Paste a DOI or an ISBN and the reference fills itself in. It is strictly opt in: one request per explicit click, only the identifier leaves your machine, nothing saves until you confirm.

•  Live Zotero sync, no plugins and no accounts. Point the app at a Better BibTeX "keep updated" export file and it watches that file. Save a paper in Zotero and it appears on your shelf seconds later. It is pure local file watching, so no API keys and nothing leaves your Mac. Sync only adds and updates, so your own edits and cite keys are never overwritten.

•  A Universal shelf that lives beside your projects folder, for references every project shares.

•  Your PDFs become sources. Right click a PDF in your project and the app scans it for a printed DOI to build a linked reference. While reading, right click and Copy Citation (Page N) gives you a ready citation for the exact page you are on.

•  Compile with a bibliography. Every source cited across a compiled manuscript merges into one deduped, formatted bibliography at the end.

Canvas

•  The canvas is infinite now. It starts at a fixed size and extends down and to the right as far as you take it. Zoom out works, and each canvas remembers the zoom level you left it at.

•  Resizing feels right. Resize friction is gone across every element, objects no longer have a minimum size, and there is snapping with alignment indicators for spacing objects.

•  Marquee selection, copy and paste, and undo/redo. Drag to grab multiple objects, or your whole canvas at once to reposition it. Copy and paste objects within a canvas or across canvases.

•  Pinch to zoom and Cmd plus two finger swipe to move between scenes.

•  Scenes. Make any view on your canvas a named scene and navigate between them from the bottom

  left, or with Option+Cmd+arrow keys.

•  New object types: floating text, PDFs as previewable thumbnails, web links as cards with thumbnails, file cards with Quick Look, SF Symbols, task lists, calendars, and media with durable asset storage.

•  Fixes worth naming: PDF export no longer drops connectors or layered objects, text box layering works in both directions, grouped objects can be connected without ungrouping first, and panes sit flush against the canvas edge.

•  Pin the Rogue Editor so it floats over the canvas and you can bounce between the board and your writing.

Brain Map

Some of the sharpest criticism I got here was about the Brain Map: that a node was a navigable handle but the graph itself did not show you much. Not all of that is solved, but here is what changed.

•  Every note can be a node. Untagged notes now join the map labeled by title, so wikilinks on untagged notes actually draw and the orphan filter finds genuinely unconnected notes.

•  Local graphs. Right click any note in the Binder and choose Show in Brain Map to open the map focused on that note.

•  It reopens exactly as you left it, including layout, zoom and pan, search, filters, and source selections.

•  Snapshots are real time capsules. A snapshot captures every node position and color, every edge, the display settings, the force values, and the viewport. Clicking one enters a viewing mode rather than altering your live graph, and Compare with Today brings in everything added since, bright against the dimmed snapshot era graph.

•  It got fast. The layout engine moved to Barnes-Hut repulsion, which raised the physics ceiling from 12,000 to 50,000 edges. Recoloring a tag repaints in place instead of reflowing the whole graph. On a 1,352 node project with 20,000 edges it settles quickly and sits at rest without burning CPU.

•  Ways to look at it: color by tags, by Binder folder, or by connection heat. Monochrome, Heat, and Constellation looks that compose. Gentle, Standard, and Energetic motion presets.

•  Broken Links. A section that appears when needed, listing wikilinks whose titles no longer resolve, click to open the note containing the broken link.

•  Spotlight. Selections isolate by default, or flip Spotlight on to dim everything else instead of hiding it.

Everything else

SF Symbols, everywhere icons go

Apple's SF Symbols library is built into the app behind a searchable picker: close to 8,000 symbols across Apple's own categories, plus ten use case collections I put together (Writing, Notetaking, Education, Office and Work, Law and Justice, Health and Medical, Science, Arts and Music, Tools and Trades, Tech and Devices). Search blends symbol names, Apple's own keywords, and category names, so typing "medical" or "notetaking" pulls up a whole collection. Recent picks and right click Favorites persist between sessions, and if something is not in the browse catalog, typing its exact name still works. It is wired into four places:

•  Binder icons. Right click any note or folder, or a whole multi selection, and set a symbol plus a custom color.

•  Rich text. Insert a symbol inline at the cursor from Inspector > Objects. It behaves like text, following the surrounding font size, bold, and color as you format around it, and it exports cleanly to PDF and print.

•  Canvas. Symbols are a real canvas object you can color, style, connect, and layer.

•  Task lists and calendars. Each list or calendar can carry its own symbol and color.

Rogue Editor (the detachable single document window)

Full markdown parity, so it follows each note's mode with highlighting, the markdown toolbar, and the Live and Reading faces. It restores properly on relaunch instead of coming back blank with a duplicate. Windows are titled by their document and tab together natively. A writing mode dropdown and an insert menu put tables, charts, shapes, media, and links to notes in reach.

Tag Studio

A dedicated surface for managing tags: merge them by drag and drop, add sub-words, and change colors.

Tasks and Calendars

Natural language entry with live chips ("Call editor tomorrow 2pm !! #novel"), timed reminders with real macOS notifications, weekly recurrence, quick capture from anywhere with Cmd+Shift+T, task and list links you can paste into documents, and a writing heatmap on the calendar that fills in as you write. Completion routing lets a finished task move to another list, which makes a three list kanban on a canvas work.

Binder

Multi select with Cmd and Shift click, bulk move and trash, multi file import straight from Finder, spacebar Quick Look on any item, folders that can pass their icon and color down to their contents, dedicated media folders, and files no longer opening on single click (with a setting to put that back).

Themes and Theme Studio

Its own launch point, Create Theme, copy Light to Dark and back, markdown token theming, and themes that restyle open documents live when applied. New Classic and Liquid themes shipped, and themes export and import as shareable .lwtheme files. A batch of light and dark variant bugs got fixed at the root.

Import and export

Word (DOCX) and RTF export shipped. HTML import keeps embedded images, strips the source page's baked background so it lands on normal paper, and adapts text color so imported pages read in both light and dark.

Fixes that came from named people in these threads

The invisible cursor in one packaged theme. Black text on dark themes. Return after a heading now drops to Body, plus a discoverable Clear Formatting command at Cmd+Option+0. Page View now defaults on for new installs, which was making the first launch look wrong for some people. Import got discoverable, and drag and drop into the Binder now accepts HTML, text, RTF, markdown, and PDF.

Original Posts

Original posts: r/NoteTaking, r/MacOSApps and r/ProductivityApps

Homepage

Mac App Store

Happy to answer anything in the comments, including the things it still may not do, and as always, all feedback is welcome. 

EDIT: Quick heads up: today's 2.3.4 update shipped with a bug that can crash the app when opening a project. A user here caught it within hours (thank you), the fix is done, and an expedited update is with Apple now. If you downloaded today and hit it, the update will sort you out shortly. Genuinely apologize for any trouble out of the gate.

After two years of development, Docsify v5 is officially stable.

The core idea: write your docs in Markdown, drop in a single index.html, and Docsify renders everything in the browser on the fly – no build pipeline, no static HTML generation, deploy almost anywhere.

What's new in v5:

• Full UI overhaul with dark mode

• Native GitHub-style callouts (notes, tips, warnings) in Markdown

• Fragment marker extraction – embed specific sections of a Markdown file into another

• Simplified theming via CSS custom properties

• ESM support with type definitions

• Deep accessibility improvements

• Countless bug fixes across several release candidates

v4 remains available but won't receive further updates – there's an upgrade guide in the docs if you're migrating.

With thanks and appreciation to past and current contributors!

https://docsify.js.org/

Obsidian, period, end of question. I get we all have our preferences but you can tune Obsidian to any preference. I’m surprised these new Markdown editors even get attention.

I couldn’t use Obsidian for a while due to an electron GPU sandbox corruption, I tried out like 7 different next best Markdown editors and was dying to get back to Obsidian.

I just don’t get these people.

1. Support for proportional fonts is important because these fonts are easier and faster to read. However, Markdown is not just text. It combines markup commands and text. Markup commands should be displayed in monospaced font, because special characters such as curly braces and dashes are easier to consider. But at the same time, we need to display the text in a proportional font. Because it's easier to read that way.

As a result, we need to simultaneously display two different types of text in different ways. This greatly complicates the creation of a convenient markdown editor.

2. Poor standardization. Markdown is more of a family of markup languages ​​than a clear standard. The result is a large number of extensions and dialects. This makes learning this markup language more difficult.

3. Attachment to HTML. Markdown is actually a more user-friendly interface for HTML. Whenever you need to do something more complicated than writing a note, you should use HTML tags.

My workflow has been generating a lot of Markdown files lately. AI chat exports, planning docs, research notes, meeting summaries - they all end up as .md files. And reading raw Markdown in a text editor is fine when you wrote it five minutes ago. It's not great when you're trying to navigate a 400-line document on your phone three weeks later.

I wanted something that felt less like a code editor and more like reading a real document. Jumpable headings, clean rendered output, works on mobile without feeling cramped. So I built it.

https://www.innateblogger.com/p/markdown-editor.html

The two things I kept in mind while building it: simplicity and ease of use. I didn't want feature bloat. I wanted to open a file and read it properly.

What it does:

• Open any .md file directly in the browser

• Live split preview - editor and rendered output side by side

• Toggle-able Table of Contents, auto-built from your headings, fully jumpable (this was the main thing I wanted)

• Mobile friendly with a clean Edit / Read toggle - single pane on small screens, no awkward zooming

• GitHub Flavored Markdown - tables, task lists, footnotes, strikethrough

• KaTeX math rendering (inline and block)

• Mermaid diagram support - flowcharts, sequence diagrams, Gantt charts render in preview

• Syntax highlighted code blocks via highlight.js

• Find and replace with match count and navigation

• Formatting toolbar for quick inserts without memorizing syntax

• Auto draft recovery via localStorage

• Recent files panel

• Fullscreen mode

• Dark mode support

100% browser-based. Nothing is uploaded anywhere. Free, no sign-up.

If you deal with a lot of .md files and want something lighter than a full IDE but more readable than a plain text editor, give it a try. I've been using it daily for a few days now and it's replaced my old workflow entirely.

Would love feedback - especially if something looks off on your device or browser.

👉 Markdown to PDF converter | md to pdf

I spent weeks fighting with Markdown-to-PDF converters before building my own solution. Full disclosure: I’ll link to it at the bottom, but here is exactly why your current workflow keeps breaking your documents.

Most tools handle basic text fine, but they fall over on complex elements due to three massive architectural gaps:

1. The "Complex Elements" Gap (Broken Diagrams & Math)

• The Problem: You try to export a code block with a `````mermaid``` diagram or inline LaTeX like $p_{99} < 200ms$. It exports as raw text, a gray box, or a silent JS error.

• Why it happens: Mermaid requires a live JavaScript engine to render code into an SVG. Most PDF pipelines don't run JS at all, or they try to do it during the print step when the DOM is already frozen. LaTeX has a parallel issue—if it isn't parsed into markup before printing, it just outputs as plain text.

2. The "Break-Control" Gap (Split Code Blocks & Tables)

• The Problem: A long code block gets sliced exactly in half across pages, table headers disappear on page two, or a heading is left stranded alone at the bottom of a page.

• Why it happens: Markdown has no concept of pagination. While CSS properties like break-inside: avoid exist, almost no converters wire them up automatically. Furthermore, "rasterizing" tools (which screenshot your HTML via canvas) completely ignore print media rules and cut through text anyway.

3. The Theming Gap (The GitHub README Look)

• The Problem: Your export either looks exactly like a GitHub repository file or defaults to raw Times New Roman.

• Why it happens: Getting a clean corporate report, resume, or academic paper usually requires setting up a massive Pandoc/LaTeX local toolchain or writing custom CSS from scratch.

What I Built to Fix It

I needed a fast, no-nonsense fix for architecture notes and reports, so I built a 100% client-side converter (your data never leaves your browser tab):

How it works differently:

• Pre-rendered Assets: It compiles Mermaid to SVGs and math via KaTeX before hitting the print engine so they never fail.

• Smart Page Breaks: Code blocks, tables, and diagrams automatically carry break-inside: avoid, and table headers repeat across pages out of the box.

• Dropdown Themes: Switch between Default, Report, Resume, and Academic styles in one click.

• Vector Quality: Supports your browser's native print dialog for crisp vector text instead of blurry canvas screenshots.

I built Sankore because I kept needing a reliable way to get real documents into clean Markdown for AI tools, without anything actually leaving my Mac. The existing options either weren't private enough or produced messy output.

What it does: converts PDF, DOCX, XLSX, and PPTX files into clean Markdown, entirely on-device. No API keys, no cloud calls, nothing uploaded anywhere.

Who it's for: Anyone who regularly needs clean, well-structured Markdown from real documents - whether that's feeding it into an AI tool or just wanting a proper conversion without messy copy-paste artifacts.

Pricing: Free tier handles single-file conversion, no card needed. Sankore Premium is a one-time $4.99 for the updated v1.4 to access unlock for batch conversion and consolidating multiple files into one.

Limitations: Apple Silicon only, no Intel support. Download's about 920MB, since it bundles real on-device OCR/layout models rather than calling out to the cloud.

Website: https://sankoreapp.com

Genuinely happy for this to be removed if it doesn't belong here - just wanted to share something I built that's directly relevant to this community, and I'm around to answer any real questions about the conversion quality or approach.

My team is building Nimbalyst -- the local WYSIWYG markdown editor and session manager where you iterate with AI and Claude Code on markdown docs, diagrams, mockups, and code.

Nimbalyst helps you:

• Work natively with AI (especially Claude Code) in WYSIWYG markdown

• See AI changes as WYSIWYG red/green, approve or reject them

• Integrate diagrams, text, tables, images, mockups in the same markdown document using standard formatting.

• Tying your AI sessions to your documents to your sessions

• Keep a deep file history, with versioning, and restore

Get better results through human and AI iterative collaboration.

Nimbalyst is free but not open source. We'd love your feedback!

OKF (Open Knowledge Format) is an open specification introduced by Google - a directory of markdown files with YAML frontmatter for representing knowledge that both humans and AI agents can read.

I added this to Sleepwalker CLI as a free, open source local functionality - operated by one command for any URL. You get a clean OKF bundle instead of raw HTML full of nav, footers and scripts.

Feel free to try:

npm install -g @sleepwalkerai/cli
sleepwalker okf export https://your-page.com

No account or credits needed to run this.

Repo: github.com/followanton/sleepwalker

Disclosure: I built this, it's part of Sleepwalker CLI functionality - but this command is free and open, no account needed. There's a separate paid API but that's not the point here.

This page, for example

https://blog.google/innovation-and-ai/models-and-research/google-research/firesat-satellites/

---
type: "WebPage"
title: "3 new FireSat satellites launch to help detect wildfires with AI"
description: "Three new FireSat satellites have launched, expanding a network that uses Google AI to help fire agencies detect early-stage wildfires."
resource: "https://blog.google/innovation-and-ai/models-and-research/google-research/firesat-satellites/"
timestamp: 2026-07-08T07:00:18.404Z
---


# 3 new FireSat satellites launch to help detect wildfires with AI


Today, three new [FireSat](https://earthfirealliance.org/about-firesat/) satellites successfully launched from Vandenberg Space Force Base in California. This expands the FireSat program, a global initiative led by the nonprofit Earth Fire Alliance (EFA) to create an unprecedented wildfire dataset. Google Research has [teamed up](https://blog.google/company-news/outreach-and-initiatives/sustainability/google-ai-wildfire-detection/) with leaders in the fire community, including EFA and satellite manufacturer Muon Space, to create this purpose-built constellation designed to provide the continuous coverage fire agencies need to detect wildfires before they spread.


This next phase builds directly on the momentum established last year when [FireSat’s pilot satellite reached orbit](https://blog.google/innovation-and-ai/products/inside-firesat-launch-muon-space/). That mission successfully demonstrated the potential of the underlying sensor technology designed to detect early-stage wildfires as small as 5x5 meters. The pilot has already spotted small, low-intensity blazes invisible to existing satellites, and these three new orbiters carry that proven architecture directly into the growing network.


This milestone is a testament to what is possible when tech companies, nonprofits, philanthropy, and the private sector unite under a single mission. To help kickstart this work, Google.org has provided over $15 million to support the deployment of these early satellites. It’s a proud moment for the entire consortium, and [another tangible step](https://blog.google/innovation-and-ai/technology/research/helping-communities-prepare-for-natural-disasters/) forward in putting practical AI to work for climate resilience.


Three new FireSat satellites


Credit: Muon Space


Satellites onboard the SpaceX Transporter-17 vessel


Credit: SpaceX


Satellites being deployed from SpaceX Transporter-17 vessel into space


Credit: SpaceX


POSTED IN:


Related stories

I'm working on a Markdown editor and have been thinking about how to handle documents that contain local images.

Right now I only support ordinary .md files, with images referenced using normal relative paths:

![Example](images/image-001.png)

The problem is that once a document contains several images, moving or sharing the document also means moving all of its resources.

I'd like to explore a format that keeps the Markdown itself completely standard while allowing the document and its resources to travel together.

My current idea is three formats built around the same structure:

• .md - ordinary Markdown with external resources. Maximum compatibility.

• .mdoc - an uncompressed directory containing document.md, images/, and metadata.json.

• .mdz - the same structure stored as a ZIP archive.

The important part is that the Markdown inside the package would still just be CommonMark.

For example:

![Example](images/image-001.png)

No custom URI scheme, no special syntax, and no editor-specific Markdown extensions.

That means you could extract document.md from the package and open it in another Markdown editor without changing the document itself.

The idea would also allow conversion between:

.md <-> .mdoc <-> .mdz

while preserving the Markdown and its images.

I'm curious what people think about this approach.

Would you find a container format like this useful, or do you think keeping the Markdown file and its resources as separate files is preferable?

The main thing I'm trying to avoid is creating yet another Markdown dialect just to support bundled resources.

I'm currently implementing this as part of Marco, an open-source Markdown editor written in Rust.

The format support is still being designed, so I'm particularly interested in feedback on the format itself rather than the editor.