Summary Digital Access & Information Freedom Acknowledges
This Windows Insider Blog post announces software updates to Notepad and Paint, operating as a public technical information channel accessible to all users without barriers. The content supports information freedom (Article 19) and digital access (Article 27) through open distribution across multiple platforms, but structural surveillance infrastructure (Google Tag Manager tracking and third-party advertising cookies) significantly undermines privacy protections (Article 12), creating a tension between information accessibility and privacy rights.
They’re turning Notepad into what Wordpad was (or was supposed to be). Now everyone looking for the light weightiest *.txt editor must find a new tool...
Markdown support isn't a bad idea, actually, as long as they don't break the most important (IMO) property of Notepad: binary WYSIWYG. I.e. if I type in some plain text and then open the file with anything else (including after moving to another machine/platform, or even viewing raw data stream in transit or on drive), I can trust to see that text, as is, and nothing else. In particular, if I restrict myself to lower 127 bytes, I expect byte-to-byte correspondence.
So the markup dialect that's widely used but suffers from a near-total lack of viewers will now finally be rendered as intended, at least on Windows?
Markdown presents a chicken-&-egg scenario that has dragged on for decades: tons of Markdown documents, but almost nothing with which to simply view (not edit) them as intended. Mystifying.
I still say this is stupid AF, and that notepad should stay as simple as reasonable as a plain text editor and they should have resurrected "WordPad" for this purpose if they wanted it in Windows. I'm mixed on the enhancements to Paint... but this just feels a bit off.
Maybe I'd mind it less if they put the new MS Edit in Windows by default, so again, there's a minimal plain text editor in the box.
The new workflow will be "AI, I need to view this text file and add some words to it. Create an app that displays it in a scrollable window, respecting the encoding. Now move the cursor to the line below the three dashes... no, the other three dashes..."
Once upon a time, you could strip formatting from the clipboard in notepad with ^V ^A ^C, for example if you were trying to paste from edge into word. There's still a market for a non-rich text editor, without autosave, cloud, account login or AI.
I built a tiny Notepad clone in ~5 minutes using an LLM: open/save, plain text, no surprises.
Lately I've been doing the same for other small utilities. Roughly half the little tools I use are ones I generated and kept because they’re predictable and easy to audit.
The point isn't replacing built-ins; it's reducing dependence on shifting defaults. I want to care less about what the software/os vendor changes this time.
Years ago replacing Notepad with an alternative was a given and everybody had their favourite. Before UTF everywhere you needed at least proper character encoding handling, other features followed.
Surprisingly, some of the projects such as AkelPad are still alive.
Win32 made things easier, as well as things like Delphi and Scintilla later.
Just checked my archives, and my own naive but functioning attempt measures whole whopping 36520 bytes, though not without the help of an executable packer, which was a fashion then.
Mostly works fine under Wine, though it is about the legal US drinking age.
If notepad were to support Markdown by giving it a nice syntax highlighting and niceties like clickable links and automatic list numbering, while preserving the monospaced font, then that would be great. But with rich text formatting it has all the pitfalls of WYSIWYG editors like accidentally changing the style of something, having "formatting typos" where you tried highlighting only part of a word before making it bold, using the wrong header type, etc.
notepad is supposed to be like the 'nano' for windows. it's already bloated.
But this is just following a pattern, the enshittified even calc.exe and mspaint. Previewing pictures in windows is shamefully slow because the previewer is also a bloat.
My diagnosis is that Microsoft doesn't have good technical leadership. It has spread the risk of bad decisions by individual leaders by spreading it amongst too many decision makers, and those people aren't always technically apt, or they have aptitude within their specific domain of expertise. Why is the start menu in react native for example.
they also have a crippling illness in the form of sunken-cost fallacy. Even when no one is especially depending on it, they go all-or-nothing on tech stacks and design patterns. Marketing and branding ultimately, I think is their biggest problem. You know how they name everything terribly? that's trying to capitalize on existing branding. This is fundamentally the mindset of salespeople. they could be spinning a new app, or making a vscode-lite ship with windows, but brand familiarity is why they're messing with notepad.
It is truly dumbfounding, they're being run like HP and IBM but because of how much the world relies on them, and because of Azure they're making so much profit.
Why are the shareholders no enraged even more? To have such a vast marketshare and failing to capitalize on it is terrible. They could be doing better than Apple. Even apple sees the writing on the wall and adapts their strategy fundamentally by starting to make their own silicon. It's like having a barn full of chicken that lay golden eggs, but the farmer is slaughtering them for their meat, and the farmer's employer doesn't care because chicken meat is still making good enough profits.
Weird, it already does at my work computer since a month which aren't exactly first to get the latest updates and definitely don't get prerelease software. I wonder how all that works.
(Update: Ah, title is a little misleading. This update doesn't introduce Markdown, it adds support for nested Markdown lists etc.)
Personally, I think they should've kept Notepad as-is and reincarnated WordPad instead, rewriting it and giving it Markdown instead of RTF. It already had the basic formatting interface and all. It would've been a pretty smooth transition.
The problem is that Markdown supports quite a bit, even tables, which lends to feature creep. It was already more sluggish without any of this due to moving Notepad to WinUI.
It's not like I am thrilled, but it has at least some value over the last what, 5-10 years of windows changes. I can see me mistaking markup. I can't see me mistaking copilot.
At this point I really think GitHub should formally publish their flavor as well as a default implementation. It's likely the single most widely used variant online at this point.
I know there are others and there are fine points. I would like to see a couple minor additions to support image placement (that aligns with Medium's editor) and finally a strike-through text notation. But that's about it.
FWIW, Notepad has had support for BoM detection and wide-characters (UTF-16/UCS-16) for some while. That said, IMO, most simple editors at this point should default to UTF-8 encoding and only LF for line endings.
I was an engineer on the Visual Studio team. Internally, the Notepad project existed to provide a minimal, shippable product that we could use as a testbed. We used it to validate everything from compiler changes to kernel32 loader behavior on beta versions of Windows. If Notepad didn’t run, your feature didn’t work.
I used to write documentation in Markdown manually. About a year ago I started using a VSCode extension to tell me if there are minor errors in the documents, but nothing else.
This is my favorite part of this story. Do you want remote code execution? Because [fixing things that aren't broken] is how you get remote code execution.
Notepad was historically just a thin wrapper for the "EDIT" window class, along with file loading and saving.
And WordPad was built on top of the "RICHEDIT" window class, and exposed lots of the OLE features provided by the rich text control. "Insert Object" is a powerful and potentially dangerous feature with a lineage going back to the Windows 3.1 days. As long as your DLL is registered correctly, any document in an OLE-capable program can cause objects from that DLL to become instantiated and deserialized.
Getting rid of documents able to instantiate arbitrary OLE controls is a good reason to try to remove WordPad. It's not just some simple styled text editor.
It was already true that an attacker could trick a user into copying a malicious link inside a file opened in Notepad to their browser, was that also a Remote Code Execution Vulnerability?
Unless it changed recently, the faster way is to just press ctrl+shift+V for "paste special" in Word, which should open up the paste dialog with "Unformated Text" preselected (IIRC), so immediately pressing Enter should close the dialog and paste the stripped text.
I remember first finding out about Edlin in 2003 while reading DOS for Dummies by Dan Gookin. Experienced a lot of anemoia that day. That short section about Edlin was the most touching part of the entire book (probably because it took place before the DOS 5-6 / Win 3.x era which already felt old).
Yeah IDK. Wordpad is built around rich text, with all the weirdness and complexity that comes with it. I know for a fact that .rtf is absurdly complicated to work with, and I assume that .docx is similar.
I’m willing to bet that adding markdown to Notepad was a lot simpler than trying to make it work in Wordpad, especially since you’d probably still have to support rich text.
Content exemplifies freedom of information by publicly sharing technical product information with community; blog format enables information reception and dissemination.
FW Ratio: 63%
Observable Facts
Page provides detailed technical information about Notepad and Paint updates publicly.
Social sharing buttons present for Twitter, Facebook, LinkedIn, and Threads.
RSS feed integration available (icon-rss class).
No registration or paywall visible.
Content available through multiple distribution channels.
Inferences
Public technical blog format supports both receiving and imparting information to broad audience.
Multiple sharing mechanisms enable users to freely disseminate information to others.
Open access policy facilitates informed participation in software development discussion.
Page implements third-party privacy opt-out iframe and Google Tag Manager tracking. Observable privacy controls present but tracking infrastructure is extensive.
Terms of Service
—
No Terms of Service content visible on page.
Identity & Mission
Mission
+0.05
Article 27
Microsoft corporate blog focused on product updates. Mission of information sharing to technical community implicit but not explicitly stated on page.
Editorial Code
—
No editorial code or ethics policy visible on page.
Ownership
0.00
Ownership clear (Microsoft). No modifier applied as this is neutral identification.
Access & Distribution
Access Model
+0.10
Article 19 Article 27
Public access to blog content. No paywall or registration visible. Supports universal access to information.
Ad/Tracking
-0.15
Article 12
Google Tag Manager (GTM-MLSXDLQ) integrated for advertising and behavior tracking. Third-party cookie infrastructure observable.
Accessibility
+0.10
Article 2 Article 26
Page includes semantic HTML (iframe ariaLabel), CSS layout systems for responsive design. No explicit accessibility statement visible.
Public blog platform accessible without authentication; content shareable via social media links (Twitter, Facebook, LinkedIn, RSS); no paywalls or content restrictions.
Third-party tracking via Google Tag Manager (GTM-MLSXDLQ) and privacy opt-out iframe observable in page code; extensive cookie infrastructure for advertising behavior tracking.
build 1ad9551+j7zs · deployed 2026-03-02 09:09 UTC · evaluated 2026-03-02 13:57:54 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.