Logarithms: How to Solve FE Problems Without Getting Lost in Base Conversions

The formula itself is simple enough. log_a(b) just asks: what power turns a into b? You learned this years ago.

The breakdown happens when you’re looking at log₆(3 × 2) and you know there’s a rule for products, but you freeze on whether it splits into addition or multiplication.

Or when the problem gives you ln(x) and log(x) in the same expression and you’re not sure if those mean different things or if you’re supposed to convert between them.

It’s not the concept that trips you up.

It’s the notation shifts, the overlapping rules, and the moment where you have to decide: do I expand this? Condense it? Convert the base? Or just recognize the pattern and evaluate directly?

The setup feels backward compared to exponentials. Instead of “raise this to a power,” you’re solving for the power itself.

And when you add that reversal to multiple logarithms being combined with different operations, the cognitive load stacks up fast.

Here’s what makes logarithms manageable: they follow a small set of consistent rules. Product inside the log? Split into a sum. Quotient? Split into a difference. Power? Pull it out front.

Once you map the structure to the rule, the execution becomes mechanical.

This guide gives you a decision tree that works on any logarithm problem the FE throws at you—from straightforward evaluations where you just need to recognize that 5³ = 125, to multi-step simplifications where you’re combining three logs using different rules in sequence.

You’ll learn which rule applies based on what’s inside the logarithm, how to execute base conversions without second-guessing yourself, and how to verify your setup matches what the problem is actually asking for.

Before we walk through it step by step, watch this short video. It shows you the full process from identifying the logarithm structure to applying the matching rule to finishing the simplification.

You’ll see exactly where students lose track of signs or confuse which base they’re working with, and how to avoid those traps completely.

What Are Logarithms?

Logarithms tell you the exponent you need to raise a base to in order to get a specific number.

If you know that 2⁴ = 16, then log₂(16) = 4. The logarithm is just asking: “What power turns 2 into 16?” The answer is 4.

In practical terms, logarithms measure relative growth or scale. When something doubles repeatedly—like bacteria in a culture or compound interest over decades—logarithms tell you how many doublings occurred.

When sound intensity increases by a factor of 10, logarithms measure that increase as a single unit on the decibel scale. Logarithms compress exponential growth into linear measurements, which makes them easier to work with and compare.

The key relationships show you how logarithms break down complex expressions:

log_a(xy) = log_a(x) + log_a(y) — Products inside become sums outside

log_a(x/y) = log_a(x) – log_a(y) — Quotients inside become differences outside

log_a(xⁿ) = n·log_a(x) — Powers inside become coefficients outside

Think of it like this: if exponentials ask “where do I end up after this many steps?” then logarithms ask “how many steps did it take to get here?”

They’re two sides of the same operation, just running in opposite directions.

This matters because exponential relationships show up everywhere in engineering—radioactive decay, signal attenuation, population growth, chemical reaction rates.

And when you need to isolate the time variable or the growth rate from an exponential equation, logarithms are the tool that lets you do it. You’re not raising numbers to powers anymore. You’re solving for the power itself.

On the FE Exam, logarithms show up when a problem gives you the result of an exponential process and asks you to work backward to find the exponent, or when you need to simplify a complex logarithmic expression using the product, quotient, or power rules.

You might see them in chemistry, thermodynamics, signal processing, or any context where exponential growth or decay is involved.

The key is recognizing when you’re being asked to invert an exponential relationship, and then applying the right logarithm rule without second-guessing the notation or losing track of the base.

Why Logarithms Feel Messier Than They Should

Logarithms don’t fail because the concept is hard. You already know they’re the inverse of exponents.

The breakdown happens because the notation, the rules, and the base conversions all layer on top of each other, and it’s easy to lose track of what you’re actually solving for.

Here’s what happens in real time:

• You see log₆(3 × 2) and you know there’s a rule for products, but you’re not sure if it becomes log₆(3) + log₆(2) or if you multiply the logs together.
• The problem gives you ln(x) and log(x) in the same expression and you freeze because you’re not sure if “ln” means natural log, if “log” means base 10, or if they’re interchangeable.
• You’re asked to evaluate log₅(125) and you start trying to convert it to base 10 or base e even though you could just recognize that 5³ = 125 and the answer is 3.
• You’re simplifying 3·log₂(x) – log₂(y) and you’re not sure whether to combine them first or deal with the coefficient first, so you guess and hope the algebra works out.
• You apply the power rule and write log_a(x²) = 2·log_a(x), but then you second-guess whether the exponent should be in front or if you wrote it backward.

