吃瓜tv

Capacitor units: one capacitance, several readable forms

The SI unit of capacitance is the farad, written F. Common electronic values are expressed in picofarads, nanofarads and microfarads because these scales are easier to read in circuits and component lists. One microfarad equals one thousand nanofarads and one million picofarads. Converting between those units changes how a value is written; it does not change the capacitor or any of its electrical ratings.

For example, 100000 pF, 100 nF and 0.1 碌贵 are the same nominal capacitance. The converter below accepts explicit units and displays all three common scales together with farads. It can also compare several lines from a small component list and flag equal nominal values. It does not parse a full customer BOM, upload data or decide whether two parts are approved alternatives.

This page owns value conversion and clear BOM notation. To interpret a printed three-digit marking such as 104, continue to how to read capacitor codes. To interpret a circuit graphic, use capacitor symbols. Those tasks may involve units, but a unit converter should not quietly guess a marking scheme or infer a component technology from an ambiguous number.

The conversion ladder and the direction of multiplication

The prefixes pico, nano, micro and milli represent powers of ten relative to the farad. Picofarad is 10^-12 F, nanofarad is 10^-9 F, microfarad is 10^-6 F and millifarad is 10^-3 F. Moving from a larger unit to a smaller unit increases the numerical value. Moving in the other direction decreases it. The BIPM prefix reference is the primary source for the SI prefix meanings.

To convert nF to pF, multiply by 1000; to convert nF to 碌贵, divide by 1000. Thus 4.7 nF is 4700 pF and 0.0047 碌贵. As another check, 220 碌贵 is 220000 nF and 0.000220 F. Writing the starting value and destination unit beside the calculation makes the direction easier to audit than a bare instruction to move a decimal point.

Use a plausibility check whenever a value crosses systems. A decoupling value copied from a schematic as 0.1 碌贵 should not become 0.1 nF in the BOM. That would be a thousand-fold change. Compare the resulting values in a common unit and keep the original source text with the conversion record. Conversion errors are often transcription errors rather than difficult mathematics.

Source context: .

碌贵, 渭F and uF: handle text deliberately

The micro prefix may appear as the micro sign 碌, the Greek letter 渭 or the plain ASCII letter u in electronic documents. This worksheet accepts all three before F and normalizes them for comparison. That input accommodation is useful when values are copied between PDFs, CAD fields and spreadsheets. It does not mean every software system will interpret those characters identically.

Capitalization still matters. In SI notation, lower-case m denotes milli and upper-case M denotes mega. A careless automatic uppercase operation can therefore change the apparent meaning of a unit. This tool accepts the explicitly listed forms and rejects unfamiliar capitalization instead of deciding what the author probably meant. For production data, choose one documented text convention and verify that the receiving system preserves it.

Historical labels such as MFD or MMF can have context-specific meanings and should not be silently normalized by a general-purpose tool. A scanned document may also misread a micro sign, decimal point or zero. If the original notation is ambiguous, inspect its source and component documentation. The correct output can be 鈥渦nresolved,鈥� because a precise conversion of the wrong interpretation is still wrong.

Use the batch converter without losing context

Enter one explicit value per line, such as 100 nF or 4.7 uF. Scientific notation is accepted, so 1e-7 F can be compared with 100 nF. The worksheet requires a unit on every line and limits the small batch to thirty entries. It rejects bare numbers, embedded-letter codes, commas and unexpected text. That keeps the scope reviewable and prevents a copied component description from being partly interpreted as a valid capacitance.

If one line is invalid, the tool asks you to correct it rather than exporting a partly valid list that looks complete. Blank internal lines are flagged as well. The displayed result retains the entered text next to the conversion. This helps the reviewer locate the source of a mismatch. Equivalent-value notices compare capacitance only, with a small numerical allowance for ordinary floating-point arithmetic.

The downloadable text is built locally from the current calculation. Editing an input clears the previous result and disables the old download until you calculate again. The tool does not store a project file, send values to analytics or automatically fill Contact. For a real BOM, preserve reference designators and part identifiers in your controlled source file; this compact worksheet is a value-checking aid, not a replacement for document control.

Equal nominal capacitance does not mean equal components

Two BOM lines can normalize to the same value while describing materially different parts. Compare tolerance, rated voltage, dielectric, package, temperature range, termination and the approved manufacturer identifier. If any of these requirements are unknown, value equivalence alone is insufficient to authorize a substitution. The converter deliberately stops short of outputting a green 鈥渃ompatible鈥� verdict.

