Show HN: OverType – A Markdown WYSIWYG editor that's just a textarea

175 panphora 50 8/17/2025, 4:13:06 PM
Hi HN! I got so frustrated with modern WYSIWYG editors that I started to play around with building my own.

The problem I had was simple: I wanted a low-tech way to type styled text, but I didn't want to load a complex 500KB library, especially if I was going to initialize it dozens of times on the same page.

Markdown in a plain <textarea> was the best alternative to a full WYSIWYG, but its main drawback is how ugly it looks without any formatting. I can handle it, but my clients certainly can't.

I went down the ContentEditable rabbit hole for a few years, but always came to realize others had solved it better than I ever could.

I kept coming back to this problem: why can't I have a simple, performant, beautiful markdown editor? The best solution I ever saw was Ghost's split-screen editor: markdown on the left, preview on the right, with synchronized scrolling.

Then, about a year ago, an idea popped into my head: what if we layered a preview pane behind a <textarea>? If we aligned them perfectly, then even though you were only editing plain text, it would look and feel like you were editing rich text!

Of course, there would be downsides: you'd have to use a monospace font, all content would have to have the same font size, and all the markdown markup would have to be displayed in the final preview.

But those were tradeoffs I could live with.

Anyways, version 1 didn't go so well... it turns out it's harder to keep a textarea and a rendered preview in alignment than I thought. Here's what I discovered:

- Lists were hard to align - bullet points threw off character alignment. Solved with HTML entities (• for bullets) that maintain monospace width

- Not all monospace fonts are truly monospace - bold and italic text can have different widths even in "monospace" fonts, breaking the perfect overlay

- Embedding was a nightmare - any inherited CSS from parent pages (margin, padding, line-height) would shift alignment. Even a 1px shift completely broke the illusion

The solution was obsessive normalization:

    // The entire trick: a transparent textarea over a preview div
    layerElements(textarea, preview)
    applyIdenticalSpacing(textarea, preview)

    // Make textarea invisible but keep the cursor
    textarea.style.background = 'transparent'
    textarea.style.color = 'transparent'
    textarea.style.caretColor = 'black'

    // Keep them in sync
    textarea.addEventListener('input', () => {
      preview.innerHTML = parseMarkdown(textarea.value)
      syncScroll(textarea, preview)
    })
A week ago I started playing with version 2 and discovered GitHub's <markdown-toolbar> element, which handles markdown formatting in a plain <textarea> really well.

