But have you ever wondered what Git actually does behind the scenes? 🤔

In this article, we’ll understand how Git works internally, using easy language, real-life analogies, and zero complex theory.

1. How Git Works Internally

Think of Git as a smart photo album 📸 for your code.

Every time you save (commit), Git takes a snapshot of your project

Git does not save full copies again and again

Instead, it saves only what has changed

So Git is:

Fast ⚡

Storage efficient 📦

Reliable 🔐

Internally, Git stores everything as objects inside a hidden folder called .git.

2. Understanding the .git Folder

When you run:

git init

Git creates a hidden folder called .git.

This folder is the brain 🧠 of Git.

Important folders inside .git

Folder/File

What it does (Simple)

objects/

Stores all code data (files, commits, folders)

refs/

Stores branch names and pointers

HEAD

Tells which branch you are currently on

index

Temporary area (staging area)

👉 If you delete the .git folder, your project is no longer a Git repository.

3. Git Objects: Blob, Tree, Commit

Git stores everything as objects.

There are 3 main object types.

1️⃣ Blob (File content)

Blob stores file content

It does NOT store file name

Same content = same blob (even if file name changes)

📄 Example:

Hello World

If two files have this same content, Git stores it only once.

2️⃣ Tree (Folder structure)

Tree stores file names + folder structure

It points to blobs and other trees

📁 Example:

project/

├── app.py

└── utils.py

Tree knows:

File names

Folder hierarchy

Which blob belongs to which file

3️⃣ Commit (Snapshot info)

Commit is like a label on a snapshot 🏷️

It contains:

Pointer to tree (project structure)

Author name

Date & time

Commit message

Parent commit reference

📝 Example:

"Added login feature"

4. How Git Tracks Changes

Git does NOT track changes line by line like Word documents.

Instead, Git:

Compares snapshots

Saves only new or changed content

What happens step-by-step?

Step 1: Modify a file

You edit main.py

Step 2: git add main.py

Git creates a blob

Stores it inside .git/objects

Updates the index (staging area)

Step 3: git commit

Git creates a tree

Git creates a commit

Commit points to the tree

Tree points to blobs

🎯 Result: A complete snapshot is saved efficiently.

Real-Life Analogy 🧠

Think of Git like a library system 📚

Blob → Page content

Tree → Book structure (chapters, pages)

Commit → Edition of the book

Branch → Different versions of the same book

Git only stores new pages, not the entire book again.