finally block0%
Throwing Custom Errors

finally block

Beginner12 min read•Updated: Jul 11, 2026
Study Materials

The finally Block in Modern JavaScript

In mission-critical applications, releasing resources (such as closing database connections, unlocking file handles, or hiding loading spinners) must happen reliably whether an operation completes successfully or crashes midway. The finally clause guarantees execution regardless of the outcome.

1. Syntax & Execution Guarantee

JavaScript
try {
console.log('1. Initiating resource transaction...');
performRiskyOperation();
console.log('2. Transaction successful!');
} catch (error) {
console.error('2. Transaction failed:', error.message);
} finally {
console.log('3. Cleanup: Releasing lock and closing connection.');
}

Whether performRiskyOperation() succeeds or throws, step 3 (finally) is always guaranteed to execute.

2. finally Executes Even with Early Return!

A remarkable property of finally is that it executes even if the try or catch block executes an early return statement:

JavaScript
function processPayment() {
try {
console.log('Processing payment...');
return 'SUCCESS'; // Return statement encountered!
} catch (err) {
return 'FAILED';
} finally {
// THIS STILL RUNS BEFORE THE CALLER RECEIVES THE VALUE!
console.log('Audit log entry created.');
}
}
 
const status = processPayment();
console.log('Result:', status);

Console Output:

  1. 1
    Processing payment...
  2. 2
    Audit log entry created. (Finally executes first!)
  3. 3
    Result: SUCCESS

3. The Dangerous Anti-Pattern: Returning from finally

If you explicitly return a value from inside the finally block, it will override any previous return value or thrown exception from try or catch:

JavaScript
function dangerousCode() {
try {
throw new Error('Fatal Database Crash!');
} finally {
return 42; // OVERWRITES THE THROWN ERROR!
}
}
 
console.log(dangerousCode()); // 42 (The error was completely swallowed!)
Rule of Thumb: Use finally strictly for side-effects and cleanup (closing streams, toggling boolean loading flags, resetting timers). Never return values or throw new errors inside finally.

4. try...finally without a catch Block

You can pair try directly with finally without a catch block. In this scenario, the cleanup code executes, and the exception continues bubbling up to the caller:

JavaScript
function writeToFile(fileHandle, data) {
try {
fileHandle.write(data);
} finally {
// Guarantees file is always closed, even if write() crashes!
fileHandle.close();
}
}
Interactive Quiz

Practice Quiz

Question 1
When does the finally block execute?
Question 2
What happens if a function returns 'A' in try, but returns 'B' in finally?
Question 3
Can you have a try statement with a finally block but NO catch block?
Question 4
What is the primary intended use case for a finally block?
Question 5
If an error is thrown in try and swallowed by a return in finally, what does the caller experience?
Next Lesson

Throwing Custom Errors

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous LessonNext Lesson
try...catchThrowing Custom Errors

Practice Quiz

Test your understanding of this lesson with 5 questions. Each question has one correct answer.

PreviousNext
PrevNext