How many saves on Instagram is good? Beat your own median

23 October 2026 · Ethan Parker, Editor

There is no universal good save count. A good one beats the middle value of your own recent posts. How to find that figure, and why saves arrive late.

A save count is good when it sits above the middle value of your own recent posts in the same format. There is no universal number, because the number of accounts a post reaches sets the whole scale. Ten saves on a post seen by three hundred people and ten saves on a post seen by thirty thousand are not the same event.

The one carve-out, and it matters before you judge anything: the number in front of you is probably not the final one. Saves keep arriving for days after a post stops being new, and later than likes do, because saving is often the second thing a person does rather than the first.

To see the figure at all, open the post, tap View insights underneath it, and find the bookmark icon in the row with likes, comments and shares. Accounts reached is on the same screen. If View insights is missing, the account is still a personal one, and Instagram gives Insights only to professional accounts, which is the free Creator or Business setting in your profile settings.

Everything below turns those two numbers into one fraction, then compares that fraction to itself over time. That is the only comparison that is fair, and the only one you can actually run.

Why no save number fits every account

Every benchmark you can find was worked out from a sample of accounts, and yours was not in the sample. That is not a technicality. Two accounts with the same follower count can sit in different topics, post at different hours, and be shown to a different mix of followers and strangers. Each of those shifts the save rate on its own.

The fair comparison is your account against your account, a month ago. Same voice, same subject, roughly the same audience. Whatever moves there moved because of something you changed.

What actually counts as a save

A save is one tap on the bookmark icon at the bottom right of a post. It files the post in your own Saved area, which nobody else can open. It is not a like, it is not a share, and the poster is never told it happened.

• Counted: a tap on the bookmark icon on a feed post, a carousel or a reel.
• Counted once per account. Tapping again removes the save rather than adding a second one.
• Not counted: a screenshot, a copied link, or a post sent to a friend in a message. That last one is a share, on a different line of the same screen.
• Not shown: who did it. The poster gets a count and never a list of names, which has its own page here.

How to work out your own save baseline

This takes about fifteen minutes and uses only figures already in the app. You are turning raw counts into one percentage per post, then finding the middle of the pile.

1. Open Insights and stretch the date range back as far as it goes, ideally three months. A small sample lies.
2. Write down two figures per post: accounts reached, and saves. Skip likes and comments; they answer a different question.
3. Sort the posts into three piles by format: reels, carousels, single images. Never compare across the piles.
4. For each post, divide saves by accounts reached and multiply by a hundred. That is your save rate as a percentage.
5. Order each pile from lowest to highest and take the middle value. That figure is your normal.
6. Anything above the middle is a good post for you. Read the top two or three again and work out what they shared.

Take the middle value, not the average. Saves cluster strangely: most posts collect a handful and one collects a pile, so an average describes the pile rather than your usual work. The middle value describes the posts you actually make.

Sample size decides whether any of this means anything. Four posts per format is not a baseline. If that is all you have, write the numbers down, keep posting, and redo the sum once removing any single post would not shift the middle much.

Why the count keeps climbing after the post is old

Saves lag more than any other reaction on a post. A like happens in the second the post is on screen. A save often happens after a pause, and sometimes on a second visit days later. Insights reports on a delay of its own too, so a fresh post is being measured while the measuring is still running.

So never set a post published yesterday against one published a month ago; the older one has had time to collect. And when you rebuild your median, use posts at least a couple of weeks old, so every post in the pile had the same chance.

Reels, carousels and single images are three separate measurements

A carousel invites a save because it holds several things at once and the viewer wants to finish it later. A reel gets saved when somebody plans to come back and copy what was in it. A single image gets saved when it is a reference: a chart, a recipe, an address, a checklist. Three different habits, so averaging them produces a figure that describes none of them. What a save is covers the mechanics.

When a low save count is not a problem

Not every post is save shaped. A post whose job is to be seen once, enjoyed and scrolled past has done that job. Asking it for saves is asking a joke to behave like a manual. If your account is mostly that kind of post, a low save rate describes your format, not a fault. Judge those on reach and likes.

A save is somebody saying they will come back. The count tells you how many said it. It never tells you how many did.

What a save count will never tell you

It will not tell you whether the save was any use. Plenty of saved posts are never opened again, because the Saved area is largely where good intentions go to sit. It will not tell you who saved it, so a customer, a competitor and an idea collector look identical inside the total. And no save count is a promise about what Instagram does with the post next. Why the signal still carries weight is set out in why a save beats a like.

Where a paid month fits, and where it does not

What we sell is one prepaid month of reach, sized by a band you pick, applied to every feed post and reel you publish across thirty days, up to thirty posts. Views, likes, shares and saves ride along inside that same band. ReachGrows does not sell followers or comments, and says so on its own pricing page. It does not touch Instagram Stories either.

One warning matters more here than almost anywhere: work out your median before a month starts, and keep the figures somewhere outside the app. Delivery moves both halves of the save rate at once, the saves and the accounts reached, so the fraction afterwards measures a different thing. Written down first, your old median stays a fair yardstick. The FAQ sets out what is delivered and what is not.

What a month can do here is give a run of posts a comparable audience size, so the gaps between them come from the posts rather than from who happened to be scrolling. What it cannot do is make a post worth keeping. That part is still the post.

• How many saves on Instagram is good? There is no set number. Good means above the middle value of your own recent posts in the same format.
• What is a good save rate? Saves divided by accounts reached, times a hundred, compared only against your own past posts.
• Why does my save count keep rising? Saves arrive late and keep arriving for days, and Insights reports on a delay of its own.
• Should I compare reels with carousels? No. They get saved for different reasons. Keep three piles and three middle values.
• Can I see who saved my post? No. Instagram gives the poster a count and never the names.
• Is a low save rate always bad? No. Some formats are made to be seen once, and belong on reach and likes instead.