Metric HP to kW converter
100 PS is exactly 73.549875 kW. Type a metric horsepower rating from a European engine plate, a DIN table or a vehicle brochure and get kilowatts and watts, kept apart from imperial mechanical horsepower. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Metric hp
- 100
- Kw
- 73.549875 kW
- Factor
- 0.73549875
- Watts
- 73,549.875
Need a precise metric horsepower to kilowatts converter for European engine nameplates, DIN ratings, vehicle brochures, or lab worksheets that use PS or CV instead of mechanical horsepower? Enter a non-negative metric horsepower value and get the equivalent power in kilowatts using the exact SI factor one metric horsepower equals seven hundred thirty-five point four nine eight seven five watts.
What this metric HP to kW converter calculates
This tool converts metric horsepower into kilowatts, the SI unit of power used on modern datasheets, grid studies, and efficiency calculations. Metric horsepower—also written as PS (Pferdestärke), CV (chevaux-vapeur or caballos de vapor), ch, or metric hp—is the classical continental engineering unit defined as exactly seventy-five kilogram-force metres per second.
Combined with standard gravity nine point eight zero six six five metres per second squared, that definition yields exactly seven hundred thirty-five point four nine eight seven five watts per metric horsepower, or zero point seven three five four nine eight seven five kilowatts per metric horsepower. The converter multiplies your input by that constant and returns kilowatts, the intermediate wattage, and the factor itself so auditors can recompute every step.
It targets metric horsepower common on European vehicle ratings, DIN engine tables, and industrial motors marked in PS or CV—not mechanical imperial horsepower (about zero point seven four five seven kilowatts), not boiler horsepower, and not the rounded seven-hundred-forty-six-watt electrical convention—because metric-hp-to-kw search intent means the PS/CV definition used on continental nameplates. Zero is accepted as a valid idle or baseline reading; negative values are rejected as invalid input rather than silently flipped.
Distinct landings keep mechanical and metric paths separate so each page, form, and example set stays aligned with how people actually search.
How to get an exact kilowatt figure
In the browser, type the metric horsepower rating and convert instantly with the identical pure function used on the server—no account required for interactive checks, classroom demos, or a quick nameplate translation from a European brochure. Keep the unit meaning explicit in your docs: metric horsepower in, kilowatts out. Status is beta while the public surface stabilizes, but the arithmetic follows fixed SI definitions and will not change for the same inputs.
Prefer this dedicated landing when searchers want metric horsepower to kilowatts rather than a multi-unit Swiss-army converter: the form, title, and examples stay focused on the conversion people actually type into the address bar when they need PS or CV translated to SI power.
What you can do with it
European engine and vehicle nameplates
Translate PS or CV ratings on cars, trucks, and industrial engines into kilowatts for SI datasheets, procurement, and cross-market comparisons.
DIN motor tables and plant sizing
Convert metric horsepower on pumps, compressors, and prime movers to kilowatts before comparing against electrical load schedules.
Homework, labs and documentation
Produce exact metric HP to kW figures for thermodynamics exercises, lab notebooks, and customer-facing specification sheets without rounded rules of thumb.
FAQ
Is this the same as mechanical horsepower (imperial hp)?
No. Mechanical horsepower is about 0.7456998715822702 kW. This tool uses metric PS/CV only. Use the mechanical HP to kW converter when your source means imperial brake horsepower.
What factor does the converter use?
One metric horsepower is exactly 0.73549875 kW, or 735.49875 watts. The value follows from the definition of 75 kilogram-force meters per second and standard gravity of 9.80665 m/s².
How many kW is 100 PS?
100 PS is 73.549875 kW, or 73,549.875 watts. The converter multiplies the rating by the exact factor and shows the watts and the factor too, so every step can be checked.
Is multiplying by three quarters close enough?
For a napkin estimate, perhaps, but such rules drift when you size cabling, compare nameplates across markets or rebuild a spreadsheet that already used the exact PS definition.
Can I enter zero or a negative value?
Zero is accepted as an idle or baseline reading. Negative values are refused as invalid entries instead of having their sign silently flipped.
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/conv/metric-hp-to-kw \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"metric_hp":100}'const res = await fetch("https://api.kit.forhosting.com/conv/metric-hp-to-kw", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"metric_hp": 100
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/metric-hp-to-kw",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"metric_hp": 100
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/metric-hp-to-kw", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"metric_hp":100}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"metric_hp":100}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/metric-hp-to-kw", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"metric_hp": 100
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.metric_hp_to_kw",
"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
Run it free online or call the same pure function through the API at $0.002 per successful request when you need scripted bulk checks and signed results.
How the exact metric factor works and why it matters
Approximate rules of thumb such as multiply by three quarters or use zero point seven three five are fine for napkin estimates, but they drift when you size cabling, compare nameplates across markets, or reproduce a colleague spreadsheet that already used the exact PS definition. Here the factor is fixed from base units: one kilogram-force equals nine point eight zero six six five newtons by the standard gravity definition, and seventy-five of those kilogram-force metres per second define one metric horsepower. Prefer this dedicated path when the source document says PS, CV, or metric horsepower; use the mechanical horsepower converter when the source means imperial brake horsepower. There is no network call, no language model, no Date dependency, and no random seed: the same metric horsepower always yields the same JSON. Invalid requests—missing metric_hp, non-finite values, or negative power—fail with invalid_input and are not billed, because the fault is in the client payload rather than in the service.
Using the free widget, API pricing and delivery
For automation, send a JSON body with the field metric_hp as a non-negative finite number; aliases value, ps, cv, hp_metric, and horsepower are accepted so older forms and spreadsheets map without renaming columns. A successful response includes metric_hp, kw, unit set to kW, the factor zero point seven three five four nine eight seven five, and watts for double-entry audits. Hosted API pricing is a flat $0.002 per successful conversion; validation errors do not consume balance. Integrate one task per rating in a catalog import, or batch from a script that already speaks the KIT task API, webhooks, and signed result links.
Technical questions
What conversion factor does this use?
Exact metric horsepower: 1 metric hp (PS) = 0.73549875 kW (735.49875 W), from 75 kgf·m/s and standard gravity 9.80665 m/s².
How much does the metric HP to kW API cost?
Each successful API call costs $0.002. The same converter runs free in your browser with no account required.
What inputs are rejected?
Missing metric_hp, non-finite values (NaN or Infinity), and negative metric horsepower return invalid_input and are not charged.
Is the result deterministic?
Yes. Pure arithmetic with a fixed SI factor and stable rounding; the same metric_hp always returns the same kw, watts, and factor with no network or randomness.