How Logarithms Turned Multiplication into Addition for Astronomers

In the previous article, trigonometry turned angles into reusable numerical relationships.

That solved one problem and exposed another.

Astronomers could build mathematical models of the sky, but using those models again and again could require long chains of multiplication, division, and table lookup.

A correct equation is not automatically a cheap calculation.

So a new question appeared:

Can we make the calculation easier without changing the astronomical model?

Logarithms showed that the answer could be yes.

Quick Answer

A logarithm gives us a different numerical representation of the same positive quantity. On that new scale, multiplication can be handled by addition, and division by subtraction.

With a printed logarithm table, the workflow could become:

numbers → logarithms → add or subtract → inverse lookup → answer

The astronomical model did not become simpler. The cost of using it became smaller.

hard operation → better representation → easier operation → same mathematical result

The New Bottleneck Was Arithmetic

Trigonometric tables made angular relationships reusable. But a practical astronomical prediction could still require many products and quotients.

Do that once and the work may be manageable. Do it for many stars, planets, dates, or observations and arithmetic itself becomes a bottleneck.

This is a computational idea that still matters:

a mathematically correct method can still be too expensive to use repeatedly

The problem is no longer only, “Is the equation right?” It is also, “How much work does one use of the equation require?”

Four-step diagram showing multiplication or division, logarithm lookup, addition or subtraction, and inverse lookup

Figure 1. Logarithms change the representation of a calculation so that a difficult operation can be replaced by an easier one.

First See the Pattern, Then Name the Logarithm

Before defining logarithms formally, look at a familiar pattern:

10² × 10³ = 10⁵

The numbers multiply, but the exponents add:

2 + 3 = 5

Modern logarithms generalize this relationship. If we write:

log(ab) = log(a) + log(b)

then a product can be handled as a sum after the numbers have been moved to logarithmic form.

Likewise:

log(a/b) = log(a) − log(b)

This modern notation is an excellent mental model. But it is not how John Napier originally thought about logarithms.

Napier Was Solving a Calculation Problem, Not Teaching Inverse Exponents

John Napier published Mirifici Logarithmorum Canonis Descriptio in 1614. His stated concern was the difficulty, time, and error involved in repeated multiplication, division, and root extraction.[1][2]

His original logarithms were not simply the modern base-10 or natural logarithms taught in textbooks. Napier developed them through a geometric idea involving changing motion, and his published tables were closely tied to trigonometric quantities such as sines.[1]

That historical detail corrects an easy misconception:

Logarithms were useful as a calculating technology before they were taught as “the inverse of exponentiation.”

A page from John Napier's 1614 Mirifici Logarithmorum Canonis Descriptio showing angles, sine values, and logarithmic table entries

Figure 2. A page from Napier's 1614 logarithm tables. The printed page stores numerical work so later users can retrieve values instead of rebuilding them from scratch. Public domain.[3]

Try It — Multiply by Looking Up and Adding

Use modern base-10 logarithms to imitate the old table workflow.

Suppose we want to calculate 37 × 52.

A four-decimal logarithm table gives approximately:

log₁₀(37) ≈ 1.5682

log₁₀(52) ≈ 1.7160

Add them:

1.5682 + 1.7160 = 3.2842

Now use an inverse lookup: 103.2842 ≈ 1924.

And indeed:

37 × 52 = 1924

The point is not that logarithms magically remove all work. Someone had to calculate the table accurately, and the user still had to look up and interpolate values carefully.

The important change is where the difficult work happens.

A Table Is Computation Paid for in Advance

A numerical table contains results that someone has already worked out.

Once printed, that effort can be reused by thousands of later calculations:

compute once → store → retrieve → reuse

That makes a logarithm table more than a reference book. It is a piece of precomputed mathematics.

Four-step diagram showing values being computed, printed in tables, carried to users, and reused by lookup

Figure 3. Precomputation moves difficult work earlier so many later users can perform cheaper calculations.

One Idea Became a Calculation Technology

Napier was not the only person developing logarithmic methods.

Jost Bürgi developed an independent system and published it in 1620, although evidence indicates that his work began earlier.[5]

