RL filter cutoff calculator
A 1000-ohm resistor and a 1 mH inductor put the 3 dB corner of a first-order RL filter at about 159.155 kHz. The same step gives the angular cutoff and the time constant, for low-pass and high-pass sections alike. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Resistance in ohms
- 1,000
- Inductance in henries
- 0.001
- Cutoff frequency
- 159,154.943092
- Cutoff frequency hz
- 159,154.943092
- Fc
- 159,154.943092
- Angular cutoff
- 1,000,000
The cutoff frequency of a first-order RL filter is the corner where the magnitude response is three decibels down from the passband, set by the ratio of resistance to inductance. In SI units the formula is simple and universal for both the low-pass and high-pass single-pole RL sections: fc equals R divided by two pi L, with R in ohms, L in henries, and fc in hertz. The same numbers also give the angular cutoff omega-c equals R over L in radians per second and the RL time constant tau equals L over R in seconds, so one request can feed Bode estimates, settling windows, and lab notebook checks at once. Students size series inductors and resistors for audio crossover experiments; power and EMI engineers place RL snubbers and choke filters against known noise bands; firmware teams convert millihenry BOM lines into hertz before writing control loops. This RL filter cutoff calculator accepts positive finite resistance and inductance, runs a deterministic multiply-and-divide path, and returns cleaned inputs, fc, omega-c, tau, and a printable expression. Zero resistance is rejected with a clear validation error because the corner formula and tau both require a positive R; zero or negative inductance is likewise invalid.
How the first-order RL cutoff frequency works
A first-order RL network has a single energy-storage element and therefore a single time constant tau equal to L divided by R. The transfer function magnitude reaches one over root two of its passband asymptote at the angular frequency omega-c equal to one over tau, which is R over L. Converting to ordinary frequency in hertz multiplies by one over two pi, so the design equation written on every exam sheet is fc equals R over two pi L.
The low-pass topology places the inductor in series with the load and the resistor as the shunt (or equivalent source resistance), attenuating high frequencies; the high-pass topology swaps the roles and attenuates low frequencies. In both cases the magnitude of the corner is the same product of R and L, which is why a single calculator serves both topologies when the question is only where the three-decibel point sits.
Resistance must be in ohms and inductance in henries so that fc lands in hertz: one thousand ohms with one millihenry yields about one hundred fifty-nine kilohertz, and one ohm with one henry yields about zero point one five nine hertz. Real inductors have series resistance, core loss, and parasitic capacitance that shift the effective corner and roll-off slope, but the first design step is still the ideal formula from the datasheet R and L.
Capacitive reactance, RC time constants, multi-pole ladders, and full Bode plots are different search intents and belong on separate landings so this page stays focused on the RL corner.
Where RL filter cutoff calculators show up in real work
Introductory electronics and signals labs assign RL low-pass and high-pass drills so students convert datasheet ohms and henries into a predicted three-decibel frequency before they measure with a function generator and scope. Audio and instrument designers size series inductors and load resistances for simple passive crossovers and RF chokes by locking fc to a known band edge and then verifying with a network analyzer. Power electronics and EMI teams estimate choke and snubber corners against switching harmonics, using the same R and L product that appears in the control notebook.
Keep RC time-constant, capacitive-reactance, and multi-pole filter landings separate so each search intent has one clear page rather than an overloaded multi-formula tool that confuses both students and search engines.
What you can do with it
Lab homework and Bode estimates
Convert a resistor value and an inductor value into fc, ωc, and τ so students can mark the −3 dB corner before measuring with a scope or network analyzer.
Passive crossover and choke sizing
Pick series L and R (or load R) so a first-order RL section sits at a target audio or EMI band edge using fc = R/(2πL).
FAQ
What formula does this RL filter cutoff calculator use?
fc = R / (2 · π · L) for the −3 dB cutoff in hertz, ωc = R / L for the angular cutoff in rad/s, and τ = L / R for the RL time constant in seconds.
What happens if resistance is zero?
Zero resistance is not allowed because fc = R/(2πL) and τ = L/R both require a positive resistance in ohms.
Does this cover low-pass and high-pass RL filters?
Yes for the corner magnitude. First-order series-L low-pass and series-R high-pass RL sections share the same fc = R/(2πL); the topology changes which side of the corner is the passband.
What units should I use?
Resistance in ohms and inductance in henries. 1 kΩ × 1 mH gives fc ≈ 159.155 kHz. Pass SI values as numbers (e.g. 1000 and 0.001); prefix strings like '1k' or '1mH' are not parsed.
What does it cost?
The browser tool is free and runs locally.
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/rl-filter-cutoff \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"resistance":1000,"inductance":0.001}'const res = await fetch("https://api.kit.forhosting.com/elec/rl-filter-cutoff", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"resistance": 1000,
"inductance": 0.001
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/elec/rl-filter-cutoff",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"resistance": 1000,
"inductance": 0.001
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/elec/rl-filter-cutoff", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"resistance":1000,"inductance":0.001}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"resistance":1000,"inductance":0.001}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/elec/rl-filter-cutoff", 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,
"inductance": 0.001
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "elec.rl_filter_cutoff",
"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
Send a finite positive resistance under the field resistance, expressed in ohms, and a finite positive inductance under the field inductance, expressed in henries. Numeric values and numeric strings are both accepted so form widgets and spreadsheet paste stay convenient; SI prefix strings such as one kilohm written as text are not parsed, so pass one thousand for a kilohm part and zero point zero zero one for a millihenry part. Classic classroom checks include one thousand ohms with one millihenry giving fc near one hundred fifty-nine point one five five kilohertz, and one ohm with one henry giving fc near zero point one five nine one five five hertz. If you need RC products, capacitive reactance at a drive frequency, or multi-element filter synthesis, treat those as separate tools rather than extending this pure RL corner formula. The same resistance is accepted under the aliases r, R, or ohms, and inductance under l, L, henries, or henry, but only one key may appear for each quantity in a request. Resistance must be strictly greater than zero; zero resistance fails with invalid_input because fc and tau are undefined or meaningless for R equal to zero, and the product requirement is explicit about that error. Inductance must also be greater than zero; NaN, Infinity, and negative values fail with invalid_input and are not charged. On success the response includes cleaned resistance and inductance, cutoff_frequency, cutoff_frequency_hz, and fc as the same R over two pi L result, angular_cutoff, angular_cutoff_rad_s, and omega_c as R over L, time_constant, time_constant_seconds, and tau as L over R, unit labels for hertz, radian per second, and second, a short expression string showing fc, omega-c, and tau, method rl_filter_cutoff, 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 RL filter cutoff calculators show 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 fc = R/(2πL) product used in the browser so automated graders and BOM checks share one ground truth for RL corners.