PostRSS Limits: Posts per Month, per Target and Targets

Short answer: every PostRSS plan has three limits that work together: posts per month for the whole account, posts per target, and the number of targets. A target is one connected destination, such as a Facebook Page, a Telegram channel or a Bluesky account. The monthly figure is the ceiling for the account, the per-target figure is the ceiling for a single destination, and the target count tells you how many destinations you can feed. Read the three numbers together before you choose a plan, and check the usage figure in your account after the first day to see how your own setup spends them.

Most people choose a social media tool by its price and its list of networks, and only discover the limits when a feed stops posting. PostRSS shows its limits openly on the pricing page and in the plan list of the API, so you can do the arithmetic before you pay. This guide explains what each limit means, how the three figures interact, which items do not use your allowance, and how to size a plan for a real website. It uses the current numbers from the live pricing page and the plan list, and it avoids guessing: where the pages do not say how something is counted, the guide tells you how to verify it in your own account.

The three limits in plain words

The pricing page lists, for every plan, a number of posts per month, a number of targets and a number of posts per target. The API plan list uses the same three values under the names tasks per month, targets and maximum tasks per target. A task is simply one publishing job, which for most readers means one post.

The first limit, posts per month, belongs to the whole account. It is the total that all your feeds and all your targets can publish in a month. The second limit, targets, is the number of connected destinations the plan allows. In PostRSS every connected account, page, channel, board or blog counts as one target, and one feed can be connected to several targets. The third limit, posts per target, belongs to a single destination, so that one very busy feed cannot spend the whole monthly allowance on its own.

The numbers for each plan

The table below repeats the current figures from the live plan list. They can change, so treat the pricing page as the source of truth and use the table to understand the pattern rather than to memorise it.

Larger Enterprise tiers exist for bigger operations, and the pricing page lists them. The pattern is the same: more posts, more targets and a higher figure per target at every step.

What the arithmetic tells you

On Free and Start the picture is simple, because both plans have one target. A single target can use the whole monthly allowance, so the monthly figure and the per-target figure are the same: 10 on Free and 500 on Start. There is nothing to balance.

From Professional upwards the numbers stop being equal, and that is useful. Ten targets with 2,000 posts each would add up to 20,000, but the plan allows 10,000 posts a month. Twenty targets with 3,000 posts each would be 60,000 against a monthly figure of 30,000, and fifty targets with 5,000 each would be 250,000 against 125,000. In every case the per-target figure multiplied by the number of targets is larger than the monthly figure. Read the labels the natural way and the consequence is clear: the monthly figure is the ceiling you meet first if you use every target heavily, and the per-target figure only matters when one destination takes a large share. If you plan to feed ten targets evenly, divide the monthly figure by ten and compare the result with the posts your feed really produces.

What counts as a post

The pages describe the limits but do not give a long definition of a counted post, so the safest approach is to understand what the product exposes. In the API every target reports a read-only used tasks value, and the subscription call reports the tasks used this month next to the tasks limit and the targets used next to the targets limit. The statistics call groups the task count by target type and gives a monthly history. All of this points to the same idea: PostRSS counts publishing jobs per target and adds them up for the month.

For planning, use a simple and cautious assumption: one feed item sent to one target is one post. If one item goes to four targets, plan for four posts. Then check the real figure. After your first full day of posting, open your account, note the used number, and compare it with the number of items your feed published and the number of targets that received them. Five minutes of checking gives you a measured rate that replaces any assumption.

Items that do not use your allowance

Some items never become posts, so they do not use the allowance. The API documentation states that items removed by a source keyword filter are not posted, do not count towards the maximum posts per update and do not count towards the plan quota; they appear in reports with the status filtered. The item statuses also include already posted, skipped, failed and a status for items that waited because the maximum posts per update was reached. An item that waited is not lost; it stays eligible for a later check.

This matters for planning. A feed that publishes thirty items a week but contains ten off-topic items can be filtered down to twenty before it touches the quota. If you run a general news site and your audience cares about one category, a filter is not only a quality tool; it is also a way to stay inside a smaller plan. The guide to include and exclude keyword filters explains how to write the rules.

Turn a feed into a monthly number

The easiest way to size a plan is to measure your feed. Count the items your site published in the last four weeks, for example from your blog archive. Multiply by the number of targets that will receive each item. Add a margin for busy months, because a campaign or a product launch can double a normal week.