That experiment turned into OverType (https://overtype.dev), which I'm showing to you today -- it's a rich markdown editor that's really just a <textarea>. The key insight was that once you solve the alignment challenges, you get everything native textareas provide for free: undo/redo, mobile keyboard, accessibility, and native performance.

So far it works surprisingly well across browsers and mobile. I get performant rich text editing in one small package (45KB total). It's kind of a dumb idea, but it works! I'm planning to use it in all my projects and I'd like to keep it simple and minimal.

I would love it if you would kick the tires and let me know what you think of it. Happy editing!

---

Demo & docs: https://overtype.dev

GitHub: https://github.com/panphora/overtype

Comments (50)

dchest · 3h ago
Looks good!

Some links I've collected in the past that describe this approach:

- https://css-tricks.com/creating-an-editable-textarea-that-su...

- https://github.com/WebCoder49/code-input

I believe https://grugnotes.com also does this for markdown.

reactordev · 2h ago
This is actually really clever. Just don’t let it balloon out to be a 500kb full fledged WYSIWYG editor, just keep it simple like you do.
bullen · 9m ago
Anyone knows a good in browser coding editor widget?

That supports color coding for different languages?

phonon · 42m ago
bloppe · 56m ago
This isn't really WYSIWYG because it keeps the formatting symbols like * or # etc.
lifthrasiir · 3m ago
Still, what you see is what you get (plus some formatting symbols). It's marginally WYSIWYG.
jackbridger · 11m ago
12 pages of docs vs it’s a textarea. Great job, gonna try it out.
janwilmake · 8h ago
Really cool! I just love the simplicity of it: has no drawbacks compared to regular textarea, but has lots of benefits. you basically improved textarea, by a lot!

I also made a similar thing a while ago called contextarea.com, maybe, I should add overtype!

ikurei · 3h ago
Having to use a monospaced font is a pretty big drawback. To me, it means I wouldn't use this for a product that wasn't intended for a techie programmer audience.

Not that it isn't a really cool project! I'm only saying it has clear drawbacks.

mmastrac · 3h ago
This is pretty nice, though I'd suggest you call it a transparent syntax highlighter.

For https://grack.com/demos/adventure/, I used a hidden <input text> for something similar. I wanted to take advantage of paste/selection and all the other goodies of text, but with fully-integrated styling.

Like you, I found that standard text input boxes were far more interesting than contentEditable because they're just so simple overall.

I think there's probably an interesting middle ground here where you render real markdown with the textarea effectively fully hidden (but still with focus), emulate the selection events of the rendered markup into the textarea, and basically get a beautiful editor with all the textarea solidness.

garbageoverflow · 4h ago
If it were a WYSIWYG editor, there'd be previews for images. But it seems like it's just syntax highlighting for textareas. Nice project either way, but false advertising.
calmworm · 1h ago
I didn’t see an option for images. Am I missing something?
macintux · 1h ago
I assume that was the point. The parent commenter feels "WYSIWYG" by definition includes images.
tomsmeding · 3h ago
In Firefox on Android, the bold font is wider than the upright and italic fonts, breaking alignment.

(It works fine in Chrome on the same Android phone. Android 16, Firefox 141.0.3)

SamInTheShell · 2h ago
This is a nifty little project. If I wasn't already neck deep in blocknote adoption in a small experiment I'm doing, I'd be taking this for a spin.

I noticed on the site the really cool animation you got has a 1px solid border on one of the overlays in firefox. Figure you might care since it's clearly supposed to be flashy.

pyromaker · 1h ago
I also got frustrated with text editors and decided to build something for myself too, so I don't have to repeat the process over and over.

https://www.texteditors.dev

jv22222 · 1h ago
Smart! I’ve been working with contenteditable for 3 years. You found a great shortcut!
mosselman · 5h ago
Very cool! So simple, I love it.

One thing that would be great is a bit better support for lists (todos, unordered and ordered) where when you press enter once it will add another `-` or `- [ ]`, etc item and when you press it a second time it becomes a blank line.

pedrovhb · 2h ago
Nice! Seems very useful if you can drop in and have everything work.

Nitpicking a bit: it's not as much _rendering_ markdown as it's _syntax highlighting_ it. Another interesting approach there could be to use the CSS Custom Highlight API [0]. Then it wouldn't need the preview div, and perhaps it'd even be possible to have non-mono fonts and varying size text for headers.

[0] https://developer.mozilla.org/en-US/docs/Web/API/CSS_Custom_...

jagged-chisel · 1h ago
The animated exploded demo definitely shows formatting differently from plain text (bold is bold, hyphens replaced with bullets.)
4b11b4 · 47m ago
Ya that's true
Tmpod · 2h ago
As it is, and without the toolbar, this really reminds me of how this[0] neovim plugin renders Markdown in the terminal. One of its nice features is doing syntax highlighting inside fenced code blocks (through tree-sitter I believe).

[0]: https://github.com/MeanderingProgrammer/render-markdown.nvim

wesz · 2h ago
I used exactly the same approach years ago working on code editor with js evaluation - http://labs.onether.com/javascript-sandbox/ (this is some old version only with whitespace characters, it also had syntax highlighting but i couldn't find it).

Anyway, nice work mate.

indigodaddy · 1h ago
This is pretty awesome. Now I’m just a dumbo sysadmin with limited webdev/JS skills, so is there a high level way to integrate this into a site so that it could create MD files that could be saved server side?
small_scombrus · 1h ago
Most JS/TS runtimes have filesystem modules, at it's simplest/least secure you could implement it with client-side fetch and:

On get request - find matching .MD file and return

On put request - write to given location

Jonovono · 4h ago
Nice, I was playing around with Milkdown. it's pretty cool: https://milkdown.dev/playground. It's like a block editor like notion for markdown so you don't need the split pane markdown/preview either
ingigauti · 5h ago
Great idea & solution

I noticed toolbar is missing from options doc, reason I went looking was if I could add my own custom button to the toolbar

ForceBru · 1h ago
I thought it should be extremely portable ("everything just works, it's native"), but it doesn't work on iOS 9.3.6. It doesn't even let me input text into the textarea...

A natural extension seems to be a source code editor with syntax highlighting, like those used in https://marimo.io/, Jupyter, https://plutojl.org/ and other notebook-like Web editors.

acherion · 1h ago
I'm not sure why you are testing in iOS 9.3.6. (which was released in 2015), when the documentation says support for Safari is for versions 16 and above.
drob518 · 2h ago
This is cool (and amazingly simple). Would be even cooler than it already is if it would syntax highlight code in code blocks, too.
aschelch · 8h ago
Looks awesome. Like the simplicity. I'll keep that in mind for future project ;)

(Btw, there might be a typo on the landing page on the set up part. There is 2 times de <div> instead of the textarea i guess;))

