RC charging voltage at time calculator
With 1 kΩ, 1 µF and a 5 V supply, the capacitor reaches about 63.2 % of the supply after 1 ms, exactly one time constant. Enter resistance, capacitance, supply voltage and elapsed time to get the voltage at that instant. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Resistance
- 1,000
- Capacitance
- 0.000001
- Supply voltage
- 5
- Time
- 0.001
- Time constant
- 0.001
- Tau
- 0.001
- Capacitor voltage
- 3.1606027941
- Voltage
- 3.1606027941
When a DC step is applied through a resistor onto an initially uncharged capacitor, the plate voltage does not jump; it climbs along the classic exponential RC charge curve toward the supply. Engineers, students, and firmware authors often need the voltage at one specific time rather than a full plot: V_c of t equals V_s times one minus e to the minus t over R C, with R in ohms, C in farads, V_s in volts, and t in seconds. This RC charging voltage at time calculator accepts those four finite numbers, returns the capacitor voltage, the time constant τ equals R C, the charge fraction, stored charge, and the series current when it is finite, and rejects negative elapsed time with a clear validation error.
How voltage rises on a series RC charge curve
Start from Kirchhoff's voltage law on a loop that contains a constant supply V_s, a series resistor R, and a capacitor C that begins uncharged. The resistor current equals C times dV_c over dt, so the capacitor voltage obeys the first-order linear ODE R C dV_c over dt plus V_c equals V_s.
With V_c of zero equal to zero at the switching instant, the unique closed-form solution is V_c of t equals V_s times one minus the exponential of minus t over tau, where the time constant tau equals R times C. At t equals zero the voltage is zero; after one tau it has reached about sixty-three point two percent of the supply; after three tau roughly ninety-five percent; and after five tau about ninety-nine point three percent, the classic settling rule of thumb.
The complementary current is I of t equals V_s over R times e to the minus t over tau: large at the first instant and decaying toward zero as the capacitor approaches open circuit at DC. Stored charge on the plates is simply C times the instantaneous voltage, so once V_c is known the coulomb count follows without a second differential equation.
The model assumes ideal linear parts, no dielectric absorption, and a pure step applied at t equals zero; real switches, ESR, and leakage add second-order effects that belong on separate analysis paths. Energy stored is one half C V_c squared and is not the primary output here, because search intent for charging voltage at a chosen time differs from search intent for energy or for the bare product Q equals C V at a fixed bias.
Where RC charging voltage at time shows up in real work
Introductory electronics labs constantly assign RC charging plots so students can mark one-tau and five-tau milestones on a scope before they move on to discharge and multi-stage filters. Embedded and power-electronics bring-up teams estimate how long a soft-start RC or a reset supervisor network needs before a rail has reached a fraction of the final supply, then convert that delay into firmware timeouts and brown-out margins.
Analog designers sizing sample-and-hold windows, peak detectors, and RC timing blobs need V_c of t rather than only the bare time constant, because percent-of-final voltage is the acceptance criterion on the bench. Keep the static Q equals C V product, the tau equals R C time-constant-only landing, energy one half C V squared, and discharge-from-initial-voltage calculators on separate pages so each search intent has one clear tool rather than an overloaded multi-formula page that confuses both students and search engines.
When you only need the voltage at one timestamp on the charge curve, this RC charging voltage at time calculator is the direct contract: four numbers in, V_c and the supporting tau and fraction fields out, with no symbolic solver and no network hop.
What you can do with it
Lab RC charge milestones
Compute V_c(t) and percent-of-supply at one, three, and five time constants so students can compare scope cursors with the ideal exponential charge curve.
Soft-start and reset timing
Estimate capacitor voltage after a power-on delay for RC soft-start and supervisor networks before locking firmware timeouts.
FAQ
What formula does this RC charging voltage calculator use?
V_c(t) = V_s × (1 − e^(−t/(R×C))) for an initially uncharged capacitor in series with R driven by a step supply V_s. The time constant is τ = R×C.
What happens if time is negative?
Elapsed charging time must be ≥ 0 seconds; negative time is rejected and is not charged.
Which units should I use for R, C, V_s, and t?
Resistance in ohms, capacitance in farads, supply voltage in volts, and time in seconds. Pass 1e-6 for 1 µF and 1000 for 1 kΩ; SI prefix strings are not parsed.
What else does the response include besides voltage?
It returns τ = R×C, charge fraction and percent of supply, stored charge C×V_c, and the series current when finite, plus a short expression and formula string.
How long does a capacitor take to charge fully?
Strictly, it never quite reaches the supply. After one time constant, resistance times capacitance, it is at about 63.2 % of the supply, and after five it is practically there, the usual rule of thumb for a settled circuit.
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/elec/rc-charge-voltage \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"resistance":1000,"capacitance":0.000001,"supply_voltage":5,"time":0.001}'const res = await fetch("https://api.kit.forhosting.com/elec/rc-charge-voltage", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"resistance": 1000,
"capacitance": 0.000001,
"supply_voltage": 5,
"time": 0.001
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/elec/rc-charge-voltage",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"resistance": 1000,
"capacitance": 0.000001,
"supply_voltage": 5,
"time": 0.001
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/elec/rc-charge-voltage", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"resistance":1000,"capacitance":0.000001,"supply_voltage":5,"time":0.001}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"resistance":1000,"capacitance":0.000001,"supply_voltage":5,"time":0.001}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/elec/rc-charge-voltage", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"resistance": 1000,
"capacitance": 0.000001,
"supply_voltage": 5,
"time": 0.001
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "elec.rc_charge_voltage",
"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
The free browser path and the paid API share one deterministic pure function, so lab demos, homework keys, and production scripts never disagree on the same R, C, V_s, and t.
What you send and what you get back
Numeric values and numeric strings are both accepted so form widgets and spreadsheet paste stay convenient; SI prefix strings such as one microfarad written as text are not parsed, so pass one times ten to the minus six for a microfarad part and one thousand for a one-kilohm resistor. Resistance and capacitance must be greater than or equal to zero; elapsed time must be greater than or equal to zero. NaN and Infinity are rejected. Classic classroom checks include one kilohm and one microfarad at five volts after one millisecond, which is exactly one time constant and should sit near sixty-three point two percent of five volts, and the t equals zero case that must return zero volts on the capacitor. Send four finite numbers: resistance under the field resistance in ohms, capacitance under capacitance in farads, supply_voltage under supply_voltage in volts, and time under time in seconds. Aliases are accepted for convenience—r, R, or ohms for resistance; c, C, or farads for capacitance; vs, Vs, voltage, or volts for the supply; t or seconds for elapsed time—but only one key may appear for each quantity in a request. Negative time is rejected with invalid_input and the message states that negative time is not allowed; negative R or C fail the same way. On success the response echoes cleaned inputs, time_constant and tau as R times C, capacitor_voltage and voltage as V_c of t, charge_fraction between zero and one, percent_of_supply as one hundred times that fraction, charge and charge_coulombs as C times V_c, current and current_amperes as the series current when it is finite, unit labels, a short expression string, method rc_series_charge, and the formula string. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where RC charging voltage at time shows up in real work
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
CI fixtures and answer keys
Script the same V_c(t)=V_s(1−e^(−t/RC)) evaluation used in the browser so automated graders share one ground truth for charging-voltage-at-time problems.
Technical questions
What does the RC charging voltage at time calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.