Why VKontakte limits got tougher in 2026
In 2026 VKontakte fully shifted to a behavioral model of restrictions: fixed daily caps gave way to dynamic limits that the antispam engine recalculates in real time based on a profile's trust score. A freshly registered account with no linked phone, an empty profile and zero history in VK Music or VK Clips gets slashed quotas — sometimes five to ten times lower than a warmed profile with two years of activity. That is why there are no longer universal numbers, and any limits table is merely a guideline for an account of average reputation.
The key ban trigger is not the count of actions but their rhythm. The algorithm tracks intervals between requests, template overlap in messages, and abnormal speed through the official client versus Kate Mobile or direct vk_api calls. Perfectly even actions every N seconds get flagged instantly.
Friend requests, follows and likes
For a warmed profile the benchmark for friend requests is around 40–50 per day with irregular pauses, and the acceptance ratio matters more than the count: if fewer than a third get approved, antispam cuts the quota. Follows on communities and people stay within a corridor of about 200 actions, but only with natural feed scrolling in between. Likes in VK Clips and on the wall allow several hundred a day, yet a streak of a hundred in a row on a single community without views is a direct route to a captcha and then a freeze.
A separate risk zone is cancellations and repeat requests. If a profile mass-sends invites and instantly withdraws them, antispam reads this as reach manipulation and lowers trust for weeks.
Messages, mailings and Senler
Private messages to strangers are the most sensitive channel. From a personal profile the safe ceiling for outgoing new dialogs rarely exceeds 20–30 per day, and only with varied text. Mass mailings in 2026 are run exclusively through VK Callback API and services like Senler, where official subscriber bases work and messages go only to those who tapped "Allow messages from community." Trying to bypass the subscription model with direct messages.send calls via an app access_token almost guarantees an account flag and a blocked token.
Communities have their own mechanics: messages on behalf of a public page are limited at the app level, not the profile level, and on excess VK returns error 9 (Flood control) before any ban.
Community invites and working through vk_api
Invites to groups and events remain strictly limited — roughly 40 invites per day per profile, and abuse quickly drops the whole public into a shadow ban on reach. When automating through vk_api or VKBottle it is critical to keep pauses and handle errors 6 (Too many requests) and 29 (Rate limit reached) with exponential backoff rather than retrying in a loop. Parsing audiences via TargetHunter and uploading them to VK Ads / myTarget does not touch profile limits in itself, but the "parse then manually send invites" combo hits the same ceiling.
How to scale without bans: warmed accounts
The main takeaway of 2026: hitting one profile's limits is wiser than risking that profile. Real scaling is built on a pool of aged accounts with history, distinct fingerprints and proxies, where load is spread across many profiles and each one operates within its own safe quota. On VKMarket you can buy ready warmed VKontakte accounts paying in USDT — with filled profiles, activity and passed validation, which removes the main reason new registrations get throttled.
Before launching a campaign, warm each profile manually for several days, alternate actions with viewing Stories and VK Music, and keep the daily load well below the theoretical ceiling — a 30–40% buffer is exactly the insurance against a trust recalculation.