The real issue is that logarithm rules feel arbitrary if you don’t see the pattern, and the notation makes it easy to confuse which base you’re working with or which rule applies to the structure you’re looking at.

But once you map the structure of the problem to the correct rule, logarithms become straightforward.

You’re not guessing. You’re identifying whether you have a product, quotient, power, or base conversion, and then applying the one rule that matches.

The math doesn’t fight you. The rules are consistent. And the answer follows directly from the setup.

How to Work Through Logarithms Problems

When you see log₃(27) + log₃(9) – log₃(3), you know you can combine them—all three logs have the same base.

But the uncertainty hits when you’re not sure whether to handle addition first or subtraction first, whether the order matters, or if you need to convert to base 10 before doing anything.

Most students either rush through and add the arguments directly (which breaks the rule), or they freeze and try to evaluate each log separately before combining (which works but takes three times as long).

Here’s the workflow that removes the guesswork. It works on any logarithm problem the FE gives you, whether it’s a straightforward evaluation or a multi-step simplification.

Once you’ve practiced this a few times, it becomes automatic—you see the structure, apply the rule, and move on.

Let’s lay out the steps.

Step 1: Identify what you’re working with

The first thing you need to do is read the problem and identify the structure of the logarithm.

Are you evaluating a single log? Simplifying an expression with multiple logs? Solving for an exponent?

Next, identify the base. If you see “log” by itself with no subscript, it’s base 10 (common logarithm). If you see “ln”, it’s base e (natural logarithm).

If you see log with a subscript like log₆, that’s your base.

Then look at what’s inside the logarithm—the argument. Is it a single number? A product? A quotient? A power?

This tells you which rule you’ll need.

Write down what you know: the base, the argument structure, and what the problem is asking for.

This keeps you from jumping straight to calculations and applying the wrong rule.

Step 2: Apply the appropriate logarithm rule

Now that you know the structure, apply the rule that matches.

If the argument is a product (like log_a(x·y)): Use the product rule and split it into a sum: log_a(x) + log_a(y).

If the argument is a quotient (like log_a(x/y)): Use the quotient rule and split it into a difference: log_a(x) – log_a(y).

If the argument is a power (like log_a(xⁿ)): Use the power rule and pull the exponent out front: n·log_a(x).

If you’re combining multiple logs: Work backward. If you’re adding logs with the same base, combine them into a product. If you’re subtracting logs with the same base, combine them into a quotient.

If you see a coefficient in front of a log, move it inside as an exponent.

If you need a numerical answer and the base isn’t 10 or e: Use the change of base formula: log_a(x) = log(x) / log(a) or log_a(x) = ln(x) / ln(a).

This lets you evaluate the logarithm using your calculator’s log or ln function.

Execute the algebra cleanly. Write out each step so you don’t lose track of negative signs or misplace exponents.

Step 3: Evaluate or simplify to the final answer

Now you just finish it.

If you’re solving for a numerical value, plug into your calculator or recognize the relationship directly if the base and argument make it obvious (like log₂(8) = 3 because 2³ = 8).

If you’re simplifying an expression, combine like terms and write it in the cleanest form possible.

If the problem asks for the expression in terms of a specific base, make sure your final answer reflects that.

Compare your result to the answer choices. If your answer doesn’t match any of them, go back and check your rule application and algebra.

Logarithm problems rarely involve complicated calculations—the work is in applying the correct rule and keeping the signs straight.

Example Problem: Logarithms

The workflow handles any logarithm problem by breaking it into a clear sequence: identify the structure, apply the matching rule, and simplify to the answer.

That’s it. No guessing which rule to use, no second-guessing your base conversions, no hoping the algebra works out.

This example walks you through the case where you’ve got multiple logs with the same base connected by addition and subtraction.

You’ll see exactly where to apply the product and quotient rules, how to handle the arithmetic inside without losing track of values, and how to evaluate the final combined log without reaching for a calculator unnecessarily.

With that laid out, let’s put these steps into practice.

This problem states:

Solution: Logarithms

When you see log₃(27) + log₃(9) – log₃(3), the question isn’t whether you can combine them—all three have base 3.

The question is whether you multiply all three arguments together first, or handle the addition and subtraction separately, and whether subtraction means dividing by that argument or subtracting logs first then combining.

That’s where students either rush and add the arguments directly (which breaks the product rule), or they pause and try to evaluate each log separately (which works but burns time you don’t need to spend).

This is exactly why we use the workflow. It removes the guessing and forces you to map structure to rule before calculating anything.

The workflow turns uncertainty into clean execution. Let’s walk it out step by step.

