How to fix fatal: LF would be replaced by CRLF in file.txt. Set core.safecrlf to false in Git

What this error means

The "LF would be replaced by CRLF" error is Git's safety mechanism preventing accidental line ending changes when you try to add or commit files. This error appears when `core.safecrlf` is set to `true` (or `warn` in some cases) and Git detects that the operation would alter the file's line endings. **Understanding Line Endings:** - **LF (Line Feed, \n)**: Used by Unix, Linux, and macOS - **CRLF (Carriage Return + Line Feed, \r\n)**: Used by Windows - **CR (Carriage Return, \r)**: Used by old Mac systems (rare today) When you have `core.autocrlf` enabled (common on Windows), Git automatically converts line endings: - On checkout: LF in repo -> CRLF in working directory - On commit: CRLF in working directory -> LF in repo The `core.safecrlf` setting adds a safety check. When set to `true`, it prevents commits where the round-trip conversion (checkout then commit) would result in a different file than what's in the repository. This protects against data loss with binary files that happen to contain CRLF sequences. This error typically appears on Windows systems where autocrlf is enabled, and you're working with files that have mixed or LF-only line endings. It's more of a warning about potential line ending inconsistency than a critical error.

Typical symptoms

• Running 'git add' fails with 'fatal: LF would be replaced by CRLF'
• Git commit fails mentioning safecrlf and line ending conversion
• The error appears when adding new files or files from other platforms
• Files cloned from a Unix/Linux repository trigger this on Windows
• Projects shared between Windows and macOS/Linux developers see this error
• The error only appears for specific files, not all files in the repo
• CI/CD builds on Linux work but local Windows builds fail at git operations

Common causes

1. core.autocrlf is set to 'true' on Windows, causing automatic line ending conversion
2. core.safecrlf is set to 'true', making Git refuse potentially lossy conversions
3. The file has LF line endings but Git would convert them to CRLF on checkout
4. Mixed line endings in the same file confuse Git's conversion logic
5. A .gitattributes file specifies line ending handling that conflicts with global settings
6. Binary files are being treated as text files by Git
7. Files were edited by tools that use different line ending conventions
8. The repository was initialized with different autocrlf settings than your current config

How to fix "fatal: LF would be replaced by CRLF in file.txt. Set core.safecrlf to false"

# Check global settings
git config --global core.autocrlf
git config --global core.safecrlf

# Check local (repository) settings
git config core.autocrlf
git config core.safecrlf

# See all relevant config at once
git config --list | grep -E "(autocrlf|safecrlf|eol)"

git -c core.safecrlf=false add file.txt
git -c core.safecrlf=false add .

git config --global core.safecrlf false

git config core.safecrlf false

# Convert to CRLF on checkout, to LF on commit
git config --global core.autocrlf true
git config --global core.safecrlf warn

# Convert CRLF to LF on commit, no conversion on checkout
git config --global core.autocrlf input
git config --global core.safecrlf warn

# Disable autocrlf globally and use .gitattributes instead
git config --global core.autocrlf false
git config --global core.safecrlf false

git config --global core.autocrlf false

# Recommended .gitattributes for most projects
* text=auto

# Explicitly declare text files
*.txt text
*.md text
*.json text
*.xml text
*.yaml text
*.yml text
*.html text
*.css text
*.js text
*.ts text
*.py text
*.rb text
*.java text
*.c text
*.cpp text
*.h text
*.sh text eol=lf
*.bash text eol=lf

# Windows-specific files
*.bat text eol=crlf
*.cmd text eol=crlf
*.ps1 text eol=crlf

# Binary files (never convert)
*.png binary
*.jpg binary
*.jpeg binary
*.gif binary
*.ico binary
*.pdf binary
*.zip binary
*.tar binary
*.gz binary
*.exe binary
*.dll binary
*.so binary
*.dylib binary

# Add the .gitattributes file first
git add .gitattributes
git commit -m "Add .gitattributes for line ending normalization"

# Renormalize all files
git add --renormalize .
git status
git commit -m "Normalize line endings"

# Using file command (Unix/macOS/Git Bash)
file filename.txt

# Using cat with visible line endings
cat -A filename.txt | head -5
# ^M at end = CRLF, $ at end = LF

# Using xxd to see hex values
xxd filename.txt | head -10
# 0d 0a = CRLF, 0a = LF

# Convert to Unix (LF)
dos2unix filename.txt

# Convert to Windows (CRLF)
unix2dos filename.txt

