Logo

MonoCalc

/

Engagement Rate Benchmark Comparator

Social Media

The definition, applied to every row

Follower, subscriber or member count at the time of the post. The most widely quoted basis, and the one least related to how many people actually saw the post.
Every ticked type is summed, for your row and for every comparison row alike. Saves are off by default because many reports leave them out.

ER = (likes + comments + shares) ÷ followers × 100

Display only. Everything is computed at full precision and rounded once, at the point it is printed.

Your figures

Appears on the chart, in the summary and in the CSV.
Shorthand such as 67.3k works, and commas are ignored.

Comparison cohort

Every comparison figure is one you entered
MonoCalc does not ship benchmark data. Every comparison figure below is one you entered. Engagement rate has no standard definition, so a figure from an external report is only comparable to yours if it uses the same numerator and denominator.

Row 1

Optional. When filled it wins over the counts.
One row per line, comma or tab separated: label, likes, comments, shares, followers. Thousands separators and percent signs are stripped. A leading heading line is skipped.

Cited benchmark (optional)

A cited benchmark is drawn as a reference line only. It is left out of the percentile, the median and the quartiles, because it is a number from somewhere else rather than a member of your comparison set.

Stored and shown exactly as you typed it. Only http and https addresses become links.

—

No rate for your own row yet — enter the interaction counts and the followers figure above.

This is not a significance test
A percentile describes where a number sits in a list. It is not a statistical test, and it says nothing about whether the difference would survive more data. Treat it as a description of the rows you entered, not as evidence.
Nothing here is fetched from a platform
Every figure is typed in or pasted by hand. This tool makes no network requests and cannot read your account metrics, so a number is only as good as the row it came from.

About This Tool

Engagement Rate Benchmark Comparator – Where Your Rate Actually Sits

A single engagement rate tells you almost nothing on its own. 4.2% is only meaningful next to other rates measured the same way, and the moment you reach for a published “industry average” to supply that context, the comparison quietly breaks: you are almost certainly holding two numbers built from different denominators. This comparator fixes that by doing the opposite of what a benchmark table does. It ships no figures at all. You supply the comparison set, it applies one stated definition to every row including yours, and it shows you the shape of the distribution you actually built.

No benchmark data is published here
There is no credible, freely licensed, current table of average engagement rate by industry and platform. The ones in circulation come from private vendor panels, do not disclose their denominator, and go stale within a quarter. Every comparison figure in this tool is one you entered.

One definition, applied to every row

Engagement rate is not standardised, so the definition is an input here rather than an assumption. Two controls set it: which interactions count in the numerator — likes, comments, shares and optionally saves — and what the denominator is: followers, reach or impressions. The resulting formula, something like ER = (likes + comments + shares) ÷ followers × 100, is pinned directly under the headline percentile and written into the first line of the CSV export. Change either control and the whole distribution recomputes, never just your own row.

The denominator is where most cross-account comparisons go wrong. Followers counts everyone subscribed whether or not they saw the post; reach counts only the unique accounts shown it; impressions counts every view including repeats. The same 1,200 interactions can be 4% on reach and 1% on impressions. Both are correct. Neither is comparable to the other.

How the percentile is calculated

The tool uses the mid-rank (Hazen) convention: (below + 0.5 × equal) ÷ n × 100, where the comparison set is the cohort rows alone and your own rate is not a member of it. Ties land halfway rather than all at the top. Quartiles and the median use linear interpolation between order statistics — R type 7, the same method as Excel’s PERCENTILE.INC — so a figure computed here matches one computed in a spreadsheet. Both conventions are named in tooltips beside the numbers, because percentile has several defensible definitions and a silent choice is unreproducible.

Percentage points are not percent

If your rate is 4.3% and the cohort median is 2.9%, the gap is 1.4 percentage points and also +48% relative. Both describe the same pair and they are constantly swapped for one another in reporting. This tool prints both, each labelled with its own unit, so a screenshot cannot be misread.

Mean, median and the pooled rate

Three averages appear, because they answer different questions. The median is the middle row. The mean averages the row rates, weighting a 300-follower post exactly as much as a 300,000-follower one — the typical post. The pooled rate adds every interaction and divides by every denominator, so the largest rows dominate — the body of work as a whole. The percentile and the quartiles are built on row rates, which puts them in the same family as the mean and the median rather than the pooled figure.

