Titration unknown concentration
25 mL of 0.1 N titrant that neutralizes a 50 mL sample means the sample is 0.05 N. Enter the titrant normality, the titrant volume at the end point and the sample volume, in any one volume unit, and get the unknown normality. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Titrant normality
- 0.1
- Titrant volume
- 25
- Analyte volume
- 50
- N1
- 0.1
- V1
- 25
- V2
- 50
- Analyte normality
- 0.05
Students, lab technicians, and automation scripts need that rearrange as a deterministic contract: three finite numbers in, one normality out, and a hard failure when the sample volume is zero so division by zero never looks like a successful zero result. Use any consistent volume unit for V1 and V2—milliliters with milliliters or liters with liters—because the ratio cancels the unit as long as both volumes match.
What N1·V1 = N2·V2 means in a normality titration
Equivalents from the titrant equal N1 times V1 when volumes are expressed in liters (or any proportional unit pair that keeps N1 V1 dimensionally consistent with N2 V2). Equivalents in the sample equal N2 times V2. Setting those products equal yields the textbook identity N1 V1 equals N2 V2.
Solving for the unknown sample normality produces N2 equals N1 times V1 divided by V2. This form is exactly what many introductory labs write on the board for acid-base, redox, or precipitation titrations when both sides are already stated in normality rather than molarity and stoichiometric coefficients. Volumes must share one unit; normality is reported in the same eq/L scale as the titrant normality you supply.
If your method is defined with milliequivalents and milliliters, the numerical product still balances, so you may enter milliliters for both volumes without converting to liters first.
Where a normality titration calculator earns its keep
Teaching labs use an unknown-concentration titration calculator so students can check N2 from recorded burette and pipette volumes without hand-calculator slips on the division. Exam generators need a deterministic oracle that marks zero sample volume as invalid instead of silently returning infinity or NaN. Failed validation does not consume balance.
Keep volumes in one unit family, pin the rounded n2 field in tests, and you get reproducible normality for homework, LMS plugins, LIMS hooks, and edge workers without standing up a full analytical-chemistry stack of your own.
What you can do with it
QC and LIMS batch rows
Attach analyte normality to each titration record from stored N1, V1, and V2 without embedding a chemistry library in the pipeline.
Homework and LMS auto-grading
Mark normality titration items with a deterministic oracle that rejects zero analyte volume and returns a stable rounded N2.
FAQ
Do V1 and V2 need to be in liters?
No. Use any consistent volume unit for both (for example both in mL). Normality products balance as long as V1 and V2 share the same unit.
Is this the same as a C1V1=C2V2 dilution calculator?
No. Dilution conserves solute when you add solvent.
What happens if the sample volume is zero?
The calculator rejects it, because the result divides by the sample volume and a zero would only produce an infinite, meaningless number. A negative sample volume is refused too, and the titrant normality must be greater than zero.
Does it work for redox and precipitation titrations?
Yes, as long as both concentrations are expressed as normality. The equality of equivalents at the end point holds for acid-base, redox and precipitation titrations alike, which is why many introductory labs write it on the board for all three.
Which volume is the titrant and which is the sample?
The titrant volume is what you delivered from the burette up to the end point, and the sample volume is the measured portion you titrated, usually pipetted. Swapping them inverts the ratio and gives a wrong normality.
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/chem/normality-titration \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"titrant_normality":0.1,"titrant_volume":25,"analyte_volume":50}'const res = await fetch("https://api.kit.forhosting.com/chem/normality-titration", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"titrant_normality": 0.1,
"titrant_volume": 25,
"analyte_volume": 50
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/chem/normality-titration",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"titrant_normality": 0.1,
"titrant_volume": 25,
"analyte_volume": 50
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/chem/normality-titration", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"titrant_normality":0.1,"titrant_volume":25,"analyte_volume":50}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"titrant_normality":0.1,"titrant_volume":25,"analyte_volume":50}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/chem/normality-titration", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"titrant_normality": 0.1,
"titrant_volume": 25,
"analyte_volume": 50
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "chem.normality_titration",
"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
When a standardized titrant of known normality is run into a measured volume of sample until the endpoint, the classical normality relation N1 times V1 equals N2 times V2 gives the unknown analyte normality without a full mole-ratio setup. This titration unknown concentration calculator accepts titrant normality N1, titrant volume V1 at the endpoint, and analyte volume V2, returns N2 equals N1 V1 over V2 with equation and step strings, and rejects zero analyte volume with invalid_input.
What N1·V1 = N2·V2 means in a normality titration
Normality expresses concentration in equivalents per liter, so at the titration endpoint the number of equivalents delivered by the titrant must equal the number of equivalents present in the analyte aliquot. It is not a dilution formula: C1 V1 equals C2 V2 describes diluting a stock solution, whereas N1 V1 equals N2 V2 here describes chemical consumption at the endpoint between titrant and analyte. Keeping the names titrant and analyte in the API fields makes that lab context explicit and avoids mixing this endpoint with a general dilution solver.
Input contract, response shape, and zero-volume errors
Titrant normality must be strictly positive. Titrant volume must be non-negative. Negative analyte volume is also rejected as non-physical for this calculation. Example: N1 equals 0.1 normal, V1 equals 25 milliliters of titrant, V2 equals 50 milliliters of sample yields N2 equals 0.05 normal, because 0.1 times 25 over 50 equals 0.05. POST a JSON body with three required finite numbers: titrant_normality (N1, aliases n1, N1, normality_titrant), titrant_volume (V1, aliases v1, V1, volume_titrant), and analyte_volume (V2, aliases v2, V2, volume_analyte). Each field may arrive as a JSON number or as a numeric string; non-finite values, missing fields, and empty strings fail with invalid_input naming the field. On success the body echoes the three inputs as titrant_normality, titrant_volume, and analyte_volume (plus short n1, v1, v2 keys), returns analyte_normality and n2 rounded to twelve decimal places for stable goldens, and includes formula, rearrange, equation, product_n1v1, product_n2v2, a short message, and ordered steps that restate the substitution. Pair the numeric result with your own lab notebook units; this endpoint does not convert between milliliters and liters or between normality and molarity.
Where a normality titration calculator earns its keep
Quality-control scripts that already store standardized titrant normality and endpoint volume can call a tiny parse API to attach analyte normality to each batch row without embedding chemistry libraries. If you later need molarity, convert with the reaction’s equivalent factor outside this endpoint; this capability stays focused on the normality product rule alone.
Integration use cases
Teaching lab endpoint checks
Students enter standardized titrant normality, burette volume at the color change, and pipette sample volume to verify the analyte normality from N1V1=N2V2.
Technical questions
How do I calculate analyte normality from a titration?
Send titrant_normality (N1), titrant_volume (V1), and analyte_volume (V2). The API returns N2 = N1·V1/V2 from the normality equation N1·V1 = N2·V2.
What happens if analyte volume is zero?
The task fails with invalid_input. Solving for N2 would divide by zero when V2 is zero, so the request is rejected and not billed.
What does the titration unknown concentration calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.