Consider a hypothetical 100 nF part used in a timing network and another 100 nF part used for local supply bypassing. Their circuit roles may lead to different stability and loss requirements even before package differences are considered. Likewise, nominal capacitance measured under one condition is not necessarily the effective capacitance under the circuit's operating conditions. Keep the required function visible when reviewing a substitute.

For temperature-stable ceramic selection, see the C0G capacitor guide. For assembly preparation, a BOM should connect each approved part to the correct reference, quantity and variant. A value column is useful, but it is only one part of that relationship. A purchasing decision based on the converted number alone can preserve a spreadsheet while changing the behavior of the circuit.

Tolerance arithmetic is separate from conversion

Unit conversion is exact as a scale relationship, while component tolerance describes a permitted interval around a specified nominal value under defined conditions. A nominal 100 nF capacitor with a declared 卤5% tolerance has an initial interval of 95 to 105 nF under that tolerance definition. Expressed in microfarads, the same interval is 0.095 to 0.105 碌贵. The conversion does not add another five percent or make the component more accurate.

For very small capacitances, a tolerance may be specified as an absolute capacitance rather than a percentage. An illustrative 10 pF value with 卤0.5 pF tolerance spans 9.5 to 10.5 pF. Do not assign a percentage meaning to an unfamiliar marking letter without its code table. This page intentionally requires explicit value units and leaves component-code interpretation to the separate reader.

Displayed digits also need perspective. Converting 0.1 碌贵 to 100000 pF does not establish six digits of measured precision. Those zeros express the chosen unit, not measurement quality. When a report needs uncertainty or significant-figure control, document that separately. The worksheet rounds its display for readability and should not be used to imply a metrology result that has never been measured.

Carry units through circuit calculations

In an ideal capacitor, charge relates to capacitance and voltage through Q = C 脳 V. With C in farads and V in volts, charge is in coulombs. A hypothetical 100 nF capacitor at 5 V corresponds to 0.5 microcoulomb under that ideal model. This example illustrates why the factor of one million between 碌贵 and F must be retained when values enter a formula.

An ideal RC time constant is R 脳 C, with resistance in ohms and capacitance in farads giving seconds. For 10 k惟 and 100 nF, the result is 0.001 second, or 1 ms. The example describes a simple first-order model, not every loaded or sampled circuit. If the capacitor is at the output of a divider, the effective resistance may be the Thevenin resistance rather than either resistor alone.

Use the voltage divider formula and load workbench to understand that DC network before adding dynamic behavior. The point is to keep each model's assumptions visible. Correctly converting nF to 碌贵 is necessary, but it does not establish a filter response, settling performance, ripple rating or a suitable component. Those conclusions require the circuit and component data as well as the units.

A review routine for schematics, BOMs and purchases

Start from the released schematic and its revision. Export or inspect the value field without changing its content, then normalize the unit in a separate review column. Preserve reference designators so an unexpected value can be traced back to the circuit. Compare the normalized value with the approved component specification rather than overwriting the original field immediately.

For every difference, decide whether it is just a display format or an actual specification change. 鈥�100 nF versus 0.1 碌贵鈥� is a value-format difference. 鈥�100 nF versus 0.1 nF鈥� is a nominal mismatch. 鈥�100 nF C0G versus 100 nF X7R鈥� can be a dielectric difference even though the values agree. Record that classification so purchasing and engineering do not have to reconstruct the discussion later.

Before an assembly enquiry, reconcile quantities, do-not-fit variants and approved alternatives in addition to values. The required files for PCB assembly guide explains the broader release package. If a conversion issue remains unresolved, identify the affected references when you contact 吃瓜tv. A short, explicit question with its source entry helps more than an apparently complete BOM built on assumptions.

Quick answers and common mistakes

Is 1 nF the same as 1000 pF? Yes. Is 1 碌贵 the same as 1000 nF? Yes. Is 0.1 碌贵 the same as 100 nF? Yes. Does 104 mean 104 pF? Not necessarily: in a confirmed three-digit multiplier scheme it represents a different value, while other contexts may use direct notation. A bare number therefore belongs in a code-identification task, not an automatic unit conversion.

Can capacitance be entered as zero? This worksheet requires a positive value because it is intended to compare physical capacitor specifications. A do-not-fit entry, absent component or open circuit should be recorded as that state, not converted into a zero-capacitance part. Is a different unit evidence of a different component? No; compare the nominal values and then the remaining specification fields.

The most useful conversion record is brief and reproducible: original text, normalized value, source revision and any unresolved interpretation. Keep those together when a drawing, BOM or supplier document is updated. This page helps resolve scale and notation so the next engineering or purchasing decision can be made from clear data rather than from a guessed prefix.