Scanner for Console Input — Read console input using Scanner (intro)

Early computer programs ran in a purely batch processing style: a programmer prepared all instructions and data in advance, submitted them, and waited for results. There was no way to pause a program and ask the user a question mid-run. As computers became more accessible in schools and offices, developers needed a simple way to create interactive programs — programs that respond to what a user types while the program is running.

Java's original release in 1995 included low-level tools for reading input, but they were clunky and error-prone. The language designers eventually introduced the Scanner class in Java 5 (2004) specifically to make reading input from the console — and other sources — much easier. Today, Scanner is one of the first tools every Java student learns.

The central question Scanner answers is straightforward: How can a Java program pause, wait for the user to type something, and then store that input in a variable? Understanding this opens the door to building programs that feel alive — from simple calculators to text-based games.

Before writing any code, you need to understand a few foundational ideas about how Java handles input. The console (also called the terminal or command line) is the text-based window where your program prints output and where users type input. Java represents the keyboard input stream as System.in, and the Scanner class acts as a translator between that raw stream of bytes and the data types your program needs — like int, double, or String.

Notice how the Scanner sits between the raw input stream and your program's variables. Without it, you'd have to manually convert bytes into characters and then parse those characters into numbers — a tedious and error-prone process. The Scanner handles all of that work behind the scenes, so you only need to call one method to get exactly the data type you want.

Scanner provides a family of methods, each designed to read a specific data type. When you call one of these methods, the program blocks — it freezes and waits — until the user types something and presses Enter. The Scanner then attempts to interpret (or parse) the input as the requested type. If the user types text when your code expects an integer, an InputMismatchException is thrown — but for now, we'll focus on the happy path where the user types correctly.

Key Scanner Methods

The key pattern to remember is: prompt, read, use. First, print a message telling the user what to type (using System.out.print()). Then, call the appropriate Scanner method to read their response. Finally, use the stored value in your program's logic.

Choosing the right Scanner method depends entirely on the type of data you expect the user to enter. Imagine you're building a simple student registration form: you need a name (text), an age (whole number), and a GPA (decimal number). Each of these requires a different method call, and the variable you store the result in must match the return type.

One of the most important distinctions to understand is the difference between next() and nextLine(). The next() method reads only until it hits a space, making it perfect for single-word inputs like a first name. The nextLine() method reads everything the user types until they press Enter, making it the right choice when you need a full sentence or a name with spaces (like "Maria Garcia"). When in doubt about reading text, nextLine() is usually the safer choice.

Let's build a complete program that asks the user for a temperature in Fahrenheit and converts it to Celsius. This example uses the full Scanner workflow from import to output.

Scanner is a powerful beginner tool, but like any tool, it has strengths and weaknesses. Understanding both will save you hours of debugging. Here's a clear comparison to keep in mind as you write interactive programs.

As your programs grow more complex, you'll encounter situations where Scanner isn't the best fit. It's helpful to know what lies ahead so you can see where Scanner fits in the bigger picture of Java I/O (input/output). The table below compares Scanner with two other common approaches you may encounter in more advanced courses or projects.

Don't worry about memorizing BufferedReader or JOptionPane right now. The important thing is knowing that Scanner is your foundation. The concepts you're learning — prompting the user, reading input, storing it in the right variable type — transfer directly to every other input method. Once you master the Scanner workflow, upgrading to more advanced techniques later will feel natural.