Resistor calculator
| Wanted | Pair | Actual | Error |
|---|---|---|---|
| 500 Ω | 1 kΩ ∥ 1 kΩ | 500 Ω | exact |
| 750 Ω | 1 kΩ ∥ 3.3 kΩ | 767 Ω | +2.2% |
| 1.5 kΩ | 2.2 kΩ ∥ 4.7 kΩ | 1.50 kΩ | +0.0% |
| 2 kΩ | 3.3 kΩ ∥ 5.6 kΩ | 2.08 kΩ | +3.8% |
| 5 kΩ | 10 kΩ ∥ 10 kΩ | 5 kΩ | exact |
| 8 kΩ | 10 kΩ ∥ 39 kΩ | 7.96 kΩ | −0.5% |
| 15 kΩ | 22 kΩ ∥ 47 kΩ | 15.0 kΩ | +0.0% |
Two LEDs in parallel behind a single resistor do not share current evenly. Forward voltage varies between parts by a tenth of a volt or so, and because the current-voltage curve is exponential, the one with the slightly lower Vf takes most of the current, runs hotter, drops further, and takes more still. Give each LED its own resistor, or drive the string in series where the same current necessarily flows through all of them.
Gives the equivalent resistance of a network of resistors, and sizes the ones a circuit needs. Series values add; parallel is a reciprocal sum, so two 1 kΩ resistors give 500 Ω and a third gives 333 Ω. It also sizes an LED resistor with its wattage, splits a current between branches, and puts a pull-up between the sink and rise-time limits.
How to use it
Two rules cover most of this page and they run in opposite directions. Series values add, so a chain is arithmetic and nothing more: the same current flows through every part and the voltage divides in proportion. Parallel is a reciprocal sum, so the total is always smaller than the smallest member, and a result larger than that is proof the arithmetic went wrong somewhere. For two parts the shortcut R₁R₂ ÷ (R₁ + R₂) is quicker by hand, and for equal parts the answer is simply the value over the count.
Which part gets hot
Neither rule tells you where the heat goes, and that is the specification people forget to check. In series it is the largest resistor, because it drops the most voltage at a shared current. In parallel it is the smallest, because it carries the most current at a shared voltage. Mixing wattages across a set is fine as long as each part is rated for what it will actually dissipate, which is not an equal share.
Pairing does nothing for tolerance either. Two 5% parts in parallel still give roughly 5% uncertainty, so a pair is a way to reach a value, not a way to tighten one: 2.2 kΩ alongside 4.7 kΩ gives 1.499 kΩ, closer to 1.5 kΩ than a 5% part is guaranteed to be, and still only as precise as the two parts you used. A long series chain behaves better than intuition suggests, because random errors partly cancel: a ten-resistor ladder of 5% parts totals closer than 5% off, even though any single tap can still be out by the full amount. That ladder shows up in real silicon. A string of equal resistors tapped at each junction is exactly how a flash ADC and a simple resistor DAC produce their references.
Dropping a voltage, and driving an LED
A series resistor is the standard way to drop voltage or limit current, and the value follows from Ohm’s law on the difference: a 5 V supply feeding something that wants 3.3 V at 20 mA needs to lose 1.7 V at 20 mA, which is 85 Ω. The catch is that the drop depends on the current, so if the load changes, the voltage moves with it. That makes a series dropper right for an LED, whose current you set deliberately, and wrong for a circuit whose consumption varies.
Forward voltage is the number people guess at and should not. It follows the band gap of the semiconductor, so red and yellow sit around 1.8 to 2.1 V, green nearer 2.2, and blue and white at 3.0 to 3.4. Use a red figure for a white LED on a 3.3 V rail and there is no headroom left; the calculator flags that case instead of printing a nonsense resistor value. Rounding matters in one direction only: pick the resistor above the calculated value, because too much resistance dims an LED and too little shortens its life.
The current divider looks like the voltage divider with the labels swapped, and that swap is where the mistakes happen. In a voltage divider the output uses the resistor it is measured across; in a current divider the branch current uses the opposite resistor on top. The physical reading is easier to hold on to: current takes the easier path, so the smaller resistance carries more. Its most common real use is a shunt, a known low resistance in parallel with a meter so a known fraction of the current bypasses it.
Pull-ups and pull-downs
The pull-up is the only variant here with two limits instead of a formula, and it is a squeeze between two different failures. Too weak and the line rises too slowly, so the receiver samples a level that has not arrived, which shows up as intermittent errors that get worse as devices are added or wires get longer. Too strong and the open-drain driver cannot pull the line low enough to read as a zero, which fails hard and immediately. The floor is the sink current of the weakest device on the bus, which I²C guarantees at 3 mA; the ceiling is rise time into the bus capacitance. The window between them narrows as speed rises and capacitance grows, which is why a long I²C bus with many devices is genuinely difficult and why active bus buffers exist at all.
A pull-down is not simply an inverted pull-up, because most digital inputs are not symmetric. A CMOS input leaks only nanoamps, so a very high value would work on paper, until board contamination, humidity and nearby switching noise couple into what is now a high-impedance node. Ten kilohms is the customary compromise: low enough to shrug off leakage and coupling, high enough that the current wasted while the line is driven high stays negligible. In a low-power design it is worth calculating properly, because a permanently driven pull-down can easily outrun the sleep current of the microcontroller it is attached to.
What people use it for
- Choosing the series resistor an LED needs, and the wattage it must be
- Adding a chain of resistors to reach a value you do not stock
- Building a voltage ladder or a reference string
- Combining a whole set of resistors in parallel
- Hitting a value between E12 steps with a parallel pair
- Working out how a current splits between two parallel branches
- Choosing an I²C pull-up between the sink limit and the rise-time limit
- Holding a MOSFET gate or a button input at a defined level with a pull-down
- Sizing a shunt so a meter reads over the range you want
- Driving an LED from a microcontroller pin without going past the pin current limit
- Checking that a circuit already built is not overdriving its LED
- Making a load bank from several resistors in parallel
- Spreading dissipation across several parts rather than one that runs hot
- Dropping a voltage for a load that draws a fixed current
- Limiting inrush into a capacitor with a series resistor
- Debugging an I²C bus that stopped behaving when it got longer or faster
- Budgeting the quiescent current a pull-down adds to a battery-powered design
Questions
1/R_total = 1/R₁ + 1/R₂ + … For two resistors, R = R₁R₂ ÷ (R₁ + R₂). For equal resistors it is simply the value over the count, so ten 1 kΩ parts give 100 Ω.
R_total = R₁ + R₂ + R₃ + … Nothing more complicated than addition.
Each extra path gives current somewhere else to go, so the overall opposition falls.
Substitution by parallel pair: 2.2 kΩ alongside 4.7 kΩ gives 1.499 kΩ, closer than a 5% 1.5 kΩ part is guaranteed to be.
Not on its own. Two 5% parts still give roughly 5% uncertainty. It helps you reach a value, not tighten a tolerance.
In parallel the smallest, because it carries the most current. In series the largest, because it drops the most voltage. Mixing wattages across a set is fine; size each part for what it will actually dissipate, which is not an equal share.
Not fully. Random errors partly cancel, so a ten-resistor ladder of 5% parts totals closer than 5% off, though any single tap can still be out by the full amount.
For a 2 V red LED at 20 mA, 150 Ω, which is an E24 value already. For a 3.2 V white LED at 20 mA, 90 Ω, and the nearest E24 part at or above it is 91 Ω. Rounding up rather than to the nearest is deliberate: a slightly larger resistor dims the LED, a smaller one shortens its life.
Usually far less than a quarter watt: 150 Ω at 20 mA dissipates 60 mW. The rating still matters, so read the power figure and pick a part comfortably above it.
The voltage it drops when conducting: about 1.8–2.1 V for red, 2.2 for green, 3.0–3.4 for blue and white.
In series yes, in parallel no. Parallel LEDs do not share current, and one ends up carrying most of it.
Up. A larger resistor dims the LED slightly; a smaller one overdrives it and shortens its life.
I₁ = I_total × R2 ÷ (R1 + R2), taught as the current division rule. The opposite resistor appears on top, which is the part people misremember.
Both branches see the same voltage, and current is voltage over resistance, so lower resistance means higher current.
Written I2C as often as I²C, and either way 4.7 kΩ is the usual default for 100 kHz. At 400 kHz the specification allows only 300 ns of rise instead of 1,000, which puts the ceiling near 3.5 kΩ at 100 pF, so fast mode wants 2.2 kΩ or lower.
The floor is the sink current of the weakest device; I²C guarantees 3 mA, so 3.3 V over 3 mA is 1.1 kΩ. The ceiling is the rise time the bus speed allows, charging the bus capacitance: 1,000 ns in standard mode, 300 in fast mode, 120 in fast mode plus.
10 kΩ suits most logic. Lower in a noisy environment, higher only in a design where the wasted current genuinely matters, and above about 1 MΩ leakage and coupled noise start to matter more than the resistor does.
Vcc divided by the resistance, whenever the line is driven high. 10 kΩ on 3.3 V is 0.33 mA, which is negligible next to a running microcontroller and enormous next to a sleeping one.
Whichever gives the safe default state when nothing is driving the line. For an active-high enable, a pull-down keeps it off.
Yes, if nothing else defines the gate. A floating gate can turn the device partly on, which is how MOSFETs get destroyed by nothing in particular.