Questions people actually ask.

No. PDFy uses the browser's File System Access API to read your folder, runs every step locally, and hands the result to your browser's print dialog. There is no upload step at any point.

Related Privacy page

Yes, free forever. PDFy is open-source under GPL v3 and there is no account to create, no email required, and no paywalled features. The source is on GitHub if you want to inspect it or fork it.

Yes. PDFy is a popular way to turn a coding assignment into a single PDF that professors and graders can read. The output has syntax highlighting, optional line numbers, a cover page with your name and project title, and a table of contents. Everything stays on your machine while you build it, and the final PDF is plain searchable text, so an instructor can copy snippets out of it for feedback.

Related Open a folderCover pageLine numbers and overrides

PDFy uses Shiki, which supports over 200 languages. The common ones include JavaScript, TypeScript, Python, Java, C, C++, C#, Go, Rust, Ruby, PHP, Swift, Kotlin, Scala, Dart, R, Julia, Lua, Perl, Elixir, Erlang, Haskell, OCaml, F#, Clojure, Shell, Bash, Zsh, PowerShell, SQL, HTML, CSS, SCSS, JSON, YAML, TOML, XML, Markdown, GraphQL, Dockerfile, Nginx, Makefile, Vim script, Solidity, Zig, Nim, V, and many more. Plain text and Markdown render cleanly even when no specific language is detected.

Yes. Line numbers are off by default to keep the output clean, but you can turn them on per file from the editor's per-file overrides. Useful for code reviews, assignment submissions where the grader needs to refer to specific lines, and for any handout where the reader will discuss the code with someone else.

Related Per-file overridesSettings reference

Anything with the File System Access API: Chrome, Edge, Brave, Opera, Arc. Firefox and Safari haven't shipped the API yet, so PDFy can't open folders there. The site itself loads fine and explains the situation if you visit on an unsupported browser.

Related Browser support details

Yes. The output is real text, not a screenshot. You can Ctrl-F your way through it, copy lines, and let any code-aware tool index it. Syntax highlighting is preserved as styled text, not as images, so file size stays small and the output is friendly to grep, archive search, and copyright registration tooling.

Source code in any language Shiki supports gets syntax-highlighted. Plain text and Markdown are formatted nicely. Images get embedded. Binary files are skipped with a placeholder. PDFs already in your folder are rasterised and embedded page-by-page.

Limited mostly by your browser's memory and how much of your folder you actually pick. Hundreds of files is comfortable. Tens of thousands works but the preview slows down. There is no server-side cap because there is no server.

Yes. The cover and TOC titles are click-to-edit. Headers and footers have six slots (top and bottom, left, center, right) that accept Mustache templates with variables like {{title}}, {{page}}, {{path}}, {{date}}.

Related Cover pageTable of contentsHeaders and footersTemplating variables

After the first visit, the page itself is cached by the browser. The first time you use a new language for syntax highlighting, the grammar gets fetched from a CDN. Once it's cached, subsequent runs are fully offline.

Yes. Nothing is uploaded, no third party sees your code, and there is no telemetry tied to file contents. The privacy page lists exactly what crosses the network (analytics page views, the GitHub API call for the home page's star count, and the static site assets themselves).

Related Privacy page

PDFy aggregates many files into one document, generates a cover and TOC, runs syntax highlighting consistently, paginates wrap-aware so long lines don't break, and lets you reorder or rename sections without touching the source files.