{"id":3527,"date":"2026-10-10T13:17:40","date_gmt":"2026-10-10T05:17:40","guid":{"rendered":"http:\/\/www.healthyharvestke.com\/blog\/?p=3527"},"modified":"2026-10-10T13:17:40","modified_gmt":"2026-10-10T05:17:40","slug":"how-to-design-a-mosfet-based-power-supply-4faa-4cc858","status":"publish","type":"post","link":"http:\/\/www.healthyharvestke.com\/blog\/2026\/10\/10\/how-to-design-a-mosfet-based-power-supply-4faa-4cc858\/","title":{"rendered":"How to design a MOSFET – based power supply?"},"content":{"rendered":"

Hey there, it\u2019s Jake from the MOSFET supply team \u2013 been getting a ton of DMs lately from techs, design engineers, and even small startup founders asking the same thing: \u201cHow do I actually build a reliable, efficient power supply using MOSFETs?\u201d Most of you aren\u2019t just chugging along with off-the-shelf parts; you\u2019re tweaking designs for IoT gadgets, portable tools, or solar setups, and your old power supplies are either wasting too much juice or frying when things get cold. I get it \u2013 I\u2019ve been in the lab at 2 a.m. troubleshooting a power supply that kept dropping voltage mid-test, staring at a pile of MOSFETs like they\u2019re magic black boxes. Spoiler: they are, but only if you design them right. Today, I\u2019m breaking this down like I would for a new hire on our team \u2013 no jargon overload, no fancy equations that make your eyes cross, just real stuff we see every day at the supplier desk. Let\u2019s dive in. MOSFETs<\/a><\/p>\n

<\/p>\n

First, let\u2019s get one thing straight: MOSFETs aren\u2019t just switches for fun \u2013 they\u2019re the backbone of every switching power supply (aka the ones that don\u2019t get hot like linear supplies, aka the ones most of you actually need). Linear supplies are great for tiny, low-load apps, but if you\u2019re running anything over a few hundred milliamps, switching supplies with MOSFETs will save you so much power. But here\u2019s the catch: pick the wrong MOSFET, and your whole design will be garbage. I\u2019ve seen a guy use a 100V N-channel MOSFET for a 12V supply just because it was cheap, and when the unit got kicked around, it shorted out. Oops. So step one: know exactly what you need from your MOSFET before you even start shopping.<\/p>\n

Let\u2019s start with the basics of power supply topologies \u2013 because the MOSFET\u2019s job changes depending on what type of supply you\u2019re building. The two big ones for low-to-medium power are buck converters and boost converters. Buck is when you need to take a higher input voltage and drop it to a lower, steady output (like 24V in to 5V for a Raspberry Pi). Boost is the opposite: lower input to higher output (like a 3.7V phone battery stepping up to 12V for a car phone charger). For buck converters, you use an N-channel MOSFET \u2013 it\u2019s more efficient, has lower on-resistance (Rds(on)) than P-channel, so less heat. For boost, sometimes you\u2019ll use a P-channel, but a lot of us prefer N-channel with a charge pump driver these days, since N-channel is easier to source and cheaper. Pro tip from the lab: if your design is going to be in a small enclosure with no airflow, stick to topologies that minimize switching losses \u2013 that\u2019s where MOSFET selection hits hard.<\/p>\n

Now, the part that trips everyone up: picking the right MOSFET specs. I see engineers online argue about this all the time, but at the end of the day, it\u2019s about matching the part to your load, not chasing the highest voltage rating just because. Let\u2019s break down the non-negotiables:<\/p>\n

    \n
  1. \n

    Voltage rating (Vds): This has to be at least 20% higher than your maximum input voltage, and if there\u2019s any transient spike (like from an inductive load or input ripple), add another 10%. Why? I\u2019ve had a customer\u2019s design fail because their MOSFET was rated for 25V, and their input spiked to 28V when they turned on a motor. RIP the prototype. So if you\u2019re doing a 12V buck, don\u2019t grab a 20V MOSFET \u2013 get at least 25V, but 30V is safer for most apps. For a boost converter going from 5V to 15V, your MOSFET\u2019s Vds needs to be at least 20V plus the boost voltage, so like 35V minimum. No skimping here.<\/p>\n<\/li>\n

  2. \n

    On-resistance (Rds(on)): This is the big one for efficiency. Rds(on) is how much resistance the MOSFET has when it\u2019s fully on (like, when it\u2019s \u201cclosed\u201d as a switch). Lower Rds(on) means less power lost as heat, which means your supply runs cooler and uses less battery. But here\u2019s the tradeoff: MOSFETs with lower Rds(on) usually cost more and are a bit bigger. So if you\u2019re designing a tiny portable gadget, you might accept a slightly higher Rds(on) to save space, just make sure it\u2019s not so high that your MOSFET overheats at full load. For example, a 10A load: a MOSFET with 0.05\u03a9 Rds(on) would lose 5W as heat (P=I\u00b2R = 10\u00b2*0.05), while one with 0.1\u03a9 would lose 10W. That\u2019s the difference between a warm case and a case you can\u2019t touch. I always tell our customers: calculate your max power loss from Rds(on), then pick a MOSFET that can handle that without exceeding its maximum junction temperature.<\/p>\n<\/li>\n

  3. \n

    Current rating (Id): This is the maximum continuous current the MOSFET can handle. Don\u2019t just match your load current \u2013 add 50% headroom. Why? MOSFET current ratings drop at high temperatures, and if your app has inrush current (like when a motor starts up), that current is way higher than normal. For example, if your load is 5A, don\u2019t get a 5A MOSFET \u2013 get a 7.5A or 10A part. I\u2019ve seen this go wrong too: a drone battery supply that used a 6A MOSFET kept failing when the drone took off, because the inrush current hit 8A and the MOSFET overheated and died. Headroom is your friend.<\/p>\n<\/li>\n<\/ol>\n

    Next up: driving the MOSFET. This is the part most first-timers skip, and it\u2019s why their MOSFET switches slow and get hot. MOSFETs need a gate voltage to turn on \u2013 for N-channel MOSFETs, that\u2019s usually 10V (most are rated for 5V or 10V gate drive, but 10V gives better performance). If your microcontroller or driver chip only outputs 3.3V, you can\u2019t just hook it up directly to the MOSFET gate \u2013 it won\u2019t fully turn on, so Rds(on) will be way higher, leading to heat loss. That\u2019s where a gate driver comes in. For our customers, we usually recommend a simple low-side gate driver for most buck converters \u2013 it\u2019s cheap, small, and does exactly what you need: amplifies the microcontroller\u2019s 3.3V signal to the 10V the MOSFET needs. Pro tip: add a gate resistor (10\u03a9 to 100\u03a9) between the driver and the MOSFET gate. Too small, and you get switching noise that messes up your circuit; too big, and switching is slow and causes losses. I\u2019ve found 22\u03a9 works for 90% of designs.<\/p>\n

    Now, the actual design steps, because specs mean nothing without putting it all together. Let\u2019s walk through a real example: designing a 12V input to 5V, 2A buck converter for a portable sensor.<\/p>\n

    Step 1: Pick the topology \u2013 obvious, it\u2019s a buck converter since we\u2019re stepping down voltage.<\/p>\n

    Step 2: Calculate MOSFET specs. Input is 12V, so Vds needs to be at least 12V * 1.3 = 15.6V, so let\u2019s grab a 20V MOSFET (room for transients). Load is 2A, so Id at least 2A * 1.5 = 3A. Now, Rds(on): we want low heat, so let\u2019s look for a MOSFET with Rds(on) \u2264 0.1\u03a9 at 10V gate drive. That gives us power loss of (2A)\u00b2 * 0.1\u03a9 = 0.4W \u2013 super low, no heat issues.<\/p>\n

    Step 3: Pick the rest of the circuit to match the MOSFET. Buck converters need an inductor and a capacitor too \u2013 but they work with your MOSFET. The inductor needs to handle the same current as your MOSFET plus a bit, and the capacitor smooths the output voltage. A rule of thumb: for 2A output, a 10\u00b5F capacitor works for basic apps, but 22\u00b5F is better for noise. We often recommend our customers pair our MOSFETs with off-the-shelf inductors from reputable suppliers, but if you need a part number, just ask our team \u2013 we have a list of compatible parts.<\/p>\n

    Step 4: Layout matters. Don\u2019t route the power lines next to signal lines \u2013 switching MOSFETs make noise, and that noise can mess up your microcontroller\u2019s readings. Keep the gate drive trace short (under 1cm if possible) to reduce noise, and use a ground plane to dissipate heat. I can\u2019t stress layout enough \u2013 I had a customer who designed a perfect schematic, but their board layout had the power trace running over a signal trace, and the unit kept dropping voltage. We re-spun the layout, and it worked first try. 50% of power supply issues are bad layout, not bad parts.<\/p>\n

    Now, common mistakes I see all the time. Let\u2019s get these out of the way so you don\u2019t make them:<\/p>\n