---
title: "Discussion on \"Why Git Commit Hashes Are Always 40 Characters Long\" | Hashnode"
description: "Discussion on \"Why Git Commit Hashes Are Always 40 Characters Long\". If you've used Git for more than a day, you've probably seen something like this:\n3f5e7c9a2b4d6e8f1a0b2c3d4e5f67890ab1c2de\n\nIt's always... 40 characters.\nNot 32. Not 64.\nExactly 40. Coincidence?\nNot a"
url: "https://hashnode.com/posts/why-git-commit-hashes-are-always-40-characters-long/6a7609373e6c12c0e977920d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Git Commit Hashes Are Always 40 Characters Long](https://blogs.ashikunnabi.com/why-git-commit-hashes-are-always-40-characters-long?utm_source=hashnode&utm_medium=feed)

If you've used Git for more than a day, you've probably seen something like this: 3f5e7c9a2b4d6e8f1a0b2c3d4e5f67890ab1c2de It's always... 40 characters. Not 32. Not 64. Exactly 40. Coincidence? Not a

Aug 7 · 4 min read · blogs.ashikunnabi.com  
Read the article

-   [#git](https://hashnode.com/tag/git)
-   [#github](https://hashnode.com/tag/github)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#system-architecture](https://hashnode.com/tag/system-architecture)

## Written by

[Md Ashikun Nabi](https://hashnode.com/@ashikunnabi)

@ashikunnabi · Dhaka, Bangladesh

  
[View profile](https://hashnode.com/@ashikunnabi)

Turning software ideas into maintainable, production-ready systems

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
