To Replace Adobe Acrobat, I Built My Own Open-Source PDF Reader Folio

It Started With a Bad PDF Experience

After setting up a new computer, the first thing you often do is open a PDF file. The built-in Windows reader isn't great, so many people—like this developer—turn to Adobe Acrobat, since it's the industry standard. But according to an experience shared on a YouTube channel, downloading and installing Acrobat was disappointing: the software is bloated, packed with features you don't need right now. Rather than put up with such a tool, he decided to write his own.

That decision gave rise to a project called Folio: a lightweight, fast, completely free and open-source PDF reading and editing tool. The developer emphasizes that he can add any feature he wants himself, without paying for software anymore.

What Folio Is: A "Good Enough" PDF Tool

Folio's positioning is clear—do what a PDF reader should do, and stay lean. The developer describes it as "lightweight" and "lightning fast," contrasting it with Acrobat's bloat.

From the description, Folio offers both reading and editing capabilities, but its core selling point isn't being feature-complete—it's extensibility: add whatever feature you need yourself. This "customize on demand" approach hits exactly the pain point of users troubled by the redundant features of commercial software.

PDF (Portable Document Format) was introduced by Adobe in 1993 and became the ISO 32000 international standard in 2008. Its core goal is to keep document layout consistent across different devices and operating systems. A PDF is essentially a format that describes page-drawing instructions, internally containing text, fonts, vector graphics, and image objects, so a reader needs to parse these objects and render them into a picture. The open-source ecosystem already has several mature PDF rendering and processing libraries, such as MuPDF, Poppler (the basis for tools like pdftoppm/pdftotext), and PDFium (the PDF engine built into Chromium). Developers who want to build a lightweight reader themselves typically implement rendering and text extraction on top of such libraries, then build their own interface layer. This also explains why an individual developer can produce a usable PDF tool in a relatively short time: the underlying parsing work can reuse mature open-source components, and the room for innovation is concentrated in interaction and feature trimming.

Why Acrobat Frustrates People

The developer's complaints about Acrobat center on two points: first, it's huge and feature-heavy after installation; second, many of those features are completely unnecessary the moment you open a file.

This dissatisfaction isn't unique. Commercial PDF software often keeps piling on features to cover enterprise scenarios, while ordinary users pay for these unused parts in startup speed, disk space, and attention. The developer's choice was to "stop putting up with it"—take matters into his own hands and trim the tool down to exactly what's needed.

The feature bloat of commercial PDF software is closely tied to its business model. Adobe Acrobat comes in a free reader and a paid Pro version, the latter integrating enterprise-oriented capabilities such as form design, OCR recognition, document signing, and cloud collaboration. To drive users toward subscription upgrades, vendors often embed numerous entry points and promotional prompts in the interface and put some basic features behind a paywall. In addition, Acrobat bundles Adobe Creative Cloud components, background update services, and browser plug-ins during installation, all of which consume disk space and startup resources. For ordinary users who just need to "open, read, and occasionally annotate," this design meant to cover all scenarios translates directly into slower startup, higher memory usage, and interface distraction. Understanding this business logic makes it clear why lightweight open-source tools are gaining more traction among individual users.

The Thinking Behind Building Your Own Tool

Folio's emergence reflects an increasingly common developer attitude: when existing software doesn't match your needs, rather than compromise, build your own. Open source makes this choice even more appealing—the code is public, features can be modified, and there are no subscription fees.

For ordinary users, whether Folio is worth trying depends on how much they value "lightweight" and "customizable." If you just need to reliably read and occasionally edit PDFs, and don't want to be bothered by pop-ups and feature lists from commercial software, this kind of open-source alternative offers a new path. The developer's words are direct: he won't be paying for this software anymore.

The advantage of open-source software in such replacement scenarios lies not only in being free, but also in the rights to modify and distribute granted by the license. Common permissive licenses such as MIT and Apache 2.0 allow users to freely modify and redistribute the code, while GPL-type licenses require derivative works to be open source as well. For a personal project like Folio, open source means other users can submit issue reports, contribute feature patches, or even fork a version that suits their own needs. At the same time, open-source projects face sustainability challenges: maintenance depends on the developer's personal effort, and feature completeness and long-term updates don't come with the same guarantees as commercial software. So when choosing, users usually need to weigh "lightweight and customizable" against "stability and support."

Conclusion

Folio is a PDF reader and editor created by an individual developer out of dissatisfaction with Adobe Acrobat. It focuses on being lightweight, fast, free, and open source, and allows features to be added on demand. It may not replace all of Acrobat's professional capabilities, but for users who value a simple experience, it represents a choice worth watching.