The “boring file format” argument is quietly becoming the most important infrastructure decision in a creator’s stack
If you’ve ever watched a year of content strategy evaporate because a scheduling tool shut down, a notes app changed its export format, or a “lifetime deal” SaaS pivoted to enterprise pricing, you already understand why this launch matters more than its modest framing suggests. Fulvid, a new open-source Markdown and MDX desktop editor from solo maker Manuel Gil, is not a social media tool. It doesn’t schedule posts, generate captions, or touch an API. But the philosophy behind it — that your writing should live in plain files you own, not inside a proprietary database you rent — is the same argument I’ve been making to creators for three years about their content archives. And it’s the argument most social media operators keep losing.
Here’s the thesis: the creators who survive the next platform shakeup won’t be the ones with the best hooks. They’ll be the ones whose ideas exist as portable text on a hard drive, ready to be reformatted for whatever surface wins in 2026. Fulvid is a small, opinionated bet on that future. Whether it’s the right tool for you depends on something the Product Hunt thread mostly glosses over: how much of your workflow actually lives in Markdown today.
What Fulvid actually is, and what problem it’s solving
Strip away the launch-page language and Fulvid is a standalone desktop application for editing Markdown and MDX files, available on Linux, Windows, and macOS. The maker’s stated design principle, quoted directly from the launch thread, is that “Markdown and MDX documents should remain ordinary files that you can open, edit, move, back up, and use with other tools.” Fulvid adds folder navigation, search, links, preview, a Graph view, and a focused writing mode on top of that foundation.
That’s the whole pitch. It is deliberately unglamorous.
The problem it solves is real but narrow: if you write in Markdown — because you publish to a static site, because you keep a content wiki, because your newsletter tool accepts MDX, because you’re tired of rich-text editors mangling your formatting — you currently have two bad options. You can use a code editor like VS Code, which is powerful but hostile to prose. Or you can use a note-taking app like Obsidian or Notion, which wraps your files in a proprietary layer that ranges from “mildly annoying” to “actively hostile to portability.”
Fulvid sits in the gap. It’s a prose-first editor that treats your folder of .md files as the source of truth, no vault, no sync service, no account required. For a certain kind of creator — the one who already thinks in Markdown — that’s a meaningful quality-of-life improvement. For everyone else, it’s probably irrelevant, and I’ll get to why that matters later.
The Graph view question, and why it’s the right question
The most substantive exchange in the launch thread comes from Alexandra Protsenko, who asks how the Graph view holds up “once a folder has a few thousand files in it.” This is exactly the right question, because every Graph-based note tool I’ve used — Obsidian, Roam, Logseq — degrades into an unusable hairball somewhere between 500 and 2,000 notes. The visual becomes noise, and the feature quietly dies.
Gil’s answer is that the graph is “deterministic and bounded, so it will always show you the same local view for a note and won’t slow down the editor.” Protsenko’s follow-up calls this “the right call.” I agree, and I’d push further: bounded local graphs are the only Graph views that have ever been useful to me. A global graph of 3,000 notes tells you nothing. A local graph showing the five notes adjacent to the one you’re writing is a genuine thinking tool. If Fulvid has actually implemented this correctly, it’s a smarter design decision than the feature list makes it sound.
The VS Code question, and why it’s the wrong framing
The other notable thread comes from Alex Koo, who asks flatly: “is this just a VS Code extension?” Gil’s answer is that Fulvid is “based on some of the VS Code extensions I’ve built and on the Monaco Editor used by VS Code, but it’s not an extension” — it’s a standalone application that “doesn’t rely on extensions to navigate through notes.”
This is a fair defense, but it also reveals the product’s biggest strategic vulnerability. Monaco is the editor component that powers VS Code. If you’re already a VS Code user with a Markdown extension pack installed, the marginal value of switching to a standalone app built on the same engine is genuinely unclear. The counter-argument — that VS Code’s extension ecosystem is a liability for prose writers, not an asset — is defensible, but Fulvid’s launch page doesn’t make it explicitly. That’s a positioning gap, not a product flaw, and it’s the kind of thing that determines whether a tool like this finds 500 users or 50,000.
How this compares to the incumbents you’re probably already using
Let me be concrete about the competitive landscape, because “open-source Markdown editor” describes about forty tools.
Obsidian is the obvious comparison. It’s the dominant player in the “local Markdown files with a nice UI” category, it has a massive plugin ecosystem, and it’s free for personal use. Its weaknesses are well-documented: the mobile app is mediocre, sync requires a paid subscription or a DIY solution, and the plugin ecosystem creates the same kind of lock-in the app claims to avoid. If you’re already deep in Obsidian, Fulvid is not going to pull you out. If you’ve bounced off Obsidian’s complexity, Fulvid’s narrower feature set might actually be a feature.
Notion is the opposite pole. It’s a database with a text editor bolted on, it’s cloud-only, and its export function produces Markdown that ranges from “usable” to “deeply mangled” depending on how many nested blocks you’ve used. I’ve migrated two content archives out of Notion, and both times I lost formatting I cared about. Notion is fantastic for team wikis and terrible for anyone who believes their words should outlive the tool.
iA Writer is the closest philosophical cousin — a beautiful, focused Markdown editor with strong file-based workflows. It’s paid, it’s polished, and it’s been around long enough to have a real track record. If you want a commercial product with support and a roadmap, iA Writer is the safer bet. Fulvid’s advantage is that it’s open source and free, which matters enormously if you’re on Linux or if you’ve been burned by abandoned indie apps before.
Ulysses is the Mac-only premium option, and Typora is the minimalist cross-platform one. Both are worth knowing about. Neither has a Graph view, which is Fulvid’s most distinctive feature.
My take: Fulvid’s realistic niche is Linux users, MDX writers (a small but growing group, since MDX is the format of choice for modern documentation sites and many static site generators), and creators who want a Graph view without Obsidian’s plugin sprawl. That’s a real audience. It’s not a mass market.
Why TikTok creators should care more than LinkedIn ones
Here’s the counterintuitive part. You’d assume a Markdown editor matters most to LinkedIn creators, who write long-form text posts and newsletters. Wrong. LinkedIn’s editor is a rich-text box, and most LinkedIn creators write directly in it.
The creators who should care about portable text files are the ones running multi-platform repurposing pipelines — and that’s disproportionately short-form video people. If you’re a TikTok creator who also posts to Reels, Shorts, and Pinterest, your scripts, hooks, and captions are the reusable asset. The video is disposable; the script is durable. Every hook you’ve ever written, every caption that outperformed, every comment-bait question that drove engagement — those should live in plain text files you can grep, tag, and remix. Not in a TikTok drafts folder that might disappear. Not in a Notes app that syncs to one ecosystem.
I’ve watched creators rebuild their hook libraries from scratch three times because they stored them in the wrong place. A folder of Markdown files with a decent editor on top is the cheapest insurance policy in this business.
What creators and social media teams can actually borrow from Fulvid’s design philosophy
Even if you never install Fulvid, there are three operational lessons in its launch that apply directly to how you run content.
First: separate your source of truth from your distribution layer. Fulvid’s core claim is that the file is the asset and the editor is just a view. Most creators do the opposite — they treat the platform as the source of truth and the file as an afterthought. This is backwards. Your distribution layer (Instagram, TikTok, YouTube, X, LinkedIn, Threads, Facebook, Pinterest) is volatile by design. Algorithms shift, APIs change, accounts get locked. Your source of truth should be a folder you control. For most creators, that means a simple directory structure: /hooks, /scripts, /captions, /ideas, all in plain text, synced via Dropbox or a Git repo. It takes an afternoon to set up and it will save you a week of work the next time a platform surprises you.
Second: bounded context beats global context. Gil’s decision to make the Graph view local and deterministic rather than global is a design principle you can steal for your content planning. A spreadsheet with 800 content ideas is useless. A short list of the five ideas most related to what you’re working on right now is actionable. If you use a tool like Notion or Airtable for content planning, consider building views that show you a bounded slice — “ideas tagged for this week’s theme” — rather than the full database. The full database is for quarterly reviews. The bounded view is for Tuesday morning.
Third: the tool should get out of the way. Fulvid’s “focused writing mode” is a small feature, but it’s the one I’d actually use. Every scheduling tool I’ve tested — Buffer, Hootsuite, Later, Metricool — has a composer that’s cluttered with preview panes, hashtag suggestions, and character counters. Those features are useful for the final 10% of the process. They’re actively harmful for the first 90%, which is just getting the words out. My own workflow, refined over years of running accounts: write in a distraction-free editor, then paste into the scheduler. Never compose inside the scheduling tool. The tool’s job is distribution, not creation, and conflating the two produces worse content.
Where the math breaks
I want to be honest about a structural problem with the “own your files” argument, because I’ve made it myself and I know where it fails.
The overwhelming majority of creators do not write in Markdown, will never write in Markdown, and have no reason to. The format’s advantages — portability, version control, plain-text longevity — only matter if you’re already comfortable with a terminal, a text editor, and the idea that your files are yours to manage. That’s a small slice of the creator economy. The rest are writing in Notes, in Google Docs, in the platform’s native composer, and they’re fine.
So the honest framing is this: Fulvid is not a tool for most creators. It’s a tool for a specific subset — technical creators, developer-adjacent creators, documentation writers, and the small but real group of social media operators who’ve already built their workflow around plain text. For that group, it might be genuinely useful. For everyone else, the lesson is the philosophy, not the product.
Where my judgment says Fulvid falls short
I haven’t done a hands-on test of Fulvid, so everything in this section is inference from the launch thread and the category, not measured experience. Flagging that clearly.
The positioning is weak. “Open-source Markdown editor with a Graph view” doesn’t tell me who it’s for. The launch thread’s most revealing moment is Alex Koo’s VS Code question — it suggests that even engaged Product Hunt users couldn’t immediately tell what makes Fulvid different from tools they already have. That’s a marketing problem the maker can fix, but it’s a real one.
The MDX support is undersold. MDX — Markdown with embedded JSX — is genuinely underserved by existing editors. If you write for a Next.js site, a Docusaurus docs project, or any modern static site generator, your options are basically VS Code or a web-based editor. A desktop MDX editor with a proper preview is a real gap in the market. Fulvid mentions MDX in passing, but it should be leading with it. That’s the feature that would make me install it.
“Deterministic and bounded” is a claim, not a benchmark. Gil’s answer to the performance question is technically reassuring but empirically unverified. I’d want to see how it handles a folder of 5,000 files on a mid-range laptop before I trusted it as my daily driver. Not a criticism — just an open question the launch thread doesn’t resolve.
Open source is not a business model. The maker says Fulvid is open source and free. That’s great for users and genuinely risky for the project’s longevity. I’ve watched dozens of promising open-source creator tools stall when the maintainer’s day job got busy. If Fulvid becomes part of your workflow, back up your files (which, to be fair, is the whole point) and don’t assume the app will be maintained forever. That’s not a knock on Gil — it’s the reality of solo-maintained software.
The mobile gap is unaddressed. Not disclosed in the launch thread, but no mobile app is mentioned. For creators who capture ideas on their phone — which is most of them — that’s a meaningful limitation. You’d need a companion app like Obsidian’s mobile client or a plain-text editor that syncs to the same folder.
What I’d watch, and what I’d test this week
Three concrete things, in order of priority.
Audit your content source of truth. Open your phone and laptop right now and find where your last ten content ideas live. If they’re scattered across Notes, DMs to yourself, a Notion page, and a drafts folder, you have a portability problem. Spend an hour this week consolidating them into a single folder of plain text files. You don’t need Fulvid for this — any text editor works. The point is to stop renting your ideas.
If you write MDX, download Fulvid and stress-test it. It’s free and open source, so the cost of trying is an hour. Load a real project folder with a few hundred files, test the preview against your actual build pipeline, and see whether the Graph view earns its place. If it does, you’ve found a tool. If it doesn’t, you’ve lost an afternoon.
If you don’t write Markdown, steal the philosophy, not the product. The lesson from Fulvid’s launch isn’t “use this editor.” It’s that the creators who treat their words as portable assets — files they own, formats that outlive platforms, workflows that don’t depend on any single SaaS staying alive — are the ones who survive the next algorithm shift with their archives intact. That’s worth more than any Graph view.
