Friction force calculator
A coefficient of 0.3 and a normal force of 100 N give 30 N of friction: multiply the two to see how hard the surfaces resist sliding, with static or kinetic coefficients alike. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Coefficient of friction μ
- 0.3
- Normal force
- 100
- Friction force
- 30 N
- Precision
- 10
This friction force calculator finds the magnitude of dry friction force when you know the coefficient of friction and the normal force pressing two surfaces together. The definition is the closed form F equals μ times N from the classic Coulomb and Amontons model used in introductory mechanics, statics, and first-order engineering checks. When the normal force is given in newtons, the result is reported in newtons; any consistent force unit works the same way. Zero coefficient or zero normal force is valid and yields zero friction; a negative coefficient or a negative normal force is rejected because those values have no physical meaning in this elementary model. The engine is fully deterministic arithmetic: no network calls, no sampling, and no date-dependent shortcuts.
What friction force means and what you get
In elementary dry-friction models the force that opposes sliding (or impending slide) between two surfaces is proportional to the normal force that presses them together. If μ is the dimensionless coefficient of friction for the material pair and N is the normal force, the friction force magnitude is F equals μ times N. Static friction uses a static coefficient μ_s up to a maximum F_max equals μ_s N at the verge of motion; kinetic friction after slip often uses a kinetic coefficient μ_k with F_k equals μ_k N.
This calculator evaluates that product for whatever non-negative μ you supply, whether you treat it as static or kinetic. It does not choose a regime, solve free-body diagrams, or resolve incline geometry for you: you enter μ and N, and it returns F. Weight on a level surface is a common special case where N equals mg when no other vertical forces act, but you can also pass a measured or free-body normal force that already includes extra loads, lift, or multi-support sharing.
Zero μ or zero N is valid and yields zero friction when both are finite.
Where friction force fits in study, design, and software
Students meet friction force when a textbook introduces statics on rough surfaces, when an incline problem asks for the force that keeps a block from sliding, or when a contest problem gives μ and N and asks for F without a full multi-body simulation. Teachers can pre-generate answer keys for modest μ and N values without trusting opaque calculator apps that silently switch units or confuse weight with normal force.
Developers call the same contract from scripts to seed deterministic test vectors for game-physics demos, to normalize user-entered contact parameters before a free-body diagram, or to satisfy programming-challenge statements that demand newtons rather than a hand-waved sketch. Structural and product first-order checks use F equals μ N when only a coefficient and a support reaction are known before safety factors or multi-axis loads are modeled.
What you can do with it
Homework and lab checks
Compute friction force from μ and normal force before grading worksheets or comparing to force-sensor data.
Design and tutoring software
Normalize user-entered coefficients and contact forces for statics demos, incline helpers, and interactive lessons.
FAQ
What does the friction force calculator cost?
It is free in your browser on this page.
How is friction force defined here?
F = μ · N, where μ is the non-negative coefficient of friction and N is the non-negative normal force. With N in newtons, F is in newtons.
What happens if μ or the normal force is negative?
Negative coefficients and negative normal forces are not accepted in this elementary Coulomb model.
Does this tool distinguish static and kinetic friction?
No. You supply the coefficient that matches your problem (μ_s or μ_k); the calculator only multiplies μ by N.
Why are results rounded to a precision?
Default precision is 10 decimal places; you can set precision from 0 to 15.
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/mech/friction-force \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"mu":0.3,"normal_force":100}'const res = await fetch("https://api.kit.forhosting.com/mech/friction-force", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"mu": 0.3,
"normal_force": 100
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/mech/friction-force",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"mu": 0.3,
"normal_force": 100
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/mech/friction-force", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"mu":0.3,"normal_force":100}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"mu":0.3,"normal_force":100}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/mech/friction-force", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"mu": 0.3,
"normal_force": 100
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "mech.friction_force",
"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.
Limits
max_abs_mu | 1000000 |
max_abs_normal | 1000000000000000 |
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
What friction force means and what the response contains
The response returns the normalized inputs mu and normal_force, the computed friction_force, the precision used, a method tag friction_force, a short formula reminder, and a unit hint N for SI normal-force inputs. There is no numerical contact simulation and no Monte Carlo sampling of asperities: the engine either evaluates the product inside the supported numeric range or rejects the input with invalid_input. Rejected cases include a missing mu or normal_force, non-finite values, magnitudes above the documented ceilings, and any μ or N that is negative, because negative coefficient or negative normal force is not accepted in this calculator.
How μ and N are read and how F stays reproducible
Zero is allowed and returns zero friction force. Supply the contact force in newtons for SI output, or any consistent force unit if you only care about the numeric product; the tool does not convert unit systems for you. Optional leading plus signs and scientific notation on numeric strings are allowed when they parse as finite decimals; embedded spaces and non-numeric tokens are rejected. The preferred field for the coefficient of friction is mu, but aliases coefficient, friction_coefficient, mu_s, and mu_k are accepted so spreadsheets, query strings, and typed forms can reuse the same contract whether the problem labels the value as static or kinetic. μ must be finite and non-negative: a negative value fails with invalid_input and a message that names the field and explains that the coefficient of friction cannot be negative in this calculator, so a bad cell does not become a silent nonsense result. The preferred field for the normal force is normal_force, with aliases N, Fn, normal, and force_normal. Normal force must also be finite and non-negative; a negative value fails with invalid_input naming normal_force. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose for the numeric outputs, defaulting to ten and capped at fifteen so JSON goldens stay stable. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing the friction-force formula yourself.
Where friction force fits in study, design, and software
Product and education tools use the endpoint when a learner types a coefficient and a normal force and the UI must show the friction magnitude. On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result. Pair it with weight-force or average-acceleration helpers when you need related mechanics, and with other math endpoints when you are building a small lab of free, deterministic physics calculators.
Integration use cases
Deterministic test fixtures
Generate reproducible F = μ·N values for unit tests, game-physics demos, and CI assertions.