Capacitance converter
One microfarad is 1,000,000 picofarads. Convert any capacitance between farads, millifarads, microfarads, nanofarads and picofarads and see the value in all five units at once, ready for a parts list or a homework sheet. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Capacitance magnitude to convert
- 1
- Input unit
- microfarad
- Output unit
- picofarad
- Result
- 1,000,000
- Farad
- 0.000001
- Millifarad
- 0.001
- Microfarad
- 1
Capacitance conversion between farads and the everyday engineering prefixes is a constant chore in electronics labs, BOM reviews, RF matching notes, power-supply decoupling lists, and secondary-school circuit homework. People search for a capacitance converter when they need microfarads next to nanofarads, picofarads next to farads, or millifarads next to microfarads, not a general multi-unit toolbox that also handles length and temperature. This capability accepts one finite amount plus from and to unit labels among farad, millifarad, microfarad, nanofarad, and picofarad, bridges every conversion through the farad so results stay consistent, and returns the target value together with the same capacitance expressed in all five units. Unrecognized unit names are rejected with a clear validation error instead of silently guessing a nearby symbol.
How the capacitance converter maps SI prefixes through the farad
Start from the farad as the SI coherent unit of capacitance C and express every other unit as a fixed power-of-ten factor into farad. One millifarad is exactly one thousandth of a farad. One microfarad is exactly one millionth of a farad, which is why electrolytic and film capacitor catalogs still print values such as 100 µF or 0.1 µF on every reel label.
One nanofarad is one billionth of a farad and one picofarad is one trillionth of a farad, the scale of small ceramic bypass parts and RF layout parasitics. This calculator never mixes those paths ad hoc. It multiplies the input amount by the factor of the source unit to reach farad, then divides by the factor of the target unit to produce the result.
Because every path shares the same intermediate, converting one microfarad to one thousand nanofarads and back, or comparing millifarads to picofarads across six orders of magnitude, stays numerically consistent within ordinary floating-point precision. The tool does not convert inductive reactance, does not solve RC time constants, does not compute energy stored as one half C V squared, and does not fetch live distributor stock.
It answers only the algebraic capacitance unit conversion people mean when they type capacitance converter into a search bar and expect farads, millifarads, microfarads, nanofarads, and picofarads with exact SI prefix factors.
Where dedicated capacitance conversion shows up in real work
Secondary-school and college electronics courses constantly assign problems that give a capacitor value on one scale and ask for another, often mixing lab-style microfarads with picofarads and nanofarads in the same worksheet. Power-electronics and PCB teams quote bulk electrolytic banks in millifarads or microfarads while RF and digital teams talk in nanofarads and picofarads, so a single conversion pass keeps decoupling lists, Bode models, and BOM spreadsheets aligned. Sensor and timing-circuit designers normalize RC parts between nF and pF before comparing vendor footprints.
Procurement scripts that scrape distributor CSV rows with mixed F, mF, uF, nF, and pF tags can call this capability once per line instead of reimplementing the factors in every service. If you later need inductive reactance, energy stored in a capacitor, general multi-category unit conversion, or RC time-constant solvers alone, treat those as separate search intents and landings rather than overloading this capacitance converter page.
What you can do with it
BOM and datasheet normalization
Normalize capacitor values among farad, millifarad, microfarad, nanofarad, and picofarad so procurement spreadsheets and SI reports stay consistent.
PCB decoupling and power design
Convert bulk bank microfarads and millifarads into nanofarads or picofarads for comparison with ceramic bypass networks without hand-written factors.
FAQ
Which capacitance units does this converter support?
Farad (F), millifarad (mF), microfarad (µF, uF), nanofarad (nF), and picofarad (pF).
What happens if I send an unrecognized unit?
The error message includes Unrecognized unit and lists the supported families so you can correct the label.
How many picofarads are in one microfarad?
Exactly 1_000_000 picofarads. One microfarad is 1×10⁻⁶ F and one picofarad is 1×10⁻¹² F.
What does it cost?
The browser tool is free and runs locally.
How many nanofarads is 0.1 µF?
0.1 µF is 100 nF, because one microfarad equals one thousand nanofarads. It is the same capacitor value written two ways, and the converter shows it in all five units so you can match any label.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/capacitance \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":1,"from":"microfarad","to":"picofarad"}'const res = await fetch("https://api.kit.forhosting.com/conv/capacitance", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 1,
"from": "microfarad",
"to": "picofarad"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/capacitance",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 1,
"from": "microfarad",
"to": "picofarad"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/capacitance", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":1,"from":"microfarad","to":"picofarad"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":1,"from":"microfarad","to":"picofarad"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/capacitance", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 1,
"from": "microfarad",
"to": "picofarad"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.capacitance",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
What you send and what you get back from the API and browser form
Send three fields: amount, a finite number for the capacitance magnitude; from, a string naming the input unit; and to, a string naming the output unit. When a unit string is unknown the error message includes Unrecognized unit and lists the five supported families so clients can fix the label rather than guessing. Classic checks include one microfarad becoming one million picofarads, one nanofarad becoming one thousand picofarads, one millifarad becoming one thousand microfarads, and one farad matching one thousand millifarads exactly. Both unit fields accept short keys and everyday words in any common casing, including farad or F, millifarad or mF or milli_farad, microfarad or uF or µF or micro_farad or mfd, nanofarad or nF or nano_farad, and picofarad or pF or pico_farad or puff. Missing fields, non-numeric amount strings, NaN, Infinity, and unrecognized unit labels fail with invalid_input and are not charged. On success the response echoes the cleaned amount, normalized from and to keys, the primary result in the target unit, the same capacitance as farad, millifarad, microfarad, nanofarad, and picofarad with twelve significant digits of stable precision, the SI factors used, the formula string, and method farad_bridge. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where dedicated capacitance conversion shows up in real work
Data pipelines that ingest mixed IoT or lab payloads with capacitance unit tags normalize those readings into one SI key before stacking with simulation models. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Integration use cases
Homework and curriculum tools
Map exam values between F, mF, µF, nF, and pF for answer keys, auto-graders, and interactive electronics demos that share one JSON contract.
Technical questions
Are microfarad and mfd the same?
Yes in common electronics catalogs. This converter accepts mfd as an alias for microfarad so legacy US datasheet labels parse cleanly.