Calibration curve calculator
Turn five standards from 0 to 4, with readings from 0.01 to 0.81, into a calibration line with a slope of 0.2, an intercept of 0.01 and an R² of 1. Enter concentration and response for each standard. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
A linear calibration curve is the everyday contract between a set of prepared standards and the numbers an instrument actually reports. Spectrophotometers, HPLC detectors, GC-FID channels, ion-selective electrodes, and plate readers all need a slope and an intercept so a later sample response can be turned into concentration with a documented line. This calculator accepts rows of standard concentration and matching instrument response, fits ordinary least squares, and returns slope, intercept, and R-squared together with the explicit equation response equals slope times concentration plus intercept.
What a linear calibration curve is and how least squares finds slope and intercept
In analytical chemistry a calibration curve is the empirical relationship between known standard concentrations and the instrument responses those standards produce under a fixed method. For many assays that relationship is linear over a working range: absorbance versus concentration in Beer's law, peak area versus milligrams per litre in chromatography, or millivolts versus ion activity on a short stretch of a Nernst plot that you have already linearized. Ordinary least squares is the textbook estimator.
Place concentration on the independent axis and response on the dependent axis. Compute the mean of each series, then Sxx as the sum of squared deviations of concentration from its mean and Sxy as the sum of the products of those deviations with the matching response deviations. Slope is Sxy divided by Sxx.
Intercept is the mean response minus slope times the mean concentration. The fitted line is then response equals slope times concentration plus intercept. R-squared is one minus the residual sum of squares over the total sum of squares of response: it is the fraction of response variation captured by that line, not a proof that the method is valid.
Two distinct concentrations are the mathematical minimum because a unique finite slope needs non-zero variance in x. Replicates at a single level, a lone blank, or a list of identical x values do not define a calibration line. This tool applies that definition exactly: it does not weight residuals, it does not force the intercept through zero, and it does not invent extra standards.
Supply the rows you actually ran, require distinct concentrations, and read slope, intercept, and R-squared as the documented linear calibration.
Where a calibration curve calculator is used, pricing, and practical limits
Teaching labs use a calibration curve calculator so students can check a five-point spectrophotometry or HPLC standard series without transcribing a spreadsheet slope that flipped x and y. Method-development notebooks pin slope, intercept, and R-squared beside each day's standards so a later audit can reproduce the line from the same rows. Quality teams compare R-squared and slope drift across batches without opening a statistics package for a two-coefficient fit.
Call the in-browser tool for lecture demos, bench-side checks, and quick verification of a CSV you already typed. Keep at least two distinct concentrations. A blank plus one standard is enough mathematically, but working methods usually run three to seven levels so curvature and outliers have somewhere to show.
R-squared near one does not replace residuals, lack-of-fit tests, or a check that the unknown sits inside the standard range. Authors shipping SDKs can map the echoed standards array into a table with concentration and response columns—the same table an analyst fills when they fit a linear calibration by hand.
What you can do with it
Spectrophotometry and Beer's law standards
Fit absorbance versus concentration for a five-point UV-Vis series, record slope as the method sensitivity, and keep R-squared with the day's calibration in the notebook.
Chromatography peak-area calibrations
Send HPLC or GC standard levels with peak area as response, retrieve intercept and slope for the sequence, and reject a run that only repeated a single concentration.
FAQ
How do I compute a linear calibration curve from standards?
Send standards as rows of concentration and instrument response (at least two distinct concentrations).
What happens if I have fewer than two distinct points?
A unique finite slope needs non-zero variance in concentration, so a single row or identical concentrations cannot define a calibration line and are not billed.
How is R-squared defined for this calibration curve?
R² is 1 − SS_res/SS_tot from the fitted line response = slope × concentration + intercept. When every response is identical and the fit is exact, R² is 1. It is a goodness-of-fit statistic, not a method-validation certificate.
Which units should I use for concentration and response?
Any consistent pair: mg/L with absorbance, µM with peak area, ppm with millivolts, and so on. The fit is unit-agnostic; do not mix concentration units or response units inside one request.
How do I turn a sample reading into a concentration?
Use the line the tool returns: subtract the intercept from the reading and divide by the slope. With a slope of 0.2 and an intercept of 0.01, a reading of 0.41 corresponds to a concentration of 2.
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/calibration-curve \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"standards":[{"concentration":0,"response":0.01},{"concentration":1,"response":0.21},{"concentration":2,"response":0.41},{"concentration":3,"response":0.61},{"concentration":4,"response":0.81}]}'const res = await fetch("https://api.kit.forhosting.com/chem/calibration-curve", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"standards": [
{
"concentration": 0,
"response": 0.01
},
{
"concentration": 1,
"response": 0.21
},
{
"concentration": 2,
"response": 0.41
},
{
"concentration": 3,
"response": 0.61
},
{
"concentration": 4,
"response": 0.81
}
]
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/chem/calibration-curve",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"standards": [
{
"concentration": 0,
"response": 0.01
},
{
"concentration": 1,
"response": 0.21
},
{
"concentration": 2,
"response": 0.41
},
{
"concentration": 3,
"response": 0.61
},
{
"concentration": 4,
"response": 0.81
}
]
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/chem/calibration-curve", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"standards":[{"concentration":0,"response":0.01},{"concentration":1,"response":0.21},{"concentration":2,"response":0.41},{"concentration":3,"response":0.61},{"concentration":4,"response":0.81}]}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"standards":[{"concentration":0,"response":0.01},{"concentration":1,"response":0.21},{"concentration":2,"response":0.41},{"concentration":3,"response":0.61},{"concentration":4,"response":0.81}]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/chem/calibration-curve", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"standards": [
{
"concentration": 0,
"response": 0.01
},
{
"concentration": 1,
"response": 0.21
},
{
"concentration": 2,
"response": 0.41
},
{
"concentration": 3,
"response": 0.61
},
{
"concentration": 4,
"response": 0.81
}
]
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "chem.calibration_curve",
"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
Fewer than two distinct concentrations fail with invalid_input instead of a silent vertical or undefined line. The same pure arithmetic runs free in the browser and as a prepaid API call at $0.002 per successful item, so a lab notebook, an LIMS plugin, and a homework check never disagree on the fitted coefficients.
Input contract, response shape, and errors when points are not distinct
Each row is an object with concentration, a finite number in any consistent concentration unit, and response, a finite instrument reading in any consistent response unit. Units never mix inside one call: milligrams per litre with peak area is fine; mixing milligrams per litre with molarity on the same axis is not. The identical-concentration case is the same mathematical defect as a single point: Sxx is zero and the least-squares slope is undefined, so the engine reports that you need at least two distinct standard points. Mean concentration and mean response are included as the centroids of the fit. The equation field rewrites the line with those rounded coefficients as response equals slope times concentration plus intercept, and the formula field restates slope equals Sxy over Sxx, intercept equals mean y minus slope times mean x, and R-squared equals one minus SS residual over SS total. Send a JSON object whose required field is standards: an array of at least two rows and at most sixty-four. Aliases points and data are accepted for the array; conc and x are accepted for concentration; signal, absorbance, and y are accepted for response. Missing arrays, empty lists, a single row, non-object rows, non-finite values, and lists whose concentrations are all identical fail with invalid_input naming the problem, and those failures are not billed. On success the payload echoes the rounded standard rows and point_count so you can confirm what was fitted. The primary results are slope, intercept, and r_squared. Identical inputs always produce identical JSON because the path is pure arithmetic with no network, no random seed, and no wall clock. Pair the coefficients with your own unknown-sample formula x equals (y minus intercept) divided by slope if you need to invert a later reading; this endpoint returns the curve, not the inversion.
Where a calibration curve calculator is used, pricing, and practical limits
Use the API when a LIMS, an electronic lab notebook, or a curriculum generator needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance.
Integration use cases
LIMS and teaching-lab automation
Pipelines and LMS plugins post standard rows as JSON, store the deterministic slope, intercept, and R-squared, and surface invalid_input when fewer than two distinct points arrive.
Technical questions
What does the calibration curve calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.