Claude Code Terminal Output Garbled on Windows Fix 2026

Windows users running Claude Code frequently encounter garbled output—characters that appear as boxes, question marks, or completely wrong symbols. This problem stems from encoding mismatches between Claude Code’s output and Windows terminal expectations. In 2026, several reliable solutions exist to fix this issue and restore clean, readable terminal output.

Understanding the Garbled Output Problem

Claude Code outputs text using UTF-8 encoding by default. Windows terminals, particularly Command Prompt (cmd.exe) and older PowerShell configurations, often default to legacy encodings like Windows-1252 or the system’s active code page (typically CP437 or CP1252). When UTF-8 encoded characters hit a terminal expecting a different encoding, characters get misinterpreted, resulting in garbled output.

The problem manifests in several ways:

• Special characters (→, ©, ü, ñ) appear as boxes or question marks
• Non-ASCII characters display incorrectly
• JSON output shows escaped Unicode sequences instead of actual characters
• Colored terminal output displays as garbled text

Primary Solution: Configure Terminal Encoding

The most effective fix involves setting your Windows terminal to use UTF-8 encoding consistently.

PowerShell Configuration

Open PowerShell and run the following commands to set UTF-8 globally:

[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
$env:PYTHONIOENCODING = "utf-8"

To make this permanent, add these lines to your PowerShell profile:

# Create profile if it doesn't exist
if (-not (Test-Path $PROFILE)) {
    New-Item -ItemType File -Path $PROFILE -Force
}

# Add encoding settings
"[Console]::OutputEncoding = [System.Text.Encoding]::UTF8" | Add-Content $PROFILE
'$env:PYTHONIOENCODING = "utf-8"' | Add-Content $PROFILE

Windows Terminal (Recommended)

If you use Windows Terminal, configure the default encoding in settings:

1. Open Windows Terminal Settings
2. Navigate to Profiles → Defaults → Advanced
3. Set “Character set” to UTF-8
4. Alternatively, add this to your settings.json:

{
  "profiles": {
    "defaults": {
      "font": {
        "face": "Cascadia Code"
      }
    },
    "list": [
      {
        "guid": "{...}",
        "commandline": "powershell.exe",
        "env": {
          "PYTHONIOENCODING": "utf-8"
        }
      }
    ]
  }
}

Command Prompt Fix

For Command Prompt users, execute this before running Claude Code:

chcp 65001

This command changes the active code page to UTF-8 (code page 65001). For a permanent solution, create a batch file:

@echo off
chcp 65001 >nul
python -m claude_code %*

Save this as claude.bat and place it in a directory in your PATH.

Solution: Set Claude Code Environment Variables

Claude Code respects several environment variables that control encoding behavior. Set these before launching Claude Code:

$env:CLAUDE_CODE_UTF8 = "1"
$env:LANG = "en_US.UTF-8"
$env:LC_ALL = "en_US.UTF-8"

For permanent configuration, add them to your system environment variables:

1. Press Win + R, type sysdm.cpl, press Enter
2. Go to Advanced → Environment Variables
3. Under User variables, click New
4. Add each variable with value 1 or en_US.UTF-8

Solution: Terminal Font Compatibility

Some fonts don’t support the full Unicode character range that Claude Code uses. Switching to a font with Unicode support resolves display issues:

• Cascadia Code: Microsoft’s monospace font with excellent Unicode support
• JetBrains Mono: Popular developer font with wide character coverage
• Fira Code: Another solid option with ligatures and Unicode support

Configure your terminal to use one of these fonts. In Windows Terminal, navigate to Profiles → Your Profile → Appearance and select a compatible font.

Solution: Update Claude Code Installation

Outdated Claude Code versions may have encoding bugs that newer releases have fixed. Ensure you have the latest version:

# Check current version
claude --version

# Update Claude Code
claude update

# Or reinstall if needed
npm install -g @anthropic-ai/claude-code

Troubleshooting Specific Symptoms

JSON Output Appears Garbled

When Claude Code returns JSON with Unicode characters, force JSON output to use ASCII-safe representations:

$env:CLAUDE_CODE_JSON_ASCII = "1"

Colored Output Displays Incorrectly

ANSI color codes sometimes display as garbled text on Windows. Install a terminal that handles ANSI escape sequences properly:

# Install Windows Terminal from Microsoft Store
winget install Microsoft.WindowsTerminal

# Or use ConEmu
winget install ConEmu.ConEmu

Git Bash or WSL Specific Issues

If running Claude Code through Git Bash or WSL:

# In .bashrc or .zshrc
export PYTHONIOENCODING=utf-8
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8

# In WSL, also ensure Windows-side encoding is set

Verification: Testing Your Fix

After applying solutions, verify that Claude Code displays output correctly:

# Test Unicode character display
claude -p "Print a Unicode test: ← → © ™ €"

# Test JSON output
claude -p "Return JSON with special chars: {'symbol': '✓', 'arrow': '→'}"

# Comprehensive encoding test
@"
Testing encoding:
- Arrows: ← → ↑ ↓ ↔ ↕
- Math: ± × ÷ ≈ ≠ ≤ ≥
- Currency: $ € ¥ £ ₹ ₽
- Symbols: © ® ™ ° § ¶
- Emoji: 🚀 ⚡ ✅ ❌
"@ | claude -p $_

If characters display correctly, your configuration is working. If issues persist, check for conflicting environment variables or terminal-specific settings.

Advanced Diagnostics

Encoding Detection Script

Create a diagnostic script to identify encoding issues automatically:

# detect-encoding-issues.ps1
function Test-EncodingCompatibility {
    param(
        [string]$TestString = "← → © ™ € ✓ 🚀"
    )

    Write-Host "System Encoding Information:"
    Write-Host "  Default console encoding: $([System.Console]::OutputEncoding)"
    Write-Host "  PYTHONIOENCODING: $env:PYTHONIOENCODING"
    Write-Host "  LANG: $env:LANG"
    Write-Host "  LC_ALL: $env:LC_ALL"

    Write-Host "`nTesting character output:"
    Write-Host "  Input: $TestString"

    # Create UTF-8 temp file
    $utf8File = New-TemporaryFile -Suffix '.txt'
    [System.Text.Encoding]::UTF8.GetBytes($TestString) |
        Set-Content $utf8File -AsByteStream

    Write-Host "  File encoding verified: UTF-8"

    # Test terminal rendering
    $rendered = Get-Content $utf8File
    Write-Host "  Rendered: $rendered"

    Remove-Item $utf8File

    # Test Python interop
    Write-Host "`nPython encoding test:"
    python -c "import sys; print(f'Python encoding: {sys.getdefaultencoding()}')"
}

Test-EncodingCompatibility

Batch Encoding Reset

When multiple encoding issues arise, reset everything systematically:

@echo off
REM reset-encoding.bat - Complete encoding reset for Windows

echo Resetting encoding configuration...

REM Clear environment variables
set PYTHONIOENCODING=
set LANG=
set LC_ALL=

REM Set UTF-8 as default
chcp 65001 >nul

REM Configure PowerShell permanently
powershell -NoProfile -Command ^
  "if (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force } | Out-Null; " ^
  "'[Console]::OutputEncoding = [System.Text.Encoding]::UTF8' | Add-Content $PROFILE"

REM Configure Node.js
set NODE_ENV_UTF8=1

echo Configuration reset complete. Restart terminals for full effect.

Platform-Specific Encoding Tables

Code Page Reference

For Claude Code: Always use 65001 (UTF-8).

Integration with CI/CD Pipelines

When running Claude Code in automated environments:

# .github/workflows/claude-code.yml
name: Claude Code with Proper Encoding

on: [push]

jobs:
  build:
    runs-on: windows-latest
    env:
      PYTHONIOENCODING: utf-8
      LANG: en_US.UTF-8
      LC_ALL: en_US.UTF-8

    steps:
      - uses: actions/checkout@v3

      - name: Set UTF-8 Code Page (Windows)
        shell: cmd
        run: chcp 65001

      - name: Run Claude Code
        shell: powershell
        run: |
          [Console]::OutputEncoding = [System.Text.Encoding]::UTF8
          claude generate-report.prompt

Troubleshooting Terminal Emulator Issues

ConEmu Configuration

If using ConEmu, add to its settings:

[ConEmu]
DefaultCP=65001
UnicodeFont=1
UnNestMonitorConEmu=1

Git Bash Configuration

# ~/.bash_profile or ~/.bashrc in Git Bash
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
export PYTHONIOENCODING=utf-8

# Ensure Git uses UTF-8
git config --global i18n.logoutputencoding utf-8
git config --global i18n.commitencoding utf-8

WSL (Windows Subsystem for Linux) Configuration

# In WSL ~/.zshrc or ~/.bashrc
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

# Set Windows-side environment for interop
export PYTHONIOENCODING=utf-8

Then from Windows, set:

$env:LANG = "en_US.UTF-8"
$env:LC_ALL = "en_US.UTF-8"

Long-term Maintenance

Monthly Encoding Audit

Create a scheduled task to verify encoding health:

# encoding-audit.ps1 - Scheduled monthly check
$auditDate = Get-Date -Format "yyyy-MM-dd HH:mm"

$auditResults = @{
    Timestamp = $auditDate
    ConsoleEncoding = [System.Console]::OutputEncoding
    EnvironmentVars = @{
        PYTHONIOENCODING = $env:PYTHONIOENCODING
        LANG = $env:LANG
        LC_ALL = $env:LC_ALL
    }
    WindowsTerminalVersion = (Get-Command wt -ErrorAction SilentlyContinue).Version
    ClaudeCodeVersion = (claude --version 2>$null)
}

$auditResults | ConvertTo-Json |
    Out-File "encoding-audit-$($auditDate -replace ':','-').json"

Write-Host "Encoding audit saved."

Common Post-Update Issues

After Windows or terminal updates, re-apply UTF-8 configuration:

# Post-update encoding check
Write-Host "Verifying encoding after system update..."

# Check if UTF-8 was reset
$currentCP = (chcp) -match '\d{5}' | ForEach-Object { [int]$_.Matches[0].Value }

if ($currentCP -ne 65001) {
    Write-Warning "Code page reset to $currentCP. Restoring UTF-8..."
    chcp 65001 | Out-Null
}

# Verify environment variables
if (-not $env:PYTHONIOENCODING -eq 'utf-8') {
    Write-Warning "PYTHONIOENCODING not set. Configuring..."
    [Environment]::SetEnvironmentVariable('PYTHONIOENCODING', 'utf-8', [EnvironmentVariableTarget]::User)
}

Write-Host "Encoding verification complete."

Preventive Measures: Avoid Garbled Output

1. Use Windows Terminal instead of Command Prompt - it handles UTF-8 natively
2. Keep fonts updated - ensure your terminal font supports Unicode
3. Monitor system updates - Windows updates sometimes reset code page settings
4. Use configuration management - store encoding settings in version control
5. Test regularly - use the test scripts above monthly