Skip to content
RFrftools.io
Unit ConversionMarch 20, 20265 min read

Decoding 3-Digit Capacitor Codes: Practical Guide

Learn how to decode 3-digit capacitor codes into pF, nF, and µF values. Worked examples, the math behind the system, and a free online calculator.

Contents

Why Capacitor Codes Still Matter

You know that moment when you're elbow-deep in a parts bin and pull out a ceramic capacitor with nothing but "104" stamped on it? Yeah, those three digits aren't just random markings — they're actually telling you exactly what capacitance you're holding. Modern parametric search tools are fantastic when you're ordering fresh parts, but they don't help much when you're reverse-engineering a 20-year-old board or trying to figure out if that mystery cap from your junk drawer is the 100 nF bypass you need.

The reality is, these codes show up everywhere. Walk into any electronics lab, crack open any consumer device, or dig through any hobbyist's component stash, and you'll find hundreds of capacitors marked this way. Learning to read them quickly saves you time and prevents that frustrating moment where you solder in the wrong value and spend an hour debugging why your circuit isn't working.

The Encoding Scheme

The system is actually pretty elegant once you understand it — think of it like resistor color codes, but simpler because you're just reading numbers instead of memorizing a rainbow. Everything is expressed in picofarads (pF), which makes sense because ceramic caps typically range from a few pF up to several µF, and pF gives you a nice integer representation across that whole span.

Here's how it breaks down:

  • The first two digits give you the significant figures
  • The third digit is your multiplier — specifically, the power of 10 you multiply by
Mathematically, it's just:
CpF=(first two digits)×10third digitC_{\text{pF}} = (\text{first two digits}) \times 10^{\text{third digit}}

Let's decode 104 as an example, since it's probably the most common code you'll encounter:

C=10×104=100,000 pF=100 nF=0.1μFC = 10 \times 10^4 = 100{,}000 \text{ pF} = 100 \text{ nF} = 0.1 \,\mu\text{F}

If you've ever grabbed what you thought was a "point one microfarad" cap based on seeing 104 printed on it, congratulations — you were using this system correctly even if you didn't know the formal rules. Most engineers learn this through osmosis after seeing it enough times, but understanding the actual logic makes you faster and more confident.

The beauty of this scheme is that it's compact. You can print three tiny digits on a component barely bigger than a grain of rice, and that's enough to fully specify the capacitance. Compare that to trying to print "0.1µF" on something that small — the decimal point alone would be nearly invisible.

Quick Reference Table

These are the codes you'll run into constantly. I've kept this table on my phone for years because even though I know the system, it's faster to glance at a reference than do the mental math when you're in a hurry:

CodeCalculationpFnFµF
10010×10010 \times 10^0100.01
10110×10110 \times 10^11000.1
10210×10210 \times 10^21,00010.001
10310×10310 \times 10^310,000100.01
10410×10410 \times 10^4100,0001000.1
10510×10510 \times 10^51,000,0001,0001
22422×10422 \times 10^4220,0002200.22
47347×10347 \times 10^347,000470.047
Here's a mental shortcut that works surprisingly well: that third digit basically tells you how many zeros to tack onto the end of the first two digits. So 473 translates to "47 followed by 3 zeros," which gives you 47,000 pF. It's not mathematically rigorous, but it's fast and it works for probably 95% of the codes you'll see in the field.

The E-series values (10, 22, 47, etc.) show up constantly because they're the standard preferred numbers used across the industry. You'll see 104, 224, and 474 way more often than oddball values like 127 or 393, though those exist too.

Worked Example: Identifying a Bypass Cap on a Legacy Board

Let's say you're troubleshooting an old industrial control board — the kind where the silkscreen has worn off and the schematic got lost sometime in the 1990s. You spot a ceramic capacitor sitting between the VCC rail and ground near an IC, and it's marked 224. Time to figure out what you're working with.

Step 1: Pull out the significant figures: 22 Step 2: Identify the multiplier: 4, which means we're multiplying by 104=10,00010^4 = 10{,}000 Step 3: Do the calculation:
C=22×104=220,000 pFC = 22 \times 10^4 = 220{,}000 \text{ pF}
Step 4: Convert to more practical units:
C=220 nF=0.22μFC = 220 \text{ nF} = 0.22 \,\mu\text{F}

That's a textbook 220 nF bypass capacitor, exactly what you'd expect to see decoupling a 5 V logic rail. The value makes sense — big enough to handle moderate frequency noise, small enough that its ESR and ESL don't cause problems, and a standard E-series value that's been common for decades.

