- Home
- Character limits
- Git commit message
How long should a Git commit message be?
Keep the subject line to about 50 characters and wrap the body at 72. Git sets no limit, but this “50/72” convention is what tools like GitHub and git log are designed around: long subjects get cut off.
Saved in this browser only. Nothing is uploaded.
Check the same text against X, Instagram, LinkedIn, YouTube, Google and SMS at once, with your own limit set to this one.
Open the character counterGit commit message: the numbers
| Shown in full up to about | 50 characters |
|---|---|
| Wrap body lines at | 72 |
| How it counts | Characters on the first line only. |
| English words that fit | 7–9 |
Last reviewed October 2026. Platforms change their limits; when it matters, check the platform’s help pages.
What counts as a character
- The counter measures the first line only: the subject.
- Leave a blank line between the subject and the body.
Best length vs the maximum
- Write the subject in the imperative: “Fix date parsing”, as if completing “This commit will…”.
- No full stop at the end of the subject.
- Use the body to explain why the change was made, not what: the diff shows what.
Questions and answers
Is there a maximum length for a commit message?
Not in Git itself. The 50/72 rule is a convention that keeps history readable in tools.
Why 72 characters for the body?
So the text stays readable in an 80-column terminal after git log indents it.