# Convert CRLF to LF
sed -i 's/\r$//' filename.txt

# On macOS, use:
sed -i '' 's/\r$//' filename.txt

# Convert to LF
(Get-Content filename.txt -Raw) -replace "\r\n", "\n" | Set-Content -NoNewline filename-lf.txt

# Convert to CRLF
(Get-Content filename.txt -Raw) -replace "(?<!\r)\n", "\r\n" | Set-Content -NoNewline filename-crlf.txt

# Remove from index (keeps working copy)
git rm --cached filename.txt

# Re-add with new settings
git add filename.txt

# Save any uncommitted changes
git stash

# Remove all files from the index
git rm -r --cached .

# Re-add all files with new line ending settings
git add .

# Check what changed
git status
git diff --cached

# Commit if there are changes
git commit -m "Normalize line endings"

# Restore stashed changes
git stash pop

# More elegant approach - renormalize without removing from index
git add --renormalize .
git status
git commit -m "Normalize line endings"

# Add to .gitattributes
*.dat binary
*.bin binary
myfile.special binary

# Discard local changes and get fresh copy
git checkout HEAD -- filename.bin

# Or from a specific commit
git checkout abc123 -- filename.bin

# This shows how Git classifies the file
git check-attr -a filename

# Or specifically for diff/merge attributes
git check-attr diff filename
git check-attr merge filename

Advanced notes

# GitHub Actions example
- name: Configure Git
  run: |
    git config --global core.autocrlf false
    git config --global core.eol lf

{
  "files.eol": "\n",  // or "\r\n" for Windows
  "files.trimTrailingWhitespace": true,
  "files.insertFinalNewline": true
}

root = true

[*]
end_of_line = lf
insert_final_newline = true
charset = utf-8
trim_trailing_whitespace = true

[*.{bat,cmd}]
end_of_line = crlf

git rm -r --cached .
git reset --hard

git config --list --show-origin | grep -E "(autocrlf|safecrlf|eol)"

git check-attr -a -- problematic-file.txt

git clone -c core.autocrlf=false -c core.safecrlf=false <repo-url>

Frequently asked questions

What does "fatal: LF would be replaced by CRLF in file.txt. Set core.safecrlf to" mean?

The "LF would be replaced by CRLF" error is Git's safety mechanism preventing accidental line ending changes when you try to add or commit files. safecrlf is set to true (or warn in some cases) and Git detects that the operation would alter the file's line endings. safecrlf setting adds a safety check.

How do I fix "fatal: LF would be replaced by CRLF in file.txt. Set core.safecrlf to"?

This error occurs when Git's safecrlf setting detects that committing a file would change its line endings from LF (Unix-style) to CRLF (Windows-style), potentially causing issues in cross-platform projects. The fix involves configuring Git's line ending settings appropriately for your project and platform.

What causes "fatal: LF would be replaced by CRLF in file.txt. Set core.safecrlf to"?

core.autocrlf is set to 'true' on Windows, causing automatic line ending conversion core.safecrlf is set to 'true', making Git refuse potentially lossy conversions The file has LF line endings but Git would convert them to CRLF on checkout

Is the "fatal: LF would be replaced by CRLF in file.txt. Set core.safecrlf to" error serious?

It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• warning: unable to create symbolic link: Permission denied

  How to fix 'Unable to create symbolic link: Permission denied' in Git

  LOW

• error: invalid path 'CON' (reserved Windows name)

  How to fix 'error: invalid path' (reserved Windows name) in Git

  MEDIUM

• error: unable to create symlink: symbolic link privilege not held

  How to fix 'unable to create symlink: symbolic link privilege not held' in Git

  MEDIUM

• Another process is using this file: file.txt

  How to fix 'Another process is using this file' in Git on Windows

  MEDIUM

• API rate limit exceeded

  How to fix 'API rate limit exceeded' in GitHub

  MEDIUM

• fatal: destination path already exists and is not an empty directory

  Destination Path Already Exists and Is Not Empty

  LOW

Official resources & further reading

• 📚Git Official Documentation
• 📖
  Git Configuration - core.autocrlf - Git Book(Official Docs)
• 📖
  gitattributes - Defining attributes per path - Git Documentation(Official Docs)
• 💬
  Git replacing LF with CRLF - Stack Overflow(Stack Overflow)
• 📖
  Configuring Git to handle line endings - GitHub Docs(Official Docs)
• 💬
  CRLF vs. LF: Normalizing Line Endings in Git(Stack Overflow)