Step 1: Identify what you’re working with

The first thing we need to do is read the expression and identify what we have.

We’ve got three logarithms, all with base 3, and they’re connected by addition and subtraction.

The structure is: log₃(27) + log₃(9) – log₃(3).

All three logs have the same base, which means we can apply the product and quotient rules to combine them into a single logarithm.

The addition tells us we’ll be multiplying arguments. The subtraction tells us we’ll be dividing by the argument of the log being subtracted.

We write this down so we’re clear on what we’re doing:

log₃(27) + log₃(9) – log₃(3)

We know we can combine these using the rules for products and quotients.

Step 2: Apply the appropriate logarithm rule

Now we apply the rules. When we add logarithms with the same base, we multiply their arguments.

When we subtract logarithms with the same base, we divide their arguments.

So log₃(27) + log₃(9) becomes log₃(27 × 9).

Then we subtract log₃(3), which means we divide by 3.

Putting it together:

log₃(27 × 9 / 3)

Let’s calculate the argument:

27 × 9 = 243

243 / 3 = 81

So now we have:

log₃(81)

Step 3: Evaluate or simplify to the final answer

Now we just need to evaluate log₃(81). This is asking: what power do we raise 3 to in order to get 81?

We know that:

3¹ = 3

3² = 9

3³ = 27

3⁴ = 81

So log₃(81) = 4.

The final answer to this problem is D) 4.

This tells us that when we combine the three logarithms using the product and quotient rules, the expression simplifies to log₃(81), which evaluates to 4 because 3⁴ = 81.

Common Mistakes to Avoid on Logarithms Problems

Logarithm problems fall apart the moment you see log₃(27) + log₃(9) and think “addition means add the arguments,” so you write log₃(36) instead of log₃(243).

You applied addition where you should have applied multiplication, and now your entire calculation is working with the wrong number.

The concept isn’t hard—you know logarithms are the inverse of exponentials. But the execution fails when you rush through rule application or second-guess which base you’re working with.

These mistakes are what turn straightforward problems into wrong answers.

Mistake 1: Adding logarithms by adding their arguments

You see log₃(27) + log₃(9) and you think “addition” so you write log₃(27 + 9) = log₃(36) and then you’re stuck trying to evaluate log₃(36), which doesn’t simplify cleanly.

This happens because addition feels intuitive—you see the plus sign and you want to add the numbers inside the logs. But that’s not how the rule works.

When you add logarithms with the same base, you multiply their arguments, not add them. So log₃(27) + log₃(9) becomes log₃(27 × 9) = log₃(243).

This error changes your entire calculation. If you added the arguments, you’re working with the wrong number and your final answer won’t match any of the choices, or it’ll match a distractor designed to catch this exact mistake.

Mistake 2: Forgetting that log by itself means base 10

You see log(100) in a problem and you treat it like it’s asking for a natural log, so you reach for the ln button on your calculator or try to convert it to base e unnecessarily.

This happens because “log” and “ln” both involve logarithms, and if you’re not paying attention to notation, you assume they’re interchangeable or that you need to convert everything to natural logs to solve it.

But “log” without a subscript means base 10. So log(100) is asking: what power do you raise 10 to in order to get 100?

The answer is 2, because 10² = 100.

If you convert it to natural log, you’re adding steps that don’t help. You’d calculate ln(100) / ln(10) and get 2 anyway, but you’ve wasted time and introduced more opportunities for calculator errors.

Mistake 3: Misapplying the power rule by putting the exponent in the wrong place

You see log₂(x³) and you write 3·log₂(x), which is correct.

But then you see 3·log₂(x) in a different problem and you try to move the 3 back inside as an exponent, but you write log₂(3x) instead of log₂(x³).

This happens because the power rule works both directions—you can pull an exponent out or push a coefficient in—but you lose track of whether the number is multiplying the variable or being applied as a power.

When you pull an exponent out, it becomes a coefficient: log₂(x³) = 3·log₂(x).

When you push a coefficient in, it becomes an exponent on the argument: 3·log₂(x) = log₂(x³).

If you write log₂(3x) instead of log₂(x³), you’ve changed the argument completely.

Now you’re taking the log of 3x instead of x³, and those aren’t equivalent.

Mistake 4: Trying to evaluate logarithms without recognizing powers of the base

You see log₅(125) and you immediately reach for the change of base formula: log₅(125) = log(125) / log(5), then punch it into your calculator.

This works, and you’ll get the right answer. But it’s slower than necessary, and it opens the door to calculator errors or rounding issues.

