← Back to blog

Does a lifting log show weight per dumbbell or total weight?

By Mr.Apps · Oct 6, 2026

Category:Wearable

Man stands beside two separate dumbbells in a bright home strength studio beneath the title.

A number needs a load convention

When a lifting log shows one weight for a pair of dumbbells, the reader needs to know what that number represents. It may be the weight of each dumbbell, the combined weight in both hands, or a machine or cable setting that is not the same as either one. Those values describe different quantities. A chart that drops the convention can make a person's training appear to double or halve even when the workout did not change.

I look for a clear label before comparing entries. “Per dumbbell” means the displayed load applies to each implement. “Combined load” means the value adds the loads being used at the same time. “Per side” can describe a unilateral movement or a machine stack, so the app should explain what side means for that exercise. If the interface does not say, check the exercise details or help page rather than assuming that one convention is universal.

For example, a two-arm dumbbell press can be recorded by the load of each dumbbell or by the combined external load. Either convention can support a consistent log if it is labeled and used the same way. The distinction becomes important when the app totals volume, compares a new session with an older entry, or imports data from another platform. Research reports training volume in different ways, including sets, repetitions, load, and total volume load. A review of volume-matched resistance training defines volume load using sets, repetitions, and weight, which makes the underlying counting convention part of the calculation.

Two per-dumbbell values connect to a combined load representation.

Per implement and combined load

The simplest case is a pair of equal dumbbells held at the same time. If each dumbbell has the same marked load, the combined external load is the sum of the two. That arithmetic describes equipment in the hands; it does not say that the movement is mechanically identical to a barbell lift with the same displayed total. The stability demands, range of motion, grip, and the path of each implement may differ.

An app should not force one representation to stand in for another. A good form could store the load per implement and also show a combined total as a derived display. The source value remains clear, and the interface can explain how the summary was calculated. If a user enters a total only, the form should say so before it is saved. It should not silently interpret a total as the weight of each side.

For one-arm exercises, “per dumbbell” may be obvious but still incomplete. A single-arm row with one dumbbell has one active implement at a time. If a person completes the same set on both sides, a session total might count the load for each side's work, while the set-level entry still records one implement. These are different summaries. The log should identify whether it counts each side as its own set, combines both sides into one set, or calculates total volume across the whole session.

This is not just formatting. In a small study comparing unilateral and bilateral leg extension sessions, the researchers defined total volume using repetitions and load lifted per repetition. Their method treated both limbs within the unilateral session as part of the total session work. The study of unilateral and bilateral exercise shows why a log must specify which unit it is counting before it compares totals.

Dumbbells, barbells, and machines are not interchangeable fields

A barbells' load is usually entered as the total load on the bar, including the bar itself if the system's instructions say to include it. Dumbbell entries often use a per-dumbbell convention. A cable station might show the selected stack value, even though pulley geometry and machine design affect the force felt through the handle. A guided-bar machine can also move differently from a free bar. The number printed on a pin or plate tells the user what setting was selected; it does not by itself establish that two machines produce the same resistance at the hand.

Studies of resistance exercise account for the exact equipment and movement when measuring load and performance. For example, researchers comparing load-velocity patterns across a weight-stack press and a guided-bar press found that the exercise mode affected the relationship they measured. The machine-variation study supports keeping the mode beside the value rather than pooling all press records under one unlabeled “weight” field.

Even two movements that use the same device can have different repetition patterns at the same relative intensity. The number of repetitions a person can complete depends on the exercise and the load. A meta-regression on repetitions at percentages of 1RM found exercise-specific differences in the available evidence. A total-load field cannot correct for a change from one exercise to another; the log needs to preserve the exercise name and variation.

The goal is not to make every movement comparable on one scale. It is to retain enough information that a reader knows what a value describes. The reporting guidance for resistance-training variables discusses why load and repetition count alone may not fully describe a protocol. Exercise, execution, range, equipment, and other variables can change the meaning of a recorded set.

Left and right dumbbell entries distinguish per-hand from combined load.

How to check a confusing entry

Start with the exercise name and the equipment. Confirm whether the movement used one dumbbell, a pair, a barbell, a cable stack, or a guided machine. Then open the load field's label or help text and look for “per dumbbell,” “total,” or “per side.” If the screen has no explanation, do not infer the convention from the size of the number. Ask the service or check its published logging instructions.

Next, inspect a known entry. If you remember the marked load of the dumbbells used, compare that with what the record displays. For a pair, check whether the stored value matches one implement or their combined load. For a one-arm movement, see whether left and right sides are separate records or grouped in one exercise set. Avoid changing historical entries until you understand the app's rule; an edit could recalculate volume or alter a strength trend.

