Repo2pdf
Convert any public GitHub repo into a formatted PDF with the free npx repo2pdf CLI — line numbers, syntax highlighting, ignore rules.
Skip any guide that points you at the hosted converter — repo2pdf.site is expired and parked on GoDaddy. The free `npx repo2pdf` CLI is the real product now: genuine control over line numbers, highlighting, comment stripping and an ignore file. If your terminal is fine with Node 18 and git, it does the job; if you need a URL box or a maintained vendor, it doesn't.
Verified 1d ago · liveness 54/100 · cite: rightaichoice.com/tools/repo2pdf
- Developers comfortable running an npx command in a terminal
- Educators distributing a codebase snapshot to a class
- Students submitting a project as a single document
- Compliance or legal reviewers who need code in a portable format
- Anyone who needs the hosted web app — repo2pdf.site has expired and is parked
- Teams wanting inline comments and diffs on code
- Anyone needing private repositories converted
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Repo2pdf if you need a live, commentable code review or any sort of two-way editing — a PDF snapshot is a one-way artifact, and the hosted web app is winding down anyway.
Large or image-heavy repositories are where the output disappoints: binaries and assets don't convert, so you can finish a job believing you have the whole repo when you have only its text files.
The open-source CLI, installed from npm and run with npx repo2pdf, is the cost-free path and covers the same conversion work for anyone willing to run a command. That leaves little reason to pay for a hosted wrapper unless you specifically need URL-in, PDF-out with no local install — and the hosted app's own site says the service is winding down. Compare against a Pandoc script, which costs nothing either.
In short
Repo2pdf — Convert any public GitHub repo into a formatted PDF with the free npx repo2pdf CLI — line numbers, syntax highlighting, ignore rules. Best for Developers comfortable running an npx command in a terminal, Educators distributing a codebase snapshot to a class, Students submitting a project as a single document. Free to use.
What people actually say about Repo2pdf — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
8 mentions across 1 source (GitHub) · researched Jul 6, 2026.
Average across the 1 source that answered — each source counts once, not each post.
- +One-click conversion from GitHub URL saves manual work.
- +Free tier available for small repos with no signup needed.
- +Syntax highlighting and table of contents included.
- +Supports multiple plain-text file types (.py, .js, .md).
- +Preserves directory structure in the PDF output.
- −Fails on large repos with buffer size errors.
- −No cancellation option in Stripe for subscriptions.
- −Unexpected output formatting reported for standard repos.
- −Error when cloning or fetching repository files.
- −Null pointer error breaks PDF generation.
- • Cancelling subscription may require manual contact; no self-service cancel
Viability Score
How well maintained and how widely used is Repo2pdf? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Convert a public GitHub repo to a formatted PDF
- Open-source CLI run with npx repo2pdf
- Convert a local repository by path instead of a URL
- Add line numbers to code in the PDF
- Add page numbers to the PDF
- Enable syntax highlighting in the output
- Strip comments from the code before compiling
- Strip empty lines from the code before compiling
- Emit one combined PDF or one PDF per file
- repo2pdf.ignore file to control included files and directories
- Automatically skip non-text files such as .png and .git internals
- Preserve file structure in the generated PDF
- Requires Node 18 or later
- git required for cloned remote repos
- Choose to keep or delete the cloned repository after generation
About Repo2pdf
Repo2pdf turns a public GitHub repository into one formatted PDF document. It clones the latest version, walks the file tree, silently drops anything it can't render (images, .git internals, other binaries), and compiles the text files with syntax highlighting intact. The output is a portable, read-only snapshot of a codebase — the kind of thing you hand to a grader, a reviewer, a client or an archive. There are two ways it was distributed. The command-line interface is the survivor: published on npm as repo2pdf, invoked with `npx repo2pdf`, accepting either a repo URL or a local path. It then prompts you through the conversion options — line numbers, page numbers, syntax highlighting, stripping comments, stripping empty lines, and whether to emit one combined file or one PDF per file. It needs Node 18 or newer, plus git if it's cloning a remote repo, and it respects a repo2pdf.ignore file at the repository root so you control what gets pulled in. A repo2pdf.ignore file at the repository root controls precisely which files and directories get included, and it will skip .png files and .git internals automatically rather than trying to embed them. You can also choose whether to keep or delete the cloned repository once generation finishes. The second path — the hosted web app at repo2pdf.site, which offered the same conversion through a URL-paste interface with a download button — is gone. The domain has expired and is parked with GoDaddy, and before that it was already showing a wind-down notice. Treat the web product as retired and the CLI as the only working route; against alternatives like ad-hoc Word exports or screenshot dumps, the CLI's determinism and ignore-file control are what it still has going for it.
Behind the Verdict
We'd reach for repo2pdf when a codebase needs to become a document and nobody wants to assemble one by hand. Graders collecting student submissions, reviewers who need an offline copy, an archive of a public repo you expect to disappear — the CLI handles all of that in one command. The ignore file is the part that earns its keep. Real repos are full of lockfiles and vendored assets; being able to fence those off before the PDF balloons is the difference between a readable 60-page document and an unusable 900-page one. The option set is more thoughtful than most snapshot tools bother with. Stripping comments and blank lines before compilation makes review copies dramatically denser, and one-PDF-per-file mode suits anyone who wants to grep or annotate individual sources rather than scroll a monolith. Syntax highlighting and line numbers mean the output is actually referenceable. Where it bites: the web route is closed. The domain is expired and parked with GoDaddy, and even before the shutdown the site was telling visitors repo2pdf was winding down. Any tutorial or bookmark pointing at the hosted converter is dead weight, so budget for the terminal or look elsewhere. The other constraint is fit. There's no collaboration layer, no diffing, no inline commenting, and nothing here targets private repositories. If your review workflow lives in GitHub pull requests or a code-review platform, converting to PDF fragments it rather than helping. Projects that are mostly diagrams, screenshots or binary assets also come out wrong — it skips what it can't render, by design. Closest alternative is doing it yourself: pandoc plus a directory walk, or printing files out of an editor one by one. Those give you total control and no dependency on an npm package, at the cost of an
Researching Repo2pdf? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Repo2pdf actually fits — and what changes day-one when you adopt it.
You run npx repo2pdf, point it at your personal project, add line numbers and syntax highlighting, and strip comments and blank lines so the PDF reads cleanly.
Outcome: One tidy PDF of the whole project you can attach to the application, with the cloned repo deleted afterward to keep the machine clean.
You add a repo2pdf.ignore file at the root of the course repo to drop test fixtures and build output, then convert the remainder to a single PDF with highlighting.
Outcome: Students get one printable, offline-readable document that matches the repo's structure without the noise.
You convert a public repository for a third-party audit and hand over the resulting PDF rather than granting repository access.
Outcome: A fixed, portable artifact for the file — with the caveat that images and binary assets won't be in it.
Use Cases
- Package a repository as a single PDF for a job-interview code sample
- Hand a non-technical stakeholder a readable copy of a codebase
- Generate a fixed snapshot of a tutorial repo to distribute to a class
- Produce an offline-readable document of a repo for travel or low-connectivity work
- Build a text-only packet of a public repo for an internal audit or legal review
- Archive a project's source and documentation as one file for citation
Limitations
- Only public GitHub repositories are converted; private repos are not supported.
- Images and binary files are excluded from the output by default, so repositories whose value lives in diagrams or assets come out incomplete.
- On the CLI, build files and directories are not all ignored automatically, so you may need to extend repo2pdf.ignore by hand.
- The CLI requires Node 18 or newer, and git when cloning a remote repo.
- Output is a read-only snapshot: there is no diffing, commenting, or version tracking inside the PDF.
- The hosted web app is currently being wound down and is no longer accepting new subscriptions, so the CLI is the part of the product to plan around.
as of 2026-09-29
Verification history
We have re-verified Repo2pdf 8 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
Showing the 6 most recent of 8 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Repo2pdf's pricing actually pencils out — and where peers do it cheaper.
The open-source CLI, installed from npm and run with npx repo2pdf, is the cost-free path and covers the same conversion work for anyone willing to run a command. That leaves little reason to pay for a hosted wrapper unless you specifically need URL-in, PDF-out with no local install — and the hosted app's own site says the service is winding down. Compare against a Pandoc script, which costs nothing either.
Setup time & first value
How long it actually takes to get something useful out of Repo2pdf — broken out by persona, not the marketing-page minute.
With Node 18+ already installed, the CLI reaches first output in a few minutes: run npx repo2pdf, answer the prompts for repo URL, options, and output name, and wait for the clone and render. Add time if you need to write a repo2pdf.ignore for a large or messy repo. Using the hosted web app is faster still — paste a URL and download — but the site says it is winding down, so don't count on it.
Switching to or from Repo2pdf
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual copy-paste: point npx repo2pdf at the repo or at a local path and let it walk the tree, instead of assembling files by hand.
- →From a one-off print-to-PDF of a code viewer: convert the repo directly so directory structure and file names are preserved in the output.
- ↗To a Pandoc script: replicate the conversion yourself with a file-walk plus a PDF engine, trading the built-in prompts for full control over formatting.
- ↗To a code-review platform: move to a tool with inline comments and diffs if you need collaboration rather than a static snapshot.
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Repo2pdf”, and we withheld 6: 6 could not be judged, because “Repo2pdf” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Repo2pdf.
Official links
Tools that pair well with Repo2pdf
Common stack mates teams adopt alongside Repo2pdf, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Repo2pdf vs Cognition Ai
Cognition AI and Repo2pdf serve completely different needs. Cognition AI is an autonomous software engineer for enterprise teams, capable of planning, coding, and shipping production code, backed by a $10M productivity guarantee. Repo2pdf is a simple utility to convert GitHub repos to PDF for offline reading or submission. Choose Cognition AI if you need AI-driven development and bug triage at scale; choose Repo2pdf if you only need to archive or share code as a PDF.
Repo2pdf vs Poolside Ai
Poolside AI and Repo2pdf serve completely different needs. Poolside is an enterprise AI platform for building and deploying agents in regulated industries, requiring a sales engagement and custom deployment. Repo2pdf is a simple, free utility for converting public GitHub repos to PDF. Unless you need an enterprise-grade AI agent, choose Repo2pdf for quick PDF generation. If you need AI-assisted software engineering with governance and security, Poolside is the way to go.
Repo2pdf vs Bito
Choose Bito if your team uses AI coding agents and needs system-wide context across multiple repositories to improve code generation, reviews, and onboarding. Choose Repo2pdf if your primary need is converting public GitHub repos to PDF for archival, offline reading, or code submission — it's simple, fast, and free for small repos.
Alternatives to Repo2pdf
View all
Popular in PDF & Document Tools
Frequently Asked Questions
Categories
Used Repo2pdf? Help shape our editorial sentiment research.