If you want to double-check your work or you're dealing with a more unusual code, the Capacitor Code Decoder will give you instant confirmation. I still use it when I'm tired or dealing with unfamiliar tolerance/voltage markings.

Edge Cases and Gotchas

Codes Below 100

Things get a little weird with very small capacitors. When you see something like 100 or 010, you're not using the multiplier system anymore — you're just reading the value directly in picofarads. A marking of 010 means 1 pF, not "01 times 10 to the zero." This makes sense when you think about it: these tiny values are already at the bottom of the range, so there's no need for a multiplier scheme.

I've seen this trip up people who try to apply the formula blindly. If you get a result that seems absurdly small or doesn't make sense for the circuit you're looking at, check if you're dealing with one of these direct-value codes.

Codes with 8 or 9 as the Multiplier

Every once in a while — usually in RF or precision analog work — you'll encounter a third digit of 8 or 9. These indicate negative powers of ten. A code like 158 could mean 15×102=0.1515 \times 10^{-2} = 0.15 pF. Yeah, that's a real thing, though you'll mostly see it in specialized applications like VCO tuning or impedance matching networks where you need fractional picofarad precision.

Most engineers go their whole careers without running into this, but if you work with RF circuits above a few GHz or do precision oscillator design, you'll eventually meet these oddball codes. The decoder tool handles them correctly, which is good because I've never bothered memorizing the exact convention.

Voltage and Tolerance Codes

The three-digit capacitance code is just the beginning. Many capacitors have additional letter codes that specify tolerance and voltage rating. A J suffix typically means ±5% tolerance, K means ±10%, and M means ±20%. For voltage, you might see something like 1H indicating 50 V rated.

These extra markings follow their own standards (often EIA or IEC), and honestly, they're harder to remember than the basic capacitance code. When I need to decode the full marking including tolerance and voltage, I just use the Capacitor Code Decoder rather than trying to keep all the letter codes straight in my head. Life's too short to memorize tables you can look up in two seconds.

Unit Conversions Worth Memorizing

Working with capacitors means constantly jumping between picofarads, nanofarads, and microfarads. The relationships are straightforward, but it's easy to drop a zero when you're tired:

1μF=1,000 nF=1,000,000 pF1 \,\mu\text{F} = 1{,}000 \text{ nF} = 1{,}000{,}000 \text{ pF}

Quick mental shortcuts that actually work:

  • To convert pF to nF, divide by 1,000 (or shift the decimal point three places left)
  • To convert pF to µF, divide by 1,000,000 (six places left)
  • Going the other direction, just multiply instead
For example, that 220,000 pF cap from earlier: divide by 1,000 to get 220 nF, then divide by 1,000 again to get 0.22 µF. You can also jump straight from pF to µF by dividing by a million, but I find the two-step approach through nF helps me catch mistakes.

One thing that confuses people: nanofarads are the natural "middle" unit that bridges the gap between pF and µF. In practice, you'll often hear engineers say "220 nano" instead of "0.22 micro" even though they're the same value — it's just cleaner to work with integers when possible.

When This Matters in Practice

You'll find yourself decoding these codes in several common situations:

When you're doing incoming parts inspection and need to verify that your supplier sent the right components, a quick visual check of the markings beats pulling out an LCR meter every time. Board repair work constantly requires identifying unmarked or poorly documented components — the code might be the only clue you have. If you're prototyping RF filters or impedance matching networks, you need to grab the right values quickly from your parts stock. And if you're teaching junior engineers or students, being able to explain this system clearly helps them become independent faster.

I've also found it useful when dumpster diving through surplus electronics. You can pull caps from old boards and quickly assess whether they're worth keeping based on the values you see stamped on them. A pile of 104 and 105 ceramics? Definitely worth harvesting. A bunch of oddball values you'll never use? Maybe not worth the desoldering time.

Try It Yourself

Next time you're squinting at a tiny ceramic cap under your bench light, trying to remember if that third digit is a multiplier or an exponent or what, just save yourself the headache. Pull up the Capacitor Code Decoder, type in what you see, and get an instant answer with all the unit conversions done for you. Your brain has better things to remember than lookup tables — like which pin is the inverting input on an op-amp or where you left your good tweezers.

The code system itself is worth understanding because it helps you think in the right units and catch mistakes, but there's no shame in using tools to speed up the grunt work. That's what they're there for.

Related Articles