How to fix warning: CRLF will be replaced by LF in file.txt in Git

This warning is informational, not an error. Git is telling you it will normalize line endings when storing the file. This is often the desired behavior for cross-platform projects.

If you're working on a cross-platform project, this normalization is helpful - it prevents line ending differences from cluttering your diffs and history.

To proceed with the commit despite the warning:

git add .
git commit -m "Your commit message"

The warning will not prevent your commit from succeeding.

Git's core.autocrlf setting controls automatic line ending conversion. Choose based on your situation:

On Windows (recommended for cross-platform projects):

git config --global core.autocrlf true

This converts LF to CRLF when checking out, and CRLF to LF when committing. Best for Windows developers on mixed teams.

On macOS/Linux:

git config --global core.autocrlf input

This converts CRLF to LF on commit but doesn't change files on checkout.

To disable conversion entirely:

git config --global core.autocrlf false

Files are stored exactly as-is. Use this only for single-platform projects.

If you understand the conversion behavior and don't want to see the warning, you can disable it:

git config --global core.safecrlf false

Alternatively, to only warn (not block) on irreversible conversions:

git config --global core.safecrlf warn

Note: This doesn't change the conversion behavior, just hides the message.

For consistent behavior across all contributors, create a .gitattributes file in your repository root:

# Set default behavior for all text files
* text=auto

# Explicitly set line endings for specific file types
*.sh text eol=lf
*.bash text eol=lf
*.bat text eol=crlf
*.cmd text eol=crlf

# Binary files that should not be modified
*.png binary
*.jpg binary
*.exe binary

This overrides individual developer's core.autocrlf settings, ensuring everyone uses the same line endings.

Commit this file to your repository:

git add .gitattributes
git commit -m "Add .gitattributes for consistent line endings"

If you've added a .gitattributes file or changed your autocrlf settings and want to apply the new settings to existing files:

# Stage all files for renormalization
git add --renormalize .

# Commit the normalized files
git commit -m "Normalize line endings"

This re-applies the line ending rules to all tracked files. After this, everyone who pulls will have consistent line endings.

Configure your text editor to use the line endings appropriate for your project:

VS Code:
1. Open Settings (Ctrl+,)
2. Search for "eol"
3. Set "Files: Eol" to "\n" (LF) for Unix or "auto" to match the file

Or per-workspace in `.vscode/settings.json`:

{
  "files.eol": "\n"
}

JetBrains IDEs (IntelliJ, WebStorm, etc.):
1. Settings > Editor > Code Style
2. Set "Line separator" to "Unix and macOS (\n)"

This prevents the issue at the source by saving files with consistent line endings.