Here is a worked example. A small shop publishes about eight blog posts and fifteen new products a month, which is twenty-three items. It wants to post to a Facebook Page, a Telegram channel and a Pinterest board. That is twenty-three items sent to three targets, so about sixty-nine posts a month, and three targets. The Free plan cannot do it: it has one target and ten posts. The Start plan has the posts but only one target. A plan with ten targets and ten thousand posts is far more than needed on the numbers, yet it is the first plan that offers more than one target, and it includes the networks the shop wants. That example shows why the target count, not the post count, often decides the plan for small sites.

A second example goes the other way. A news site publishes sixty items a day and wants to post only the three best categories to one Telegram channel and one Bluesky account. With a filter, perhaps twenty items a day pass, which is six hundred a month per target and twelve hundred posts for the two targets. The monthly figure is comfortable, and the per-target figure of the plan must be above six hundred. Both examples start with the same three steps: count the items, count the targets, and apply the filters.

Control the speed of spending

PostRSS gives you several settings that shape how quickly the allowance is used. The maximum number of posts per update limits how many items go out at each check, which prevents a burst when a feed publishes many items at once. The publishing order decides which items go first, so that a limit applied to a long backlog still shows the newest or the oldest items, as you prefer. Exact times and posting windows spread posts across the day. These controls are described in the guides on publishing order and posts per update and on exact times, windows and intervals.

The catch-up option deserves a warning in a guide about limits. When you add a start date and turn on catch-up, PostRSS also posts older feed items that were never published. That is a powerful way to fill a new page with content, and it is also a way to spend a month of allowance in an afternoon on a small plan. Use catch-up with a low limit per update on a small plan, and read the guide to catching up older feed items before you switch it on.

Signs that you are near a limit

You do not have to wait for a feed to stop to notice that a limit is near. Three signals help. First, the usage figure in your account: if you are two thirds through the month and have used far more than two thirds of the allowance, your rate is too high. Second, the reports: runs where items wait because the maximum per update was reached show that the pipeline is throttled by your own setting rather than by the plan. Third, errors when you edit a target: the API documents that a plan restriction returns an insufficient subscription error, and the website applies the same checks for the minimum interval, the number of targets and network support.

When you see these signals, you have four options. Filter the feed so that fewer items qualify. Reduce the number of targets that receive each item. Lower the frequency of low-value feeds. Or move to the next plan, which is a reasonable decision when the numbers say that your real need is above the current ceiling. Upgrading is a normal step, and a plan chosen on measured numbers wastes less money than a plan chosen on hope.

Common mistakes

• Choosing a plan by the number of networks and ignoring the number of targets.
• Forgetting that one item sent to several targets uses the allowance several times.
• Adding a long backlog with catch-up on a small plan.
• Leaving an old test target connected, so that it keeps using one of the available targets.
• Reading the per-target figure as an extra allowance instead of a cap on a single destination.
• Never opening the usage figure until a month has ended.

Пов’язане читання

• How to choose the right PostRSS plan
• How to read PostRSS reports and item statuses
• Common RSS auto-post mistakes that break your automation

The bottom line

PostRSS plans are built on three numbers: posts per month, targets and posts per target. The monthly figure is the account ceiling, the target count is the number of destinations, and the per-target figure caps one destination. Count your items, multiply by the targets that will receive them, subtract what a filter removes and compare the result with the table. Then watch the usage figure in your account and adjust. The current numbers are on the pricing page, and the full feature list is on the features page.

FAQ

What is a target in PostRSS?

A target is one connected destination, such as a Facebook Page, a Telegram channel, a Bluesky account or a webhook. One feed can be connected to several targets, and each target counts toward the target limit of your plan.

Do filtered items use my monthly allowance?

No. Items skipped by a source keyword filter are not posted and do not count toward the plan quota. They appear in reports with the status filtered.

How many posts does the Free plan include?

The Free plan includes ten posts a month and one target, with ten posts for that target. It is meant for testing and for very small feeds.

Why is the per-target figure multiplied by the targets larger than the monthly figure?

The per-target figure caps one destination, while the monthly figure caps the whole account. If you spread posts evenly across many targets you meet the monthly ceiling first.

Where can I see how much I have used?

Your account shows the usage, and the API reports tasks used this month beside the tasks limit, plus the used value of every target.

What happens when I reach the limit?

Check the current behaviour in your account and on the pricing page. The safest approach is to size the plan so that you stay below the limit and to filter or slow down feeds before you reach it.