How to clip GitHub README to PDF without the repo chrome
Clip a GitHub README to PDF by selecting the document, not the repo shell. Keep a local, searchable copy with Excerpt.
Also on Microsoft Edge Add-ons
A repository page is mostly chrome: the file tree, the branch switcher, the stars, the issue count. If you clip GitHub README to PDF, select the README document itself so the file is the installation notes, the badges-as-text, and the code fences you wanted—not a printout of the entire GitHub shell.
Excerpt’s web clipper path is a page selection. It is not an official GitHub integration, and it will not clone the repo or follow every relative link into other files.
Clip GitHub README to PDF in four steps
- Open the README on the repo’s default view (or the blob view for a single Markdown file) and wait until the rendered document is visible.
- Select from the title through the last section you need. Avoid the left files pane, the top repo header, and the comment box if one is on the page.
- Export PDF if you want a snapshot to attach, or Markdown if you will paste the instructions into your own notes.
- Write down the repo, branch or commit, and date in a one-line note or tag. READMEs change; the clip is what you saw, not a live file.
What a README clip will not include
- Other files in the tree, unless you open them and clip those pages separately.
- Rendered diagrams that are actually external images, if they do not appear in the selection as usable graphics.
- Private repo content you only saw after signing in—keep that clip on a machine and a profile that are allowed to hold it.
Relative links such as “see /docs/deploy.md” will not magically become a second chapter. If that page matters, open it and make a second clipping. The same is true of wiki pages and GitHub Discussions, which are different documents.
Code fences deserve a glance after export
Open the file and check that indented code still looks like code, especially if you chose PDF. If you will copy commands later, Markdown is usually the better export. A screenshot of the README is a last resort: you cannot search it well, and copy-paste from a picture is how people mistype install flags.
File it next to related notes
You can keep the README beside a ChatGPT or Claude troubleshooting note in the same local IndexedDB library. Free includes 100 clippings and 5 tags; Pro is $29 one-time for unlimited clippings plus backup import/export. There is no cloud sync and no AI summarizer claimed as shipped.
LICENSE, CHANGELOG, and contributing guides are separate documents. If you need those, open each file and clip it on its own. The repo homepage can also differ from the README blob view. Choose the URL you want to remember, and avoid clipping a README rendered inside a pull request unless that PR version is specifically the one you reviewed.
Use Chrome or Edge, clip the document not the shell, and treat the PDF as a dated snapshot of a file that the maintainers may rewrite tomorrow.
FAQ
Does Excerpt download the whole repository?
No. It saves the selection you make on the page, usually the rendered README. Clone the repo separately if you need the project files.
Should I include the repo header and file tree?
Usually no. They add noise and date poorly. Record the repo name, commit or branch, and date in a short note instead.
Related guides
Install Excerpt and save your next clip as a clean PDF
Free: up to 100 clippings and 5 tags. Pro is $29 one-time for unlimited + library backup import/export.