Convert Kilowatts to Foot-Pounds per Second - Power Converter
This converter transforms power expressed in kilowatts (kW) into foot‑pounds‑force per second (ft·lbf/s). A kilowatt is 1000 watts; a watt is one joule per second. A foot‑pound‑force is a unit of work/energy in customary units and is related to the joule by a fixed conversion constant.
Engineers and technicians commonly use this conversion when exchanging specifications between SI and US customary systems, or when comparing instrument readings expressed in different unit systems. Use the guidance below for correct application and recommended precision in calculations.
Governance
Record 794ea0a749e8 • Reviewed by Fidamen Standards Committee
Interactive converter unavailable for this calculator.
We could not resolve compatible units for this experience. Please verify the slug follows the pattern `from-unit-to-unit-converter`.
Methodology
The conversion uses SI base definitions: 1 watt = 1 joule per second. The relationship between the foot‑pound‑force and the joule is a defined constant established and documented by national metrology institutes.
This tool applies the internationally accepted conversion between joules and foot‑pounds‑force and scales by 1000 to convert kilowatts to watts. Results are numeric transformations only; they do not account for measurement instrument uncertainty or site calibration errors.
Key takeaways
Use ft·lbf/s = kW × 737.5621492772662 for numeric conversion from kilowatts to foot‑pounds‑force per second.
Confirm the number of significant digits and document measurement uncertainty and traceability when results are used for compliance or certification.
Worked examples
Example 1: 1 kW = 1 × 737.5621492772662 = 737.5621492772662 ft·lbf/s (round to appropriate sig figs as needed).
Example 2: 0.5 kW = 0.5 × 737.5621492772662 = 368.7810746386331 ft·lbf/s.
F.A.Q.
Why use 1000 in the calculation?
A kilowatt is defined as 1000 watts. The intermediate step converts the kilowatt input into watts so the watt→ft·lbf/s conversion constant can be applied.
How many significant digits should I show?
Report results with precision appropriate to your input data and instrument uncertainty. For typical engineering work, 3–6 significant digits are common. For regulatory or metrology work, follow the significant‑figure rules in the applicable standard and include measurement uncertainty.
Is foot‑pound‑force the same as foot‑pound used for torque?
Foot‑pound‑force (ft·lbf) denotes an energy or work unit (force × distance). Torque is sometimes given in ft·lb and can be numerically identical but conceptually different because torque is a moment. Ensure contextual correctness when converting or labeling units.
Does this conversion include measurement uncertainty or calibration adjustments?
No. This converter applies exact unit relationships per published constants. It does not account for instrument calibration errors, traceability, or site‑specific measurement uncertainty. For compliance testing or metrology, document uncertainty and traceability per relevant standards.
Which standard defines these unit relationships?
Unit relationships used here follow international metrology guidance and recommended constants from national metrology authorities and international standards bodies; see the citations for authoritative sources.
Sources & citations
- NIST Reference on Units and Constants — https://physics.nist.gov/cuu/Units/units.html
- ISO 80000 Quantities and Units (overview) — https://www.iso.org/standard/30669.html
- IEEE Standards Collection (standards body site) — https://standards.ieee.org
- OSHA Electrical Standards and Guidance — https://www.osha.gov/laws-regs/regulations/standardnumber/1910
- NIST SP 811 — Guide for the Use of the International System of Units — https://www.nist.gov/pml/special-publication-811
Further resources
Related tools
Versioning & Change Control
Audit record (versions, QA runs, reviewer sign-off, and evidence).
Record ID: 794ea0a749e8What changed (latest)
v1.0.0 • 2025-11-20 • MINOR
Initial publication and governance baseline.
Why: Published with reviewed formulas, unit definitions, and UX controls.
Public QA status
PASS — golden 25 + edge 120
Last run: 2026-01-23 • Run: golden-edge-2026-01-23
Versioning & Change Control
Audit record (versions, QA runs, reviewer sign-off, and evidence).
What changed (latest)
v1.0.0 • 2025-11-20 • MINOR
Initial publication and governance baseline.
Why: Published with reviewed formulas, unit definitions, and UX controls.
Public QA status
PASS — golden 25 + edge 120
Last run: 2026-01-23 • Run: golden-edge-2026-01-23
Engine
v1.0.0
Data
Baseline (no external datasets)
Content
v1.0.0
UI
v1.0.0
Governance
Last updated: Nov 20, 2025
Reviewed by: Fidamen Standards Committee (Review board)
Credentials: Internal QA
Risk level: low
Reviewer profile (entity)
Fidamen Standards Committee
Review board
Internal QA
Entity ID: https://fidamen.com/reviewers/fidamen-standards-committee#person
Semantic versioning
- MAJOR: Calculation outputs can change for the same inputs (formula, rounding policy, assumptions).
- MINOR: New features or fields that do not change existing outputs for the same inputs.
- PATCH: Bug fixes, copy edits, or accessibility changes that do not change intended outputs except for previously incorrect cases.
Review protocol
- Verify formulas and unit definitions against primary standards or datasets.
- Run golden-case regression suite and edge-case suite.
- Record reviewer sign-off with credentials and scope.
- Document assumptions, limitations, and jurisdiction applicability.
Assumptions & limitations
- Uses exact unit definitions from the Fidamen conversion library.
- Internal calculations use double precision; display rounding follows the unit's configured decimal places.
- Not a substitute for calibrated instruments in regulated contexts.
- Jurisdiction-specific rules may require official guidance.
Change log
v1.0.0 • 2025-11-20 • MINOR
Initial publication and governance baseline.
Why: Published with reviewed formulas, unit definitions, and UX controls.
Areas: engine, content, ui • Reviewer: Fidamen Standards Committee • Entry ID: 4b49a082b301