The faster way is to recognize that 125 is a power of 5. You know 5¹ = 5, 5² = 25, 5³ = 125.

So log₅(125) = 3 because 5³ = 125.

If you don’t check for this first, you miss the shortcut. And on the FE, where time is limited, recognizing common powers (2, 3, 4, 5, 10) can save you 20-30 seconds per problem.

Quick Checks for Logarithms Problems

The workflow maps structure to rule—product to multiplication, quotient to division, power to coefficient.

You know how to combine logs with the same base and how to break apart complex arguments using the three core rules.

These checkpoints keep you from misapplying rules or losing track of bases when answer choices are tight and you’re moving fast.

• Check the base notation first, every time: Before you apply any rule, confirm whether you’re working with common log (base 10), natural log (base e), or a specified base like log₃. If you see “log” with no subscript, it’s base 10. If you see “ln”, it’s base e. This prevents you from converting unnecessarily or using the wrong base in your calculations.
• When you see logs being added, multiply their arguments: If you see log_a(x) + log_a(y), combine them into log_a(x·y). The addition outside means multiplication inside. Don’t add the arguments—that’s not how the rule works. Write out the combined form first, then calculate the product separately.
• When you see logs being subtracted, divide their arguments: If you see log_a(x) – log_a(y), combine them into log_a(x/y). The subtraction outside means division inside. This rule is consistent with the product rule—the operation outside determines the operation inside.
• When you see a coefficient in front of a log, it’s an exponent inside: If you see n·log_a(x), it can be rewritten as log_a(xⁿ). The coefficient moves inside as a power. It doesn’t multiply the argument—it becomes an exponent. Write it out explicitly to avoid confusing multiplication with exponentiation.
• Before you reach for the change of base formula, check if the argument is a power of the base: If you see log₅(125), ask yourself: Is 125 a power of 5? (Yes, 5³ = 125.) So log₅(125) = 3. You don’t need to convert to base 10 or base e unless the argument doesn’t simplify cleanly. Recognizing common powers saves time and reduces calculator errors.
• Logarithms of 1 always equal 0, logarithms of the base always equal 1: No matter what base you’re working with, log_a(1) = 0 because any number raised to the power of 0 equals 1. And log_a(a) = 1 because any number raised to the power of 1 equals itself. These identities show up in simplifications and can shortcut multi-step problems if you spot them early.

You’ve got the structure now. You know which rule applies when, and you know how to move between expanded and condensed forms without second-guessing yourself.

These checkpoints just make sure you don’t lose points to execution errors when the clock is running.

Final Thoughts | Logarithms

Logarithms fail on the FE at the exact moment you see three logs connected by addition and subtraction and you’re not sure if you handle them all at once or one at a time.

Not because you don’t know what a logarithm is—you learned that in high school.

Because you’re trying to remember which rule applies to which structure while the clock is running and the answer choices are all within one unit of each other.

That hesitation costs you time you can’t get back. You read log₃(27) + log₃(9) – log₃(3), and instead of executing immediately, you pause.

Should I add first? Subtract first? Combine them all together? Convert to base 10?

And while you’re deciding, 45 seconds burns off the clock.

The workflow removes that pause. You see addition and subtraction connecting logs with the same base, and you know instantly: combine into a single log, multiply for addition, divide for subtraction.

No decision tree. No hoping you remember correctly. You map structure to rule, execute the algebra, and compare to answer choices.

The concept isn’t what makes these problems hard. What makes them hard is having five different rules (product, quotient, power, base 10, base e) and needing to select the right one in under ten seconds while holding the intermediate arithmetic in your head.

The workflow handles that selection for you. It turns every logarithm problem into the same process: identify structure, apply matching rule, simplify.

Looking to build more confidence across every FE topic? Explore our full library of practice problems and step-by-step guides here.

Here’s what’s draining your prep time right now. You’re three weeks out. You’ve done hundreds of practice problems, but you still don’t know if you’re practicing the right things.

Every night you study, you finish the session wondering: did that actually move me closer to passing, or did I just stay busy?

And that uncertainty—not knowing if your effort is building real readiness or just burning hours—keeps you stuck in the same loop.

That’s the gap Prepineer closes. You get a personalized roadmap that tells you exactly what to study and when.

You get targeted practice on the topics the FE actually tests, not random problems from a generic bank. You get real coaching when you’re stuck, not just answer keys.

And you can see your progress tracking toward exam day, so you’re not hoping you’re ready—you know you’re ready.

If you’re tired of scattered prep and you want a clear plan that builds confidence instead of anxiety, start your free 7-day trial and see what structured study feels like.