Should try‑catch be placed inside or outside a for loop in Java?

In this article we discuss whether a try‑catch block should be placed inside or outside a for loop when reading multiple files in Java.

Placing the try‑catch outside the loop allows a single unified handling of any exception that occurs, preventing the program from crashing and keeping the code layout clean.

try {
    for (int i = 0; i < fileList.size(); i++) { // loop reading files
        String fileName = fileList.get(i); // get file name
        readFile(fileName); // read file method
    }
} catch (FileNotFoundException e) {
    System.out.println("File not found, please check before running!");
} catch (IOException e) {
    System.out.println("IO exception, please check your network connection!");
}

However, putting the try‑catch inside the loop can be useful when each file read may fail independently, allowing the loop to continue processing remaining files.

for (int i = 0; i < fileList.size(); i++) { // loop reading files
    try {
        String fileName = fileList.get(i); // get file name
        readFile(fileName); // read file method
    } catch (FileNotFoundException e) {
        System.out.println("File not found, please check before running!");
    } catch (IOException e) {
        System.out.println("IO exception, please check your network connection!");
    }
}

The downside of the inner placement is duplicated code and potential performance impact; the choice depends on business requirements and the desired robustness of the application.

In addition, the article includes a promotional notice offering a free “Programmer Book Collection” and a QR‑code for downloading a book management system.