Default Encoding Behavior in FileReader and FileWriter
What you'll learn: How FileReader and FileWriter choose character encoding automatically and why this matters for cross-platform text file compatibility.
The Encoding Decision You Didn't Make
When you create a FileReader or FileWriter, you haven't specified how characters should be converted to bytes (and vice versa). Both classes silently use your platform's default character encoding—the encoding your operating system prefers. On Windows, this might be windows-1252 or Cp1252. On Linux or macOS, it's typically UTF-8.
Why This Matters
Imagine you write a text file on a Windows machine using FileWriter:
FileWriter writer = new FileWriter("data.txt");
writer.write("Café");
writer.close();
The character é gets encoded using Windows's default encoding. Now someone on a Linux machine reads it with FileReader:
FileReader reader = new FileReader("data.txt");
// Reads using UTF-8 default encoding
The character may appear corrupted because the two systems used different encodings.
The Implicit Contract
Think of default encoding like speaking your "native language" without asking if the other person understands it. FileReader and FileWriter assume everyone speaks the same language—but that's often not true across different systems or even different user configurations on the same OS.
When Default Encoding Works
- Single-platform applications where all users share the same OS configuration
- Quick prototypes or learning exercises
- ASCII-only text (since ASCII is compatible with most encodings)
When It Fails
- Cross-platform file sharing
- International text with special characters
- Web applications serving diverse users
- Any production code requiring predictable behavior
Key Takeaway: FileReader and FileWriter use the platform's default encoding implicitly, which creates portability risks—files written on one system may not read correctly on another with different encoding defaults.