ForHosting KIT · Engineering & construction

Series capacitor voltage sharing calculator

Across 400 V, a string of 100, 220 and 100 µF capacitors leaves the 220 µF part with the smallest share, and every part stays within its rating. Enter each capacitance and rating to see the voltage, margin and pass or fail per part. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Total voltage
400
You get
Equivalent capacitance
40.7407407407
Highest rating utilization percent
65.1851851852

This series capacitor voltage sharing calculator finds the ideal voltage across every capacitor in a series string when the total applied voltage and individual capacitances are known. Because series capacitors carry equal charge, smaller capacitances take a larger share of the voltage. Enter each part’s capacitance and voltage rating to see its calculated voltage, percentage share, rating utilization, remaining margin, and pass or fail result. The calculation is useful for an early design check, while clearly separating ideal capacitance-based division from real-world leakage, tolerance, and transient effects.

Why series capacitors do not always split voltage equally

Capacitors connected in series carry the same magnitude of charge in the ideal steady-state model, but equal charge does not imply equal voltage. The relationship is voltage equals charge divided by capacitance, so a smaller capacitor develops more voltage than a larger one. Two identical parts divide the applied voltage equally; mixed values divide it in inverse proportion to capacitance.

This distinction matters when a designer stacks capacitors to withstand a bus voltage or combines available parts to obtain an equivalent value. A string can have a comfortable sum of nameplate ratings and still overstress one member if that part receives a disproportionate share. The calculator exposes that risk row by row.

It reports the calculated voltage, the percentage of total voltage, and the percentage of the supplied rating used by each capacitor. A negative voltage margin or a utilization above one hundred percent marks a failed ideal rating check. Use capacitance values in farads, microfarads, nanofarads, or another unit, but use the same unit for every capacitor because only their ratios determine sharing.

How the inverse-capacitance calculation works

First, the calculator forms the reciprocal sum of the capacitances: one divided by the first capacitance, plus one divided by the second, continuing through the complete string. The equivalent series capacitance is the reciprocal of that sum. Each capacitor’s ideal voltage is then the total applied voltage multiplied by its own reciprocal capacitance and divided by the reciprocal sum.

This produces shares that add to the requested total apart from harmless display rounding. For every row, rating utilization is calculated as assigned voltage divided by voltage rating, while voltage margin is rating minus assigned voltage. The overall result passes only when every calculated voltage is less than or equal to its corresponding rating.

Inputs must include a positive total voltage and at least two records, each with a positive finite capacitance and voltage rating. The response also includes the formula and equivalent capacitance so automated reviews can preserve both the decision and the basis for it.

Use the result as an ideal check, not a complete safety guarantee

Real series strings rarely maintain perfect capacitance-only voltage division under every condition. Component tolerances change the actual capacitance ratios, leakage currents can dominate long-term DC sharing, dielectric absorption affects settling, and switching or surge events can create transient distributions unlike the steady-state result. Temperature, aging, contamination, and differences between manufacturers can widen those imbalances.

High-voltage assemblies commonly use balancing resistors or active networks, selected from worst-case leakage data, to establish a more predictable static division. Snubbers or other protection may be needed for transients. Therefore, treat the calculated pass result as an early screening step: it confirms whether the nominal ideal division already violates a rating, but it does not certify the finished circuit.

Repeat the analysis with tolerance extremes, apply the manufacturer’s recommended voltage derating, check ripple current and thermal limits, and evaluate fault conditions.

High-voltage DC bus screening

Check the nominal voltage assigned to every capacitor before developing a balancing network and worst-case tolerance analysis.

BOM substitution review

Compare a proposed mix of capacitances and ratings with the original string and identify the part with the highest rating utilization.

Electronics education

Demonstrate why equal charge creates inverse-capacitance voltage division and why unequal capacitors do not split voltage evenly.

What formula is used for each capacitor voltage?

For capacitor i, Vi = Vtotal × (1/Ci) / Σ(1/Cj). The capacitances may use any unit as long as all entries use the same one.

Do equal capacitors share voltage equally?

Yes in the ideal model. Identical capacitances have identical reciprocal weights, so each receives total voltage divided by the number of capacitors.

Why does the smallest capacitor receive the highest voltage?

Series capacitors carry equal ideal charge, and V = Q/C. With the same charge, a smaller capacitance produces a larger voltage.

Does a passing result guarantee the string is safe?

No. The result covers nominal capacitance-based sharing only. Check tolerance, leakage, derating, temperature, transients, ripple, and balancing components for a real design.

Can I enter capacitances in microfarads or nanofarads?

Yes, any unit works as long as every capacitor uses the same one, because only the ratios between capacitances decide how the voltage is shared. The total voltage and the ratings are always entered in volts.

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.

POSThttps://api.kit.forhosting.com/elec/series-cap-voltage-share

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.

curl -X POST https://api.kit.forhosting.com/elec/series-cap-voltage-share \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"total_voltage":400,"capacitors":[{"capacitance":100,"voltage_rating":250},{"capacitance":220,"voltage_rating":200},{"capacitance":100,"voltage_rating":250}]}'
{
  "total_voltage": 400,
  "capacitors": [
    {
      "capacitance": 100,
      "voltage_rating": 250
    },
    {
      "capacitance": 220,
      "voltage_rating": 200
    },
    {
      "capacitance": 100,
      "voltage_rating": 250
    }
  ]
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "elec.series_cap_voltage_share",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

max_n1000
HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

How the inverse-capacitance calculation works

Invalid, missing, zero, or negative values return an invalid_input error rather than a plausible-looking result.

Use the result as an ideal check, not a complete safety guarantee

The browser calculator uses the same deterministic arithmetic as the API. Automated calls cost $0.002 per request, making the endpoint suitable for BOM checks and design pipelines without changing the engineering assumptions.

How much does the API calculation cost?

Each successful API request costs $0.002. The on-page browser calculation uses the same deterministic core and is free.

Read the full KIT documentation →