All 15 I/O & NIO questions
More in I/O & NIO
What is the difference between byte streams (InputStream/OutputStream) and character streams (Reader/Writer) in the classic java.io package? How does wrapping a FileInputStream in a BufferedInputStream (or FileReader in a BufferedReader) improve I/O performance, and what's the mechanism behind this improvement? What are the modern java.nio.file utility classes (Path, Files) introduced in Java 7 (NIO.2), and how do they improve on the older java.io.File class? How would you implement object serialization using ObjectOutputStream/ObjectInputStream, and what does the Serializable marker interface and serialVersionUID actually do? How would you use try-with-resources combined with multiple chained I/O wrapper classes (like FileInputStream wrapped in BufferedInputStream wrapped in GZIPInputStream) to correctly read a compressed file while ensuring all layers are properly closed? How would you use the WatchService API (java.nio.file) to monitor a directory for file system changes (creation, modification, deletion) in real time? What is the purpose of the PrintStream and PrintWriter classes (like System.out), and how do they differ from lower-level OutputStream/Writer in their exception-handling behavior? How would you recursively copy an entire directory tree (including all subdirectories and files) using the Files.walkFileTree() method and a FileVisitor implementation? How does java.nio's Channel and Buffer abstraction differ fundamentally from the classic java.io Stream model, and what specific capability does this enable for non-blocking I/O? How would you implement memory-mapped file I/O using MappedByteBuffer, and what performance advantage does this provide for very large files compared to traditional stream-based reading?
Advertisement
Java › I/O & NIO

How do you read all bytes or all lines of a small-to-medium text file in a single, concise call using modern NIO.2 utility methods?

Beginner

Answer

For files small enough to comfortably fit entirely in memory, Files.readString(path) (Java 11+) reads an entire file's content as a single String in one call, and Files.readAllLines(path) reads it as a List<String> (one element per line) -- both dramatically more concise than the older manual approach of opening a BufferedReader and looping with readLine(), appropriate specifically for smaller files where loading everything into memory at once isn't a concern (for very large files, a streaming approach like Files.lines() returning a lazily-evaluated Stream<String> avoids loading the entire file into memory at once).
// Read entire file as one String (Java 11+)
String content = Files.readString(Path.of("config.json"));

// Read entire file as a List of lines
List<String> lines = Files.readAllLines(Path.of("data.csv"));

// For large files: lazily-streamed line-by-line processing instead
try (Stream<String> lineStream = Files.lines(Path.of("huge.log"))) {
    long errorCount = lineStream.filter(line -> line.contains("ERROR")).count();
}
Real-world example A configuration-loading utility reads an entire small JSON config file into a String using the concise Files.readString() one-liner, replacing what would have previously required several lines of manual BufferedReader setup, reading, and closing.

Common follow-ups: At what file size does loading the entire file into memory with readAllLines()/readString() become a genuine concern versus using a streaming approach?;What charset does Files.readString() assume by default, and how would you specify a different one?

Java Fundamentals: Syntax Data Types & Operators;File Uploads & Streaming Large Files
All 15 I/O & NIO questions