Acrobat, Rebuilt in Rust? 15K Stars in 18 Days (I Tested It)
Read the Portuguese translation →
Author: Prompt Engineer 48 · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: Acrobat, Rebuilt in Rust? 15K Stars in 18 Days (I Tested It) · Channel: Prompt Engineer 48 · 02:37 · Watch on YouTube
Topics: Task and workflow automation, Software engineering with AI, Open source and software ecosystems
Summary
Section titled “Summary”The video tests a new Rust-based PDF editor that has quickly attracted about 15,600 stars, clarifying that it is a clean-room implementation based on a public standard and observed behavior, not reverse-engineered Adobe code. The project is still alpha, with some features incomplete and its current page rendering relying on Cairo. Testing found that it handles viewing, searching, organizing, and combining PDFs, including a 15,000-page document, quickly. However, editing, OCR, and office export remain limited or missing, so the reviewer does not consider it a full Acrobat replacement yet.
Key points
Section titled “Key points”- The repository was about 18 days old and had approximately 15,600 stars and 6,000 forks at the time of the video.
- The authors describe the project as a clean-room implementation informed by the public ISO 32,000 specification and external observation of Acrobat.
- The project is labeled alpha; its stated coverage is 57% of tracked Acrobat features and 94% of must-haves.
- The project says it is about 55% of the way toward replacing Acrobat for everyday work, and has not yet been compared side-by-side with it.
- Pages are currently drawn using the Cairo crate while the project’s own renderer is being built.
- The reviewer tested version 0.9.0 on Windows from an 82-megabyte portable zip, with no installer or account required.
- The app opened and searched a 660-page PDF, finding 1,160 matches for “Acrobat,” and displayed all pages in its organizing grid.
- On a 15,000-page, 97-megabyte PDF, the command-line tool read the document summary in under a second and rendered a middle page in half a second.
- Combining two PDFs took 0.08 seconds, while extracting one page of text took 2.4 seconds.
- Editing remains a major limitation: reliable editing of existing text, OCR, and office export are listed as thin or missing.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:01 | What the project is—and is not | The video corrects the claim that the project reverse-engineered Adobe, describing its clean-room approach and the limits of its alpha feature coverage. |
| 00:33 | Alpha status and rapid development | The reviewer notes the project’s incomplete feature set and Cairo-based rendering, then describes its contributors, releases, and portable Windows download. |
| 01:34 | Testing large PDFs | Tests on a 660-page file and a 15,000-page book show the app’s search, page organization, document-summary, rendering, text-extraction, and merging performance. |
| 02:06 | Where it falls short | Editing features remain incomplete, so the reviewer recommends keeping Acrobat for signing and editing real documents while recognizing the app’s strengths for other PDF tasks. |
Quotes
Section titled “Quotes”That is not what happened. — 00:01
The authors call it alpha and I respect that. — 00:33
It opens, the bookmarks are there, and I searched for Acrobat. — 01:34
I cannot tell you it replaces Acrobat. — 02:06
that is the real story. — 02:37
Concepts and entities
Section titled “Concepts and entities”Adobe Acrobat, Rust, clean room, ISO 32000, Cairo, RunPod, Apache, MIT
Full transcript (original language)
Section titled “Full transcript (original language)”00:01 18 days ago this repository did not exist. Today it has about 15,600 stars, 6,000 forks, and it says it rebuilds Adobe Acrobat in pure Rust. The internet says someone reverse-engineered Adobe. That is not what happened. I ran the thing on my own laptop to find out what is First, the correction. Reverse-engineering means taking Adobe’s software apart. The readme says clean room instead. The behavior comes from the public ISO 32,000 spec plus watching what Acrobat does from the outside. Never anyone else’s code. That matters
00:33 because it is the difference between a legal cousin and a copy. Second, the authors call it alpha and I respect that. By their own count, it covers 57% of tracked Acrobat features and 94% of the must-haves. For everyday work, they say it is about 55% of the way to replacing Acrobat and they admit the quality has not been compared with Acrobat side-by-side yet. One more honest detail. The readme says pages are still drawn by a borrowed
01:03 crate called Cairo while their own renderer is being built. So, the headline written from scratch is not the whole story. So, why is it moving so fast? 225 contributors, over 1,200 commits, and three releases in six days. This is a crowd, not one person in a basement. So, I downloaded version 0.9.0, the Windows portable zip, 82 megabytes. I checked its checksum against the release, unzipped it, and ran it. No installer, no account.
01:34 To stress it, I glued the readme and a Wikipedia page into one 660-page file. It opens, the bookmarks are there, and I searched for Acrobat. 1,160 matches across the whole file. Then, the page grid for organizing pages with all 660 pages ready to drag around. Then, the command-line tool on a 97-megabyte book with 15,000 pages that I had on disk, it reads the document summary in under a second and renders a page from the middle in half a second, including startup. Pulling the text of one page took 2.4 seconds, which is the
02:06 slowest thing I measured. Combining two PDFs took eight hundredths of a second. Where it falls short is editing. The edit panel itself says coming in milestone M7 and only the items marked ready work today. I did not test text editing end-to-end and the readme lists reliable editing of existing text, OCR, and office export as thin or missing. So, I cannot tell you it replaces Acrobat. My take for viewing, searching, merging, splitting, and organizing, it is already
02:37 fast, free, offline, and open source under Apache and MIT. For signing forms and editing real documents, I would keep Acrobat until they ship that side-by-side fidelity check. 18 days old alpha and already this usable, that is the real story. If you’re looking for cheap and reliable GPUs, I use RunPod and the link is in the description. The repo link is below. Would you trust an 18-day-old PDF editor with your real documents? Tell me in the comments.