Imported workouts deserve extra care. A source system may use per-hand values while a destination system expects combined load, or may attach the same number to different equipment. A conversion can preserve a number while changing what it means. An import review should show the original value, the destination convention, and any conversion applied. If the source convention is unknown, label it as unknown rather than choosing one without evidence.

A training volume calculation can be useful for a consistent set of entries, but it is not a full measure of training quality or effort. The load, repetitions, range, tempo, assistance, and rest structure may all matter for the question being asked. A systematic review of exercise reporting encourages precise descriptions so protocols can be compared with care. The load and volume reporting review also summarizes how resistance-training load is studied across different protocols; it does not imply that an app's single total captures every feature of a session.

The same caution applies when a chart suggests adding weight. First confirm that the displayed number represents the same quantity as the last session. Then review whether the exercise, equipment, range, and repetitions remained comparable. If those details changed, the chart may be showing a different task rather than a straightforward increase in performance. A practical review of training-plan changes covers how to inspect the evidence behind a proposed adjustment before using a trend to alter a routine.

Where possible, keep the original entry beside any normalized summary. That lets a reader see whether a total was calculated from one or two implements and whether a conversion was made during import. A correction should update the stated convention and retain an audit trail, rather than silently rewriting the earlier value.

When two values must be compared, make the convention explicit first. Keep the unit, implement count, side, and equipment consistent. If one entry says per dumbbell and another says combined load, convert only when the inputs are clear and the conversion is appropriate. If a machine or exercise changed, compare those records as separate movement histories unless there is a validated way to relate them.

Exercise, load basis, repetitions, and side remain separate fields in a lifting log.

FAQ

Should a pair of dumbbells be logged as one weight or two?

Follow the app's stated convention. It may store the weight of each dumbbell and calculate a combined display, or it may ask for the total. The log should label which value it stores so a later chart does not mix conventions.

Is combined dumbbell load the same as a barbell load?

The arithmetic total may be the same, but the exercises can differ in stability, movement path, grip, and range. Keep the equipment and exercise variation with the entry. A matching number alone does not show that the training tasks were equivalent.

How should a one-arm exercise be counted?

Record the load and repetitions for the working side, then follow the app's rule for whether the other side is a separate set or part of a combined session total. The rule should remain consistent and visible in summaries.

*This article is for informational purposes only and is not a substitute for professional medical advice, diagnosis or treatment.*

Related articles

What an app should explain before increasing a planned lifting load

What an app should explain before increasing a planned lifting load

A heavier planned lifting load needs an explanation tied to completed sets, a visible progression rule, and any missing evidence. Learn what to check before accepting, adjusting, or keeping the next target.

How equipment constraints should shape a generated workout plan

How equipment constraints should shape a generated workout plan

A generated workout is useful only when its exercises fit the equipment you can actually use. Learn how to list constraints, review substitutions, and check the whole session before saving a plan.

Why compound exercise sets can appear under several muscle groups

Why compound exercise sets can appear under several muscle groups

A compound exercise set is performed once but may be attributed to several muscle-group charts. Learn how to trace the original set, check the app's credit rule, and avoid adding overlapping views together.

Checking which planned session an automatic workout match completed

Checking which planned session an automatic workout match completed

Automatic matching can confuse similar planned workouts. Compare how a session was started, its timing, and its recorded details before treating a plan as completed.

Why skipped workouts should remain visible in a training calendar

Why skipped workouts should remain visible in a training calendar

A skipped workout is useful calendar information, not a judgment about effort. Keeping it visible helps separate completed work from the sessions a plan originally intended.

Keeping a reusable workout routine separate from its session history

Keeping a reusable workout routine separate from its session history

A reusable routine describes a session that can be started again, while workout history records what happened on specific days. Keeping the two linked but separate makes later edits easier to understand without rewriting past sessions.

A training program needs more than a collection of workouts

A training program needs more than a collection of workouts

A list of workouts does not explain how sessions connect or what should change over time. Learn which goal, sequence, progression, and review rules make a training program coherent.

How to reschedule a missed workout without crowding the week

How to reschedule a missed workout without crowding the week

A missed workout does not have to become a debt that crowds the rest of the week. Review spacing, session order, and available time before choosing whether to move, shorten, or skip it.

Separating planned workouts from completed training load

Separating planned workouts from completed training load

Planned workouts describe intent, while completed records describe work that actually happened. Keeping both views separate makes weekly training load easier to interpret and future schedules easier to review.

Why a Health App Should Label Which Features Work Offline

Why a Health App Should Label Which Features Work Offline

A health app may keep local measurements and history available while search, cloud analysis, recommendations, or sharing need an internet connection. Clear feature-by-feature labels should show what works now, what is waiting to sync, and what data or permissions are required.