This is a key use case for me. Supporting Markdown is important because it enables cross-device synchronization. It allows important information to be edited directly on a mobile device or via the web without creating an additional Proton Doc file. In addition to working across devices, it is also cross-platform: these Markdown files can be opened smoothly on both macOS and Windows. Furthermore, the Markdown files can be regularly backed up to a portable hard drive, reducing concerns about format compatibility when accessing them in the future.

If this matters to you, feel free to upvote this :)

Came here because I wanted something similar, but now I'm no so sure. It seems like what you want more than "markdown support" is offline mode where md files sync between Drive and local with Drive appropriately rendering md in the cloud. Is that right?

I'm a Linux user and don't have a Proton Drive desktop app yet, so I'm not sure I understand what you mean when you describe your workflow and "local representations." It seems to me a Proton Doc is a specific format more than text renderer. Just guessing because I can download a Proton Doc in a docx, html, txt, md, or pdf as of mid-Jan 2026, but cannot tell Proton Drive which format of file I want to create when I create a new file in the cloud.

I'm uncertain if Proton would consider this "markdown support" already. I'm not sure I do because if I understand your idea it sounds really cool.

I agree. This would be very useful, but as someone else said, just plain text support would be a good start.

just edit plain text md file would be great. Preview or style can arrive later

I like the existing support for markdown in proton docs (import, export, auto-detecting syntax)

But, it would also be handy to be able to edit a *.md file in-place, or any other plain-text file.

Would be a nice to have! Currently still using Dropbox for my Obsidian Notebook as I can edit the markdown files in that app.