# Git version control for handwritten notes as PDFs

How to store scanned handwritten notes as PDFs in Git, what binary files do to a repository, and when Git LFS or a scan-and-commit routine helps.

Git version control for handwritten notes as PDFs means storing scans of your paper notes in a Git repository so each version is tracked. Git records every saved change, but a PDF is a binary file, so Git stores a full copy of the file at each commit instead of a line-by-line difference. The page explains how that works, how to commit scans cleanly, and when Git LFS (Large File Storage) keeps a repository manageable. 

## Why PDFs behave differently in Git 

A PDF is a binary file, so Git cannot show changes line by line the way it does with plain text. Each commit that changes a scanned note stores a complete new copy of the file inside the repository. That keeps the history intact but makes the repository grow with every scan you save. Plain-text notes stored beside the PDFs stay readable and diffable in the same repository. 

## A steady scan and commit routine 

A scan and commit workflow keeps handwritten notes current without extra effort. Scan the page, give the PDF a name that includes the date and subject, and save it in a folder for the week or topic. Commit the file with a short message describing what the note covers, such as a handover or an appointment list. Doing this in one sitting after writing keeps the history tidy and easy to follow. 

## Keeping the repository manageable 

Git LFS moves large binary files out of the main repository and stores a small pointer in their place. PDF versions in Git then cost little room in the history, while the full scans sit in separate storage. Use Git LFS when your scanned handwritten notes are large or saved often. For a small set of notes, plain Git still works if you keep the files modest in size. 

## Questions about Git and handwritten notes 

### Can I use Git for handwritten notes? 

Yes, Git can track handwritten notes once you scan them into a file such as a PDF. Git version control records each commit, so you can return to an earlier scan if a page is lost or overwritten. The tradeoff is that binary files take more space than plain text, so keep the scans organized. 

### Does Git store a full copy of each PDF version? 

Yes, Git stores a complete copy of each changed PDF in the history. Binary files in Git do not compress into line changes, so every committed scan adds a full file to the repository. This is why a long history of large scans grows quickly. 

### What is Git LFS and do I need it for scanned notes? 

Git LFS is an extension that stores large files outside the main repository and keeps a pointer in their place. You need it when your scanned handwritten notes are large or committed often enough to bloat the repository. A small collection of modest PDFs can stay in plain Git without LFS. 

### How should I name and commit scanned notes? 

Name each scanned note with a date and a short subject, then commit it with a message that says what the page covers. A steady scan and commit routine after writing keeps the PDF versions in Git easy to find. Organize the files into folders by week or topic so the history stays readable.
