Convert Feet to Meters – Length Converter
This converter transforms a length in feet (ft) to meters (m) using the internationally agreed conversion factor. It is intended for quick conversions, engineering checks, and everyday use where unit consistency is required.
The numeric conversion factor used here is exact by definition; guidance on rounding, measurement uncertainty, and traceability is provided to help you choose an appropriate display precision for your application.
Governance
Record 50750e8f4f7c • Reviewed by Fidamen Standards Committee
Interactive Converter
Convert between foot and meter with precision rounding.
Quick reference table
| Foot | Meter |
|---|---|
| 1 ft | 0.3048 m |
| 5 ft | 1.524 m |
| 10 ft | 3.048 m |
| 25 ft | 7.62 m |
| 50 ft | 15.24 m |
| 100 ft | 30.48 m |
Methodology
The conversion uses the fixed relationship between the foot and the metre established by international agreement. The metre is the SI base unit of length and the relationships among customary units are maintained for compatibility with SI.
For measurement traceability and notation guidance we reference national and international standards. Use calibrated instruments and documented procedures when measurements affect safety, compliance, or contractual obligations.
Key takeaways
Multiply feet by 0.3048 to obtain metres. The factor 0.3048 is exact by international definition; round results according to the required measurement precision.
When converting measurements that originated from physical instruments, include instrument uncertainty and calibration records for any regulated, safety-critical, or contractual work.
Worked examples
5 ft → 5 × 0.3048 = 1.524 m
6 ft 2 in: convert inches to feet first (6 + 2/12 = 6.1666667 ft) → 6.1666667 × 0.3048 ≈ 1.87962 m
0.1 ft → 0.1 × 0.3048 = 0.03048 m
F.A.Q.
Is 1 foot equal to exactly 0.3048 meters?
Yes. By international agreement the inch is defined as exactly 0.0254 metres, making one foot exactly 0.3048 metres. The conversion factor is exact; uncertainty comes from how the input value was measured or rounded.
How many decimal places should I show?
Depends on context. For simple everyday use 2–3 decimal places are usually fine. For engineering or surveying tasks 3–6 decimal places may be appropriate. For legal or safety-critical contexts, follow the precision specified in contracts or standards and include measurement uncertainty.
Why do two calculators give slightly different results?
Differences usually stem from display rounding or from how the input was entered (for example, converting feet and inches vs entering feet as a decimal). The underlying exact factor is the same; check input format and rounding rules.
Can I convert very large or very small values?
Yes, but beware of floating-point precision limits in software. For extremely large or precise values use software or libraries that support arbitrary precision arithmetic and keep track of significant figures and instrument uncertainty.
Do standards or regulators require calibration or documentation?
Standards bodies and regulators recommend or require traceable calibration of measurement instruments for regulated work. Maintain calibration certificates and follow relevant guidance when measurements affect compliance, safety, or contracts.
How do I convert from feet and inches?
Convert inches to feet first by dividing inches by 12, add to feet, then multiply the total feet by 0.3048 to get metres.
Sources & citations
- NIST Special Publication 811 - Guide for the Use of the International System of Units (SI) — https://www.nist.gov/pml/special-publication-811
- ISO 80000 series - Quantities and units (overview) — https://www.iso.org/standard/70042.html
- IEEE Standards Association (standards and best practices) — https://standards.ieee.org/
- OSHA - Occupational Safety and Health Administration — https://www.osha.gov
- BIPM SI Brochure (9th edition, 2019) — https://www.bipm.org/en/publications/si-brochure
Further resources
Related tools
External guidance
Versioning & Change Control
Audit record (versions, QA runs, reviewer sign-off, and evidence).
Record ID: 50750e8f4f7cWhat changed (latest)
v1.0.0 • 2025-11-27 • 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-27 • 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 27, 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-27 • 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: 06c0877a181c
