ForHosting KIT · Engineering & construction

MOSFET switching loss calculator

Hard-switching 48 V and 10 A with 50 ns and 40 ns edges at 100 kHz dissipates 2.16 W in the MOSFET. Enter voltage, current, rise and fall times and frequency to get that overlap loss for heat-sink sizing. 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
Drain voltage
48
Drain current
10
Rise time
0.00000005
Fall time
0.00000004
Switching frequency
100,000
You get
Energy on
0.000012
Energy off
0.0000096
Energy switching
0.0000216
Energy joules
0.0000216

Hard-switched MOSFETs in buck, boost, half-bridge, and full-bridge converters dissipate energy every time drain voltage and drain current overlap during turn-on and turn-off. That switching loss often dominates conduction loss at high frequency and sets how large a heat sink, copper pour, or package you need. This MOSFET switching loss calculator applies the classic linear V–I overlap model used in power-electronics handbooks and datasheet application notes: energy per edge is one half times voltage times current times transition time, total switching energy is the sum of turn-on and turn-off contributions, and average power is that energy times switching frequency. Enter positive finite drain voltage, drain current, rise time, fall time, and frequency in SI units (volts, amperes, seconds, hertz).

How hard-switching MOSFET loss is estimated

During a hard turn-on, drain current rises while drain-source voltage is still high, then voltage falls while current is near full load. During turn-off the sequence reverses: voltage rises while current is still flowing, then current falls.

If you approximate each transition as a linear ramp of the overlapping V and I waveforms, the energy lost in that edge is the area of a right triangle with base equal to the transition time and height equal to the product of bus voltage and switched current—exactly one half V_DS times I_D times t. The model deliberately ignores reverse-recovery of a body diode or freewheel diode, Coss charging loss, gate drive energy, and soft-switching ZVS or ZCS regions—those need separate terms when they matter.

What remains is a transparent first-pass loss number you can drop into a thermal spreadsheet, compare against I²R conduction loss, and decide whether to slow the edges for EMI or speed them up for cooler silicon.

Frequency and gate-drive trade studies

Sweep switching frequency or measured edge times to see how P_sw scales, then balance efficiency against EMI when choosing R_g and PWM rate.

What formula does this MOSFET switching loss calculator use?

It uses the classic hard-switching linear V–I overlap model: E_on = ½·Vds·Id·tr, E_off = ½·Vds·Id·tf, E_sw = E_on + E_off, and P_sw = E_sw·f. Times are in seconds and frequency in hertz.

Should rise and fall times be entered in nanoseconds or seconds?

Seconds (SI). Enter 50 ns as 5e-8 or 0.00000005. Non-positive times are rejected so unit mistakes surface as validation errors instead of absurd multi-megawatt losses.

Does this include conduction loss or Coss / Qrr loss?

No. This page estimates hard-switching overlap loss only. Conduction I²R, output-capacitance charging, diode reverse recovery, and soft-switching ZVS/ZCS need separate terms or other tools.

Which voltage and current should I use?

Use the hard-switched bus voltage (drain-source voltage during the transition) and the drain current being switched at that edge—often inductor current at the switching instant, not the absolute maximum ratings.

What does it cost?

The browser tool is free and runs locally.

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/mosfet-switching-loss

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/mosfet-switching-loss \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"drain_voltage":48,"drain_current":10,"rise_time":5e-8,"fall_time":4e-8,"switching_frequency":100000}'
{
  "drain_voltage": 48,
  "drain_current": 10,
  "rise_time": 5e-8,
  "fall_time": 4e-8,
  "switching_frequency": 100000
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "elec.mosfet_switching_loss",
  "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.

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.

Invalid inputs fail with invalid_input and are not charged.

How hard-switching MOSFET loss is estimated

Summing the turn-on rise interval and the turn-off fall interval gives total switching energy E_sw equals one half V_DS I_D times (t_r plus t_f). Average switching power is then simply E_sw multiplied by the switching frequency f_sw, because each full cycle repeats that energy dump once. Datasheets often quote t_r and t_f under specific V_GS, R_g, and test load conditions; use the times that match your gate drive and clamp the voltage to the actual bus you switch, not the absolute maximum rating.

What you send and what you get back

Wire the free browser form for homework and quick thermal checks, then call the identical contract from scripts when you need bulk loss sweeps across frequency or current. If you need RC snubber sizing, resistor continuous dissipation, conduction I²R only, or RC time constants, treat those as separate tools rather than overloading this switching-loss page. Send five required finite positive numbers: drain_voltage in volts for the hard-switched V_DS bus level, drain_current in amperes for the load current at the transition, rise_time in seconds for the turn-on transition (for example 5e-8 for fifty nanoseconds), fall_time in seconds for the turn-off transition, and switching_frequency in hertz (for example 100000 for one hundred kilohertz). Aliases such as vds, v_ds, voltage, v, id, i_d, current, i, tr, t_rise, t_r, tf, t_fall, t_f, f, f_sw, and frequency are accepted so form widgets and scripts stay convenient, but only one key may appear for each quantity. Missing fields, non-numeric strings, NaN, Infinity, zero, or negative values fail with invalid_input and are not charged. On success the response echoes the cleaned inputs, energy_on and energy_off for each edge, energy_switching and energy_joules as the same total joule value, power_switching and power_watts as the same average watt value, total_transition_time as tr plus tf, unit labels for joule, watt, second, and hertz, method hard_switching_linear_overlap, 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 MOSFET switching-loss calculators show up in real work

Power-supply designers sizing a synchronous buck or active-clamp flyback often start with a first-pass P_sw estimate before ordering magnetics and heat sinks; plugging bus voltage, peak inductor current, and datasheet rise and fall times into a trusted calculator turns a napkin estimate into a documented loss budget. Motor-drive and inverter teams compare hard-switched loss at several PWM frequencies to decide whether silicon MOSFET or wide-bandgap parts clear the thermal envelope at the target switching rate. Keep snubber design, pure resistor wattage, and conduction-loss landings separate so each search intent has one clear page rather than an overloaded multi-physics tool that confuses both students and search engines. Application engineers writing gate-driver notes use the same linear-overlap identities when they show how reducing R_g shortens t_r and t_f and therefore cuts E_sw, while also warning that faster edges raise EMI. 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.

Converter thermal budget

Estimate hard-switching watts from bus voltage, load current, datasheet tr/tf, and f_sw so heat-sink and copper area are sized before the first prototype board is ordered.

Lab and CI loss fixtures

Script the same linear-overlap formulas used in the browser so homework auto-graders and production efficiency logs assert consistent switching-loss numbers.

Read the full KIT documentation →