Solar Generator Runtime: How Long Will Yours Actually Run?
What Does "Solar Generator Runtime" Actually Mean?
"Runtime" is a simple question with a deceptively complicated answer: how long will this specific unit keep this specific device running before it needs a recharge? That's different from the question our buying guide and sizing guide answer — those help you decide how much capacity to buy. This guide assumes you already have a number in mind (or a unit sitting on the shelf) and want to know what it will realistically do.
Runtime depends on three things working together: how much energy is stored (watt-hours), how much power your device pulls (watts), and how much of that stored energy is actually usable once real-world losses are accounted for. Get any one of those wrong and the runtime estimate falls apart — which is exactly why so many "solar generator runtime" answers online oversimplify.
The Runtime Formula — and Why It's Only a Starting Point
The basic formula almost every manufacturer and reviewer uses is:
Runtime (hours) ≈ Usable battery capacity (Wh) ÷ Device power draw (W)
For example, a 1,000Wh battery running a 50W device works out to roughly 1,000 ÷ 50 = 20 hours before accounting for any losses. That number is a ceiling, not a realistic estimate, because it assumes:
100% usable capacity — in reality, inverter conversion and battery-management overhead typically leave you with somewhere around 85–90% of the rated Wh figure actually available.
A perfectly flat, constant load — most real devices don't draw exactly one wattage the whole time (a refrigerator's compressor cycles on and off; a laptop draws more under load than idle).
No temperature effect — lithium batteries deliver less usable capacity in cold conditions.
No battery aging — capacity degrades gradually over hundreds to thousands of charge cycles.
No solar input during use — the plain formula assumes the battery is only ever draining, never simultaneously recharging.
A more honest version of the formula builds in an efficiency factor:
Runtime (hours) ≈ (Battery capacity (Wh) × usable-efficiency factor) ÷ Device power draw (W)
Using roughly 0.85 as a reasonable usable-efficiency planning assumption, that same 1,000Wh/50W example becomes (1,000 × 0.85) ÷ 50 ≈ 17 hours — about 15% lower than the naive calculation. Treat every runtime figure in this guide, including that one, as a planning estimate, not a guarantee for your specific unit or device.
Table 1 below breaks down exactly what feeds into that formula.
| Factor | Typical Real-World Range | Effect on Runtime |
|---|---|---|
| Usable capacity vs. rated Wh | ~85–90% of rated capacity | Reduces runtime below the naive Wh ÷ W figure |
| Device power draw | Varies by device; check nameplate | Larger denominator = shorter runtime |
| Cycling / duty cycle (fridges, ACs) | Compressor often runs ~1/3 of the time | Average effective draw is much lower than peak nameplate watts |
| Ambient temperature | Cold reduces usable lithium capacity | Can meaningfully shorten runtime in cold conditions |
| Battery age / cycle count | Gradual capacity loss over hundreds–thousands of cycles | Slightly shortens runtime over the unit's lifespan |
| Solar input while in use | Depends on panel wattage, sun, and input cap | Can extend runtime, or make it indefinite while sun holds |
Common Appliance Wattages
Before you can estimate runtime for anything, you need a realistic wattage figure — and this is where a lot of DIY calculations go wrong, because a device's running wattage, its startup surge, and its actual daily draw (for anything that cycles on and off) are three different numbers.
Table 2 is a reference table of typical wattages for devices people most often ask about running from a solar generator. These are general planning ranges based on commonly published appliance data, not measurements of any specific product — always check your own device's nameplate or manual for its actual rating.
| Device | Running Watts* | Startup Surge | Notes |
|---|---|---|---|
| LED light bulb | 5–10W | None | Very low, steady draw |
| Wi-Fi router/modem | 10–20W | None | Continuous 24/7 draw |
| Smartphone charging | 5–10W | None | Only draws while actively charging |
| Laptop | 30–65W | None | Higher under heavy processing load |
| CPAP (no humidifier) | 30–60W | None | Steady overnight draw; check your model |
| Flat-screen TV | 80–150W | None | Varies by screen size/type |
| Box/window fan | 50–100W | Minimal | Higher on max speed |
| Mini-fridge / cooler | 50–100W running | 150–300W | Cycles on/off; use average effective draw for runtime math |
| Standard refrigerator | 100–250W while running | 800–1,200W | Compressor cycles ~1/3 of the time on average |
| Microwave | 600–1,200W | Minimal beyond running watts | Minutes of use, not hours |
| Coffee maker | 900–1,200W | Minimal | Short brew cycle |
| Blender | 300–1,000W | Minimal | Short bursts |
| Small space heater | 750–1,500W | Minimal | High continuous draw if run for hours |
| Portable air conditioner | 500–1,500W | Can exceed running watts | Cycles like a refrigerator |
| Corded power tool | 600–1,500W | Can be significantly higher | Intermittent, short-duration use |
*General planning ranges based on commonly published appliance data, not measurements of any specific product. Always check your device's nameplate or manual.
A few things worth flagging from that table:
Cycling appliances (refrigerators, mini-fridges, portable ACs) are the trickiest. Their nameplate wattage is what the compressor draws while running, not a continuous draw. The U.S. Department of Energy's own consumer guidance on refrigerator energy use notes that a compressor typically runs only a fraction of the time the unit is plugged in — commonly cited as roughly one-third — which is why we use an "average effective wattage" for these devices in the runtime tables below, rather than their peak nameplate number.
Startup surge matters even when it doesn't affect runtime math. A device can have plenty of energy available in the battery and still fail to start if the generator's surge rating doesn't cover that brief spike. Runtime and "will it start at all" are two separate checks.
High-draw, short-duration devices (microwaves, kettles, coffee makers, hair dryers) aren't meant to run for hours — their "runtime" numbers below are really a budget of total available minutes across a day, not a realistic single session.
Runtime by Battery Capacity: The Master Reference Table
This is the core reference for the whole article: given a battery capacity you already have (or are considering), how long will it run a device at a given wattage? Table 3 applies the efficiency-adjusted formula above across seven common capacity tiers and five representative load levels.
| Capacity | 10W Load | 50W Load | 100W Load | 200W Load | 500W Load |
|---|---|---|---|---|---|
| 300Wh | 25.5 | 5.1 | 2.6 | 1.3 | 0.5 |
| 500Wh | 42.5 | 8.5 | 4.3 | 2.1 | 0.9 |
| 1,000Wh | 85.0 | 17.0 | 8.5 | 4.3 | 1.7 |
| 1,500Wh | 127.5 | 25.5 | 12.8 | 6.4 | 2.6 |
| 2,000Wh | 170.0 | 34.0 | 17.0 | 8.5 | 3.4 |
| 3,000Wh | 255.0 | 51.0 | 25.5 | 12.8 | 5.1 |
| 5,000Wh | 425.0 | 85.0 | 42.5 | 21.3 | 8.5 |
*Assumes ~85% usable efficiency after inverter and battery-management losses. Treat as a planning estimate, not a guarantee for any specific unit.
Read this table as "if my total simultaneous load is roughly X watts, my Y-Wh unit gives me about Z hours" — then cross-reference Table 2 to see which of your specific devices land near each load tier.
How Long Will It Run This? Appliance-Specific Runtime Examples
Generic wattage tiers are useful, but most people asking about runtime have a specific device in mind. Table 4 applies the same formula to the devices people search for most.
| Device (avg. effective W) | 500Wh | 1,000Wh | 2,000Wh | 3,000Wh |
|---|---|---|---|---|
| Wi-Fi router (15W) | 28.3 | 56.7 | 113.3 | 170.0 |
| CPAP, no humidifier (45W) | 9.4 | 18.9 | 37.8 | 56.7 |
| Laptop (50W) | 8.5 | 17.0 | 34.0 | 51.0 |
| Box fan (75W) | 5.7 | 11.3 | 22.7 | 34.0 |
| Standard TV (100W) | 4.3 | 8.5 | 17.0 | 25.5 |
| Refrigerator (~65W avg., cycling) | 6.5 | 13.1 | 26.2 | 39.2 |
| Microwave (900W) | 0.5 | 0.9 | 1.9 | 2.8 |
| Small space heater (1,200W) | 0.4 | 0.7 | 1.4 | 2.1 |
*Assumes ~85% usable efficiency. Refrigerator and other cycling-appliance figures use average effective wattage (accounting for compressor duty cycle), not peak nameplate wattage. Individual devices vary — check your own model.
A few notes on the appliances that generate the most questions:
Refrigerators. Because a refrigerator's compressor cycles rather than running continuously, its effective draw (averaged across a full day) is much lower than its nameplate wattage — commonly landing somewhere around 60–70W of average draw for a standard fridge, even though the compressor itself might pull 150–250W while actively running. That's why a 2,000Wh unit can realistically stretch to somewhere in the neighborhood of a full day of refrigerator coverage, even though a naive calculation using the nameplate wattage would suggest far less. Your specific refrigerator's efficiency, age, ambient temperature, and how often the door opens will shift this meaningfully in either direction — the energy-guide label on the appliance itself (a more precise annual kWh figure) is a better input than any generic estimate if you want a tighter number.
CPAP machines. Most CPAP units without a heated humidifier draw a fairly steady 30–60W, which is why they're one of the more predictable devices to estimate — and why even a modest capacity unit can comfortably cover a full night. Adding a heated humidifier or heated tubing increases draw meaningfully; check your specific machine's manual rather than assuming the "no humidifier" figure applies. This is general planning information, not medical guidance — for anything related to a specific medical device's power requirements, confirm directly with the manufacturer or your equipment provider.
TVs, laptops, and routers. These are the most predictable devices on this list because they draw a fairly flat wattage with no real startup surge, which means the simple formula holds up better here than almost anywhere else in this guide.
Microwaves, space heaters, and portable ACs. These are the appliances where people most overestimate runtime, because they're used to thinking in "hours" and these devices are realistically a "minutes" category — a 3,000Wh unit gives you a meaningful budget of total minutes across a day, not a multi-hour single session.
Solar-Assisted Runtime: The Section Most Runtime Guides Skip
Every runtime discussion above assumes the battery is only draining. But if solar panels are actively charging the unit while it's powering something, the effective drain rate drops — and if solar input is high enough relative to the load, the unit can run indefinitely as long as that sunlight holds, rather than eventually running the battery down.
Battery-only runtime is what the formula above calculates: stored energy divided by load, full stop.
Solar-assisted runtime subtracts the effective solar contribution from the load before dividing:
Solar-assisted runtime (hours) ≈ (Battery capacity (Wh) × efficiency factor) ÷ (Device load (W) − effective solar input (W))
The tricky part is "effective solar input" — it is not simply your panel's rated wattage. A panel's rated output assumes near-ideal sunlight; real-world output depends on weather, panel angle, time of day, and your local peak-sun-hours (a standard metric published by the National Renewable Energy Laboratory that expresses how much usable sunlight a location gets, distinct from simple daylight hours). Depending on region, U.S. locations commonly see somewhere in the range of roughly 3 to 6 peak sun hours per day on average — meaning a panel rarely delivers its full rated wattage for more than a portion of the daylight hours, and your unit's solar-input cap (discussed in the buying guide) further limits how much of that panel output the battery can actually accept at once.
Table 5 illustrates the difference using conservative, clearly-labeled example solar contributions rather than assuming a panel always delivers its rated wattage.
| Capacity | Combined Load | Battery-Only Runtime | +100W Effective Solar | +300W Effective Solar |
|---|---|---|---|---|
| 1,000Wh | 300W | 2.8 hours | 4.3 hours (+52%) | Runs indefinitely while sun holds |
| 2,000Wh | 300W | 5.7 hours | 8.5 hours (+49%) | Runs indefinitely while sun holds |
| 2,000Wh | 500W | 3.4 hours | 4.3 hours (+26%) | 8.5 hours (+150%) |
*"Effective solar" is the realistic average power a connected panel contributes under actual sun/weather conditions — not its rated wattage — and is capped by the unit's solar-input rating. When effective solar input meets or exceeds the load, the battery stops net-draining rather than reaching a specific "extra hours" number.
The practical takeaway: if your effective solar input is lower than your device's load, solar recharging extends runtime — sometimes substantially — but the battery is still net-draining, just more slowly. If effective solar input meets or exceeds the load, the unit can run indefinitely as long as that sunlight level holds, because it's no longer drawing down stored capacity at all. This is the single most useful distinction for anyone planning off-grid, camping, or extended-outage use, and it's the reason two units with identical battery capacity can behave very differently in practice depending on their solar-input rating and how much panel wattage is actually connected.
How to Calculate Your Own Runtime: A Step-by-Step Method
Confirm your unit's rated battery capacity (Wh). Check the spec sheet, not a rounded marketing number.
Apply a realistic usable-efficiency factor. Roughly 85% is a reasonable general planning assumption absent more specific manufacturer guidance.
Identify your device's actual wattage. Use the nameplate or manual, not a generic chart, whenever possible — especially for anything with a compressor or motor, where nameplate and average effective draw can differ significantly.
For cycling appliances, estimate average effective wattage, not peak wattage. A refrigerator or portable AC's peak running wattage overstates its 24-hour average draw considerably.
Divide usable Wh by device wattage to get battery-only runtime.
If solar panels will be connected and producing power during use, estimate your effective solar contribution (panel wattage × a conservative sun-condition factor, capped by your unit's solar-input rating) and subtract it from the device wattage before dividing, per the solar-assisted formula above.
Cross-check the result against the unit's continuous output rating, not just its battery capacity — a runtime estimate is meaningless if the device's wattage exceeds what the unit can even output continuously in the first place.
Real-World Runtime Scenarios
Scenario 1 — Refrigerator during an outage. A 2,000Wh unit, refrigerator averaging roughly 65W effective draw (accounting for compressor cycling): (2,000 × 0.85) ÷ 65 ≈ 26 hours of battery-only runtime — a bit over a full day, consistent with the general "2,000Wh ≈ roughly a day of fridge coverage" reference point used elsewhere on this site, though your specific refrigerator's efficiency will shift this.
Scenario 2 — Wi-Fi, phones, lights, and a laptop. Router (15W) + three LED lights (24W combined) + occasional laptop use (50W) ≈ 89W combined when everything runs at once: (1,000 × 0.85) ÷ 89 ≈ 9.5 hours on a 1,000Wh unit if all four ran continuously and simultaneously — realistically longer, since the laptop and lights won't be on every single hour.
Scenario 3 — Camping. A 500Wh unit running a fan (75W) most of the evening plus occasional phone and light use, averaging roughly 90W combined: (500 × 0.85) ÷ 90 ≈ 4.7 hours of that combined load — enough for an evening, not an unattended overnight run at that combined wattage.
Scenario 4 — CPAP overnight. A 600Wh unit, CPAP at 45W (no humidifier): (600 × 0.85) ÷ 45 ≈ 11.3 hours — comfortably more than a typical night's sleep, with margin for a humidifier adding some draw.
Scenario 5 — Essential home backup. A 3,000Wh unit running a refrigerator (65W effective) plus router (15W) plus a few lights (16W) simultaneously ≈ 96W combined: (3,000 × 0.85) ÷ 96 ≈ 26.6 hours — again, roughly a day-plus, with the caveat that this treats the combined load as constant, when in practice the fridge's compressor isn't always running alongside everything else.
Scenario 6 — Solar recharging while running. Same 3,000Wh setup as Scenario 5 (96W combined load), now with roughly 150W of effective solar contribution during daylight hours (a realistic planning figure for a mid-sized panel setup in decent sun, well under most panels' full rated wattage): effective solar input already exceeds the 96W load, so during those daylight hours the unit is net-charging, not net-draining — extending real-world coverage well beyond the 26.6-hour battery-only estimate, with the exact extension depending on how many hours of that solar level you actually get per day.
Common Runtime-Calculation Mistakes
Using nameplate wattage for cycling appliances instead of average effective draw. This is the single most common error, and it can overstate a refrigerator's or portable AC's real energy consumption by several times.
Ignoring the efficiency factor entirely. Treating rated Wh as 100% usable inflates every runtime estimate.
Assuming a solar panel delivers its full rated wattage all day. Real-world output is lower, and variable, almost all the time.
Forgetting the unit's continuous output cap. A large battery paired with a device that exceeds the unit's continuous wattage rating won't run at all, regardless of how the Wh math looks.
Treating a single worked example as universal. Every appliance-runtime figure — including every one in this article — is a planning estimate for a representative wattage, not a guarantee for your specific model, age, ambient temperature, or usage pattern.
Skipping surge requirements when a device does start successfully at first. A unit can sometimes start a compressor-based appliance under favorable conditions and fail to on a hotter day or when the battery is partially depleted — surge headroom matters throughout the runtime, not just at the first startup.
| Device Type | Runtime Math Sufficient? | Also Check |
|---|---|---|
| Lights, routers, laptops, phones | Yes | Nothing extra — flat, predictable draw |
| CPAP, fans, small electronics | Yes | Nothing extra in most cases |
| Refrigerators, freezers, portable ACs | No | Surge rating must cover compressor startup, not just runtime |
| Power tools, well pumps | No | Surge rating; also confirm continuous output isn't exceeded mid-use |
| Microwaves, heaters, kettles | Partially | Confirm continuous output covers the running wattage even for short use |
How Runtime Should Inform Which Generator You Choose
If the runtime numbers above are shorter than you need for your actual situation, that's a sizing decision, not a runtime one — head over to our solar generator buying guide for the full step-by-step sizing process, or What Size Solar Generator Do I Need? for a device-by-device sizing calculator. If you're comparing specific current models against these runtime expectations, the Best Solar Generators comparison covers seven current units across capacity classes with verified specifications. And if you're still deciding between a solar generator and a traditional fuel-based one for extended, multi-day scenarios where recharging access is uncertain, Solar Generator vs. Gas Generator walks through that trade-off directly.
FAQ
"1,000W" describes output (what it can power at once), not runtime — runtime depends on the unit's watt-hour battery capacity relative to your device's wattage, not its output rating alone. Check the Wh figure and use the formula in this guide.
It depends entirely on the load. At roughly 85% usable efficiency, a 1,000Wh unit runs a 50W device for about 17 hours, a 100W device for about 8.5 hours, and a 500W device for under 2 hours — see Table 3 for more load levels.
Using average effective draw (accounting for compressor cycling, roughly 60–70W average for a standard fridge), a 2,000Wh unit works out to somewhere around a day of coverage — though your specific refrigerator's efficiency and cycling behavior can shift this meaningfully.
A typical flat-screen TV draws roughly 80–150W. On a 1,000Wh unit, that works out to somewhere in the range of 6–10 hours, depending on the exact set.
For low-draw overnight devices like a CPAP (30–60W) or a few lights and a router, even a 500–1,000Wh unit typically covers a full night comfortably — see the CPAP scenario above for a worked example.
A battery-only unit can't run indefinitely — it will eventually deplete based on the runtime math above. If solar panels are connected and contributing more power than the load requires, the unit can effectively run indefinitely while that sunlight level holds, because it stops net-draining the battery.
Yes — most solar generators can charge and discharge simultaneously. Whether that meaningfully extends runtime depends on how much effective solar power is coming in relative to the load; see the battery-only vs. solar-assisted comparison above.
Divide usable battery capacity (rated Wh × roughly 0.85 for typical efficiency losses) by your device's wattage. For cycling appliances, use average effective wattage rather than peak nameplate wattage. See the step-by-step method above for the full process, including how to factor in solar input.
For the same device and load, yes — more stored energy means more runtime, all else equal. But a bigger battery doesn't help if the unit's continuous output rating can't handle the device in the first place, and it doesn't change how efficiently that energy is used.
Watts measure the rate of power draw at a given moment; watt-hours measure total stored or consumed energy over time (watts × hours). Runtime calculations always divide a Wh figure by a W figure.
Enough effective solar input to offset your device's load, if you want the runtime to stop shrinking rather than just shrink more slowly. Effective input depends on panel wattage, sun conditions, and your unit's solar-input cap — not the panel's rated wattage alone.
