Boolean Conversion: Why "false" Can Be True in Code

Oct 19, 2026 · 2 min read · Developer

Here is a bug that catches almost every beginner: Boolean("false") in JavaScript returns true. It feels wrong, but the rule is simple. Any text that is not empty counts as true, even if the word inside is "false".

Truthy and falsy

In JavaScript, some values act as false when used in a condition. They are called falsy. There are only a few: false, 0, -0, 0n, an empty string, null, undefined and NaN. Everything else is truthy. That includes the text "0", the text "false", an empty array [] and an empty object {}.

Python is similar, with one difference

In Python, bool("False") is also True, because the text is not empty. But an empty list and an empty dictionary are False, unlike JavaScript.

Where this hurts

Settings are often saved as text: "true", "false", "1", "0", "yes", "no". If you load one and check it directly, "false" will turn the feature on. This is a classic cause of wrong behaviour in config files, environment variables and form data.

The safe way

Compare the text to the words you accept:

function toBool(text) {
  return ["true", "yes", "1", "on"].includes(text.trim().toLowerCase());
}

Decide what happens with unknown words. Treating them as false is common, but sometimes it is better to show an error.

Do not use == with booleans

Loose comparison gives odd results: "0" == false is true, but "0" on its own is truthy. Use === to avoid surprises.

See it in action

The Boolean Conversion tool on our Developer Converters page lets you type several values, one per line, and shows how JavaScript, Python and a word-based check treat each one. It is a quick way to learn the rules and test your own inputs.

Frequently asked questions