Henry Briggs, meanwhile, recognized the value of Napier's work and helped develop the more convenient common-logarithm system associated with base 10. He published an early table in 1617 and the much larger Arithmetica Logarithmica in 1624.[4]

The useful historical picture is therefore not “one formula suddenly appeared.” It is:

idea → improved representation → accurate tables → widespread calculation

Kepler Saw the Payoff for Astronomy

Johannes Kepler encountered Napier's logarithms soon after their publication and recognized their value for astronomical calculation.[6]

In the Rudolphine Tables, published in 1627, logarithmic tabulations helped reduce the work required to calculate planetary positions from Kepler's astronomical model and Tycho Brahe's precise observational data.[7]

This gives us a useful systems view:

better data + better model + cheaper computation → better practical prediction

Timeline from Napier in 1614 through Briggs, Bürgi, Kepler, and the Rudolphine Tables in 1627

Figure 4. Logarithms moved quickly from a new mathematical method into the working tools of seventeenth-century astronomy.

The Same Trick Still Appears in Computing

Modern computers no longer need printed logarithm tables for ordinary multiplication.

But the deeper strategy survives: change the representation so the computation becomes easier or more stable.

Probability and machine-learning software often works with logarithms of very small probabilities. Products then become sums, and log-space calculations can avoid numerical underflow that would otherwise turn extremely small values into zero in floating-point arithmetic.[8]

So the old astronomy story points toward a much broader computational habit:

do not only ask how to solve the problem — ask whether another representation makes the problem cheaper

Try It in Python

import math

a = 37
b = 52

log_product = math.log10(a) + math.log10(b)
recovered_product = 10 ** log_product

print(log_product)
print(recovered_product)

The recovered value is approximately 1924. A computer performs the operations differently from a seventeenth-century table user, but the relationship is the same.

Words to Keep

Logarithm — a numerical representation that converts multiplication into addition under the logarithm rule.

Logarithm table — precomputed logarithmic values that let users replace repeated hard arithmetic with lookup and simpler operations.

Inverse lookup / antilogarithm — the step that converts a logarithmic result back to the original number scale.

Representation — the form in which a mathematical problem is expressed; changing it can change computational cost without changing the underlying problem.

One Sentence to Keep

Logarithms sped up astronomy by moving repeated hard arithmetic into a new representation where tables and addition could do much of the work.

What Should We Ask Next?

Faster arithmetic can make a model practical.

But fast calculation cannot rescue poor observations.

Kepler's later predictions depended on an extraordinary observational record assembled before logarithms became widespread.

So we now step back one generation and ask where that data came from:

Next question: How Did Tycho Brahe Turn the Sky into Data?

Previous: Why Astronomy Needed Trigonometry to Predict the Sky

Chapter bridge: How Sailors Carried a Predicted Sky Across the Ocean

Sources & Further Reading

  1. MacTutor History of Mathematics, “John Napier” — Napier's motivation, original construction, and why his logarithms were not modern textbook logarithms.
  2. Royal Society, “Counting bones” — Napier's effort to replace difficult arithmetic with simpler operations and practical applications such as navigation.
  3. Wikimedia Commons, page from Mirifici Logarithmorum Canonis Descriptio — 1614 table page; public domain. See also the University of Oklahoma digitized exhibit.
  4. MacTutor History of Mathematics, “Henry Briggs” — Briggs's role in developing and publishing common-logarithm tables.
  5. MacTutor History of Mathematics, “Jost Bürgi” — independent development and 1620 publication of Bürgi's logarithmic system.
  6. MacTutor History of Mathematics, “Johannes Kepler” — Kepler's reception and use of logarithms in astronomical calculation.
  7. University of Cambridge, “Kepler and Astronomical Tables” — logarithmic tabulations in the Rudolphine Tables and calculation of planetary positions.
  8. SciPy documentation, log probability calculations — modern use of log-space calculations to avoid floating-point underflow.

Historical note: equations such as log(ab) = log(a) + log(b) are used here as the modern conceptual model. Napier's original system was constructed differently and should not be retroactively described as ordinary base-10 or natural logarithms.