Baking soda is pure base, full stop. Left alone with no acid to react against, it doesn't leaven anything — it just sits there, chemically inert, until something sour shows up.
Sodium bicarbonate — baking soda — is roughly four times stronger than baking powder by weight, but it's also incomplete on its own. It needs to react with an acid to release the carbon dioxide gas that actually makes a batter rise. No acid, effectively no lift.
This is exactly why so many "classic" recipes — chocolate cake, banana bread, buttermilk pancakes — call for baking soda specifically instead of baking powder: they already contain a built-in acid, and baking soda reacting against it also helps neutralize excess acidity that could otherwise make the final product taste sour or overly tangy.
A common starting ratio is about 1/4 teaspoon of baking soda per 1 cup of flour, assuming the recipe has enough acidic ingredients to fully react with it. Too much baking soda relative to available acid leaves unreacted soda behind — and unreacted sodium bicarbonate has a distinctly bitter, soapy taste that's hard to miss once you know what to listen for.
If a recipe already has a clear acidic ingredient (buttermilk, brown sugar, cocoa, citrus), baking soda alone is often enough. If a recipe is neutral — plain milk, granulated sugar, no acidic mix-ins — it needs baking powder's built-in acid to do anything at all. Some recipes use both: baking soda to neutralize existing acid and aid browning, baking powder to provide the actual reliable lift.
Subscribe on YouTube for cake decorating and baking videos that put this science into practice.
Subscribe — it's free