Reading the distribution strip

The strip is the point of the tool. A shaded band spans Q1 to Q3, a solid line marks the median, every cohort row is a tick on the axis, and your own rate is a tall marker with a callout. A benchmark you cited, when you add one, is drawn as a dashed reference line and excluded from every statistic — it is a number from somewhere else, not a member of your set. Ticks are keyboard-reachable in sorted order and each announces its label and rate. Below it, a sorted bar chart shows every row descending by rate with the median drawn across them, which is the view worth screenshotting.

Edge cases the tool refuses to fudge

A row with no denominator is excluded and marked, never treated as 0%. A row with zero interactions and a real denominator is a legitimate 0.00% and stays in. A rate below the display precision shows as < 0.01% rather than rounding to nothing, while full precision is kept for the maths and the export. Negative inputs are rejected at the field. And a cohort of exactly one row suppresses the percentile entirely in favour of a plain two-way comparison, because a percentile over a single value is either 0 or 100 and means nothing.

A percentile is not a significance test
Where a number sits in a list is a description, not evidence. It says nothing about whether the difference would survive more data. For a genuine comparison between two variants, use a significance test rather than reading a rank as proof.

Frequently Asked Questions

Is the Engagement Rate Benchmark Comparator free?

Yes, Engagement Rate Benchmark Comparator is totally free :)

Can I use the Engagement Rate Benchmark Comparator offline?

Yes, you can install the webapp as PWA.

Is it safe to use Engagement Rate Benchmark Comparator?

Yes, any data related to Engagement Rate Benchmark Comparator only stored in your browser (if storage required). You can simply clear browser cache to clear all the stored data. We do not store any data on server.

How does this engagement rate comparator work?

You pick one definition — which interactions count, and what to divide them by — and the tool applies it identically to your own figures and to every comparison row you enter. It then sorts the comparison rates, works out where yours lands, and reports the percentile, the median, the quartiles and the gap, with a distribution strip and a sorted bar chart drawn from the same numbers. Rows can be typed one at a time or pasted straight out of a spreadsheet, and changing the definition recomputes every row, not just yours.

Why does this tool not come with industry benchmark data?

Because no benchmark table exists that is simultaneously free to republish, transparent about its method and still current. The widely circulated ones come from a vendor's private panel, never disclose the denominator they used, and are stale within a quarter. Comparing your follower-based rate against someone else's reach-based rate produces a confident number that means nothing, so this tool ships none. Every comparison figure it shows is one you entered, and if you want to cite a published figure you paste it in with its label, source link and the date you read it, and the tool re-displays that attribution beside it.

What is the difference between percentage points and percent here?

They are two different measurements of the same gap and they are routinely confused. If your rate is 4.3% and the median is 2.9%, the gap is 1.4 percentage points — a subtraction — and also +48% relative, because 1.4 is 48% of 2.9. Saying you are '48% above the median' and 'a point and a half above the median' both describe that same pair correctly. This tool prints both, each labelled with its own unit, so a screenshot cannot be read the wrong way.

Why does the denominator change the answer so much?

Because followers, reach and impressions are three different-sized numbers. Followers counts everyone subscribed to the account whether or not they saw the post; reach counts only the unique accounts shown it; impressions counts every view including repeats, so it is usually the largest of the three. The same 1,200 interactions can be a 4% rate on reach and a 1% rate on impressions. Neither is wrong, and neither is comparable to the other, which is why the basis you picked is printed under the headline, written into the CSV and carried in the share link.

Can an engagement rate really be above 100%?

Yes, and this tool never clamps one. On a follower basis, a post that is shared, recommended or surfaced in search reaches people who do not follow the account, and each of them can like, comment and share, so the interaction count can exceed the follower count outright. On a reach basis, one person can contribute several interactions to the same post. Capping such a rate at 100% would delete the single most informative result the arithmetic can produce, so it is shown as measured and flagged with a short note the first time it appears.

Should I look at the mean or the pooled rate?

They answer different questions. The mean is the average of the row rates, so a post that reached 300 people counts exactly as much as one that reached 300,000 — useful when you want the typical post. The pooled rate adds every interaction and divides by every denominator, so the biggest rows dominate — useful when you want the rate of the body of work as a whole. Both are shown, separately labelled. The percentile and the quartiles are built on the row rates, matching the mean rather than the pooled figure.