Average percentage calculator
Scores of 80, 90 and 70 percent average out to 80 percent. Paste exam scores, conversion rates or survey results already written as percents, with or without the % sign, and get one representative percentage. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Percentages
- 80, 90, 70
- Quantity
- 3
- Sum
- 240
- Average percentage
- 80
Average percentage is the arithmetic mean of a list of percent figures: add every percentage and divide by how many there are. People reach for this when they have exam scores, conversion rates, survey results, or completion figures already expressed as percents and they want one representative percent for the set. This calculator accepts a non-empty list of finite numbers, optionally written with a trailing percent sign, and returns the count, the sum, and the mean percentage together with the formula used.
What average percentage means and when the unweighted mean is the right tool
The average of a list of percentages is the unweighted arithmetic mean of those percent figures: add every value and divide by the count n. If the list is eighty, ninety and seventy, the sum is two hundred forty and the mean is eighty percent. That is the number people mean when they search for an average percentage calculator: one representative percent that treats each observation with equal weight.
The formula does not convert percents into fractions first, does not annualize a rate, and does not weight by sample size, revenue, or elapsed time. It is the right tool when the percentages already share a comparable base: exam scores out of one hundred, conversion rates from campaigns of similar volume, weekly completion percents for the same process, or survey agreement rates collected on the same question. It is the wrong tool when the percents come from very different denominators.
Averaging a ninety percent conversion on ten visitors with a ten percent conversion on ten thousand visitors hides the large sample and overstates the tiny one. Negative percents (a decline) and values above one hundred (over-completion or growth) are accepted because they are still finite numbers. Empty lists are rejected: there is no mean of nothing.
Any entry that is not a finite number is rejected by index rather than skipped, so a stray label cannot silently shrink the sample and produce a fake average.
Where an average percentage calculator earns its keep, and what it is not
Use this average percentage calculator when you already have a list of percent figures and you want their unweighted mean. Teachers average quiz scores that are already expressed as percents. Marketers average conversion rates across campaigns of similar scale.
Operations teams average weekly completion percents for the same workflow. Analysts average survey agreement rates collected on one question. Prefer a weighted mean when sample sizes differ a lot.
Round-trip checks are easy: add the percents by hand, divide by the count, and confirm the ratio matches the published mean within twelve decimal places.
What you can do with it
Campaign conversion rates
Summarize several conversion percents of similar volume into one unweighted average percentage for a weekly marketing report.
Survey agreement and completion percents
Combine weekly completion percents or survey agreement rates for the same process into a single representative percent without inventing weights.
FAQ
How is average percentage calculated?
Send a non-empty list of finite percentage values.
What happens if the list is empty or a value is not a number?
There is no mean of an empty list, and non-numeric entries are not skipped. Failed validation is not billed.
Should I type 80 or 0.8 for eighty percent?
Type 80 for eighty percent (or 80%). Use 0.8 only if you actually want the mean of decimal fractions rather than percents.
Can percentages be negative or greater than 100?
Yes. Negative percents (declines) and values above 100 (growth or over-completion) are accepted as long as they are finite numbers.
When is averaging percentages misleading?
When the percentages come from very different bases. A 90% conversion on ten visitors and a 10% conversion on ten thousand visitors average to a figure that overstates the tiny sample; a weighted mean is the honest summary there.
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/math/average-percentage \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"percentages":[80,90,70]}'const res = await fetch("https://api.kit.forhosting.com/math/average-percentage", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"percentages": [
80,
90,
70
]
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/math/average-percentage",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"percentages": [
80,
90,
70
]
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/math/average-percentage", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"percentages":[80,90,70]}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"percentages":[80,90,70]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/math/average-percentage", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"percentages": [
80,
90,
70
]
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "math.average_percentage",
"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_items | 100000 |
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
An empty list or any value that is not a number fails with invalid_input and is never billed. A successful API call costs $0.002.
What average percentage means and when the unweighted mean is the right tool
In that case a weighted mean is the honest summary, and this endpoint will not invent weights you did not supply.
Input contract, response shape, and error behaviour
Numeric strings inside the array are coerced, including an optional trailing percent sign so that eighty percent may be written as 80 or as 80%. A comma, semicolon or whitespace separated string is also accepted for simple text forms. Enter eighty for eighty percent, not zero point eight, unless you actually want the mean of decimal fractions. A single-element list is valid: the average of one percentage is that percentage itself. Send a JSON body with one required field named percentages: a non-empty array of finite numbers. Aliases values, list and numbers are accepted and behave the same. On success the body reports count as n, percentages as the parsed list in input order, sum as the total of those values, average_percentage as sum divided by n, and a formula string restating (p1 + p2 + … + pn) / n. Failed validation—missing percentages, an empty list, a non-finite entry, a list longer than one hundred thousand values, or a magnitude above one quadrillion—returns invalid_input naming the problem and is never charged. A successful API request is charged the published $0.002 base price with unit item.
Where an average percentage calculator earns its keep, and what it is not
Pair classroom examples deliberately: eighty, ninety and seventy produce eighty percent; ten, twenty and twenty-five produce about 18.3333 percent; an empty list demonstrates the invalid_input path. This page is not a percentage difference calculator, which compares two peer numbers relative to their average and is a different search. It is not a percent-of or markup engine, and it is not a generic mean-median-mode summary of unlabeled numbers. Keep magnitudes inside the published absolute limit and keep the list within one hundred thousand values so interactive Worker and browser paths stay fast. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners send empty arrays or stray text. Pin the rounded average_percentage field in tests. API pricing remains the flat $0.002 per successful request.
Integration use cases
Quiz and exam percent scores
Average a class list of scores already expressed as percents (80, 90, 70) and check the mean against a deterministic browser or API result.
Technical questions
What does the average percentage calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.