Edit: and the link to the Github is brocken

panphora · 8h ago
The idea is that two instances of overtype would be initialized inside those divs!
philo23 · 4h ago
The first time I saw this technique was while trying to figure out how GitHub styled the keyword:value tokens in their search box. It's a very cool technique, and you've done a very nice job of integrating it with a markdown parser!

Only down side to it is that you cant apply any padding to the styled inline elements.

neilv · 2h ago
Am I doing it wrong?

The animation shows variable-pitch fonts, but the demo seems to be all the same fixed-pitch font for me. (On Firefox ESR and Chromium.)

skyzouwdev · 2h ago
This is honestly brilliant. I love how you leaned into the constraints instead of trying to hide them, and the transparent textarea trick is such a clever hack. The fact that you got it down to 45KB while keeping undo/redo, mobile keyboard, and accessibility makes it feel like a breath of fresh air compared to bloated editors. Definitely bookmarking this for my next project.
walterlw · 2h ago
would absolutely love this for a personal note-taking project, but having image support and some sort of auto-completion for commands, lists, tags etc is crucial for something i'd use every day on desktop and mobile. Still love seeing more options for different purposes.
maz1b · 3h ago
Nice job. How is this different than marked on npm?
nm980 · 7h ago
Can you send the GitHub link again?

And how does this handle rendering larger documents?

cchance · 4h ago
is there a way to show the rendered preview (not with the markdown characters)
jerpint · 3h ago
This is great! Gonna try this on my next project
sdairs · 3h ago
This is really nice
octobereleven · 5h ago
Love this. Pretty much markdown on steroids!
nodesocket · 5h ago
Very cool. I’m gonna implement into my hobby project today and see how it goes.
breakfastduck · 5h ago
I really like the simplicity of this.

I have a couple projects I could see this being really useful in, at least as an option instead of pure plain text. I still feel like consumers don't like markdown though, it's frustrating.

One thing I noticed, when doing a list (bullet, numbered etc) it would be great if the list continued on barrage return (enter) - most general users would expect that I think.

knoopx · 3h ago
very nice!
Bengalilol · 5h ago
> That's it. No npm. No build. No config.

That's it, I am loving it.

sitkack · 3h ago
If it doesn't have an NPM build, it isn't a serious project. Not using anything w/o a build.
neilv · 2h ago
If it doesn't work with crack pipes, it's not a serious pharmaceutical.
vid · 2h ago
I agree with sitkack. npm (packaged software) is really handle to bundle code and keep a repo up to date. But I guess if you just want a markdown editor on a page, this is fine.
3836293648 · 1h ago
You are arguing two (subtly) different points. Not requiring npm or any build step is great. Always.

Having it available to simplify integration into larger projects is also great.

These two things are entirely orthogonal, even if this only does the first one.