how to run java program in cmd

Screenshot of Windows Command Prompt showing 'javac' and 'java' commands being executed

To run a Java program in the Command Prompt (CMD), compile the source code with javac and execute the resulting bytecode with java. This requires a properly installed JDK and correct system PATH configuration.

Java programs are written in human-readable source code (.java files) and must be compiled into bytecode (.class files) before execution. The Command Prompt provides direct access to the Java compiler (javac) and runtime engine (java). This process is essential for testing, debugging, and deploying Java applications outside integrated development environments (IDEs).

Running Java in CMD is standard practice in enterprise environments, academic settings, and CI/CD pipelines. It ensures consistent behavior across systems and supports automation scripts. The workflow is identical a complex server application.

Prerequisites: Install JDK and Set PATH

Before running any Java program in CMD, install the Java Development Kit (JDK). Oracle's OpenJDK 17 or later is recommended for production use. Download it from Adoptium.net, which offers free, open-source builds.

After installation, verify the JDK is accessible by opening CMD and typing:

java -version

If the command returns a version string (e.g., openjdk version "17.0.8"), the runtime is available. If not, the system cannot locate the java executable.

Set the PATH environment variable to include the JDK's bin directory. On Windows, go through to System Properties → Advanced → Environment Variables. Add C:\Program Files\Java\jdk-17\bin (adjust path to match your installation) to the Path variable under System Variables. Restart CMD after making changes.

Compile and Run: Step-by-Step Process

Create a file named HelloWorld.java with the following content:

public class HelloWorld {
    public static void main(String[] args) {
        System.out.println("Hello, World!");
    }
}

Save the file in a folder such as C:\projects\hello. Open CMD, go through to the directory:

cd C:\projects\hello

Compile the program using javac:

javac HelloWorld.java

This generates a HelloWorld.class file. If compilation fails, check for syntax errors or missing semicolons.

Run the compiled program with java:

java HelloWorld

Output: Hello, World!. Do not include the .class extension when running.

Common Errors and Fixes

The most frequent issue is "'java' is not recognized as an internal or external command." This occurs when the JDK is installed but not added to the system PATH. Recheck the PATH variable and restart CMD.

Another error is "Could not find or load main class." This happens when the class name in the java command doesn't match the filename. For example, if the file is MyApp.java, the command must be java MyApp.

Case sensitivity matters. A file named helloWorld.java must be compiled with javac helloWorld.java and run with java HelloWorld-note the capitalization. Java uses the exact class name, not the filename.

Comparison: CMD vs IDE

While IDEs like IntelliJ IDEA or Eclipse automate compilation and execution, using CMD gives precise control over the build process. It's essential for understanding how Java runs under the hood.

Aspect	CMD	IDE (e.g., IntelliJ)
Compilation command	`javac MyClass.java`	Automated via build tool
Execution command	`java MyClass`	Click "Run" button
Debugging	Manual breakpoints, logging	Integrated debugger with visual tools
Learning value	High - reveals JVM mechanics	Lower - abstracts underlying steps

Using CMD teaches you how Java programs are actually executed. This knowledge prevents dependency on IDE features and helps troubleshoot issues when deployment fails.

Real-World Example: Running a Script in Production

A company deploys a batch processor written in Java to a Linux server. The server has no GUI, so they use SSH to connect and run commands manually. They copy the compiled .class files and execute:

java -cp /app/batch.jar com.example.BatchProcessor

This command specifies the classpath and the main class. It mirrors the basic CMD workflow but includes additional flags for security and memory management.

I've deployed a similar script during a cloud migration. The server had no IDE, and the team relied entirely on CMD-style execution. We caught a missing dependency early because the error message was clear: ClassNotFoundException. Without direct access to the command line, we'd have struggled to diagnose the root cause.

Key Distinction: javac vs java

javac compiles source code into bytecode. It does not run the program. java executes the bytecode. These are separate tools with distinct purposes.

Some users confuse java with javac. Typing java HelloWorld.java fails because java expects a class name, not a source file. Always compile first, then run.

As Oracle states in the Java Compiler Manual, javac converts Java source files into platform-independent bytecode. The Java Runtime Manual confirms that java launches the JVM and loads the specified class.

Best Practices

Use absolute paths when working in shared environments. Avoid spaces in project directories. Name your main class exactly as the filename (e.g., Calculator.java must contain public class Calculator).

For multiple classes, compile all files together: javac *.java. Then run the main class: java MainClass.

When scripting, use batch files (.bat) to automate the process. Create a file called run.bat with:

@echo off
javac *.java
java MainClass
pause

This simplifies repetitive tasks and reduces typos.

Understanding how to run a Java program in CMD is foundational for any developer. It enables direct interaction with the JVM, supports troubleshooting, and prepares you for automated workflows. managing a server, mastering this process ensures reliability and clarity.