Add to queue,
never pick a time
Picking a date and time for every post is small friction repeated forever, and it is usually what turns daily posting into weekly posting. Write the post, press Add to queue, and it lands in your next peak-engagement slot.
The Content Drifter queue lets you add a post without picking a time: it lands in your next open peak-engagement slot, skipping any hours you marked off-limits and never double-booking a slot that already has a post. Unlike other schedulers, whose queues run on a table of times you filled in by hand, these slots are measured windows personalised from your own results. The queue also tells you the date it runs dry, which is the number that actually gets the next post written.
The decision you stop making
A queue is not a scheduling feature so much as a habit feature. Every time a tool asks you to choose a date, it gives you a chance to close the tab. Removing that choice is why queue-first products get used daily and calendar-first products get used when someone remembers.
Measured slots, not a table you filled in
Most queues run on times you typed in once and never revisited, so the queue is only ever as good as your guess about when your audience is awake.
Ours fills Gold Slots: peak-engagement windows per platform, which on paid plans are re-ranked using your own posting history. The next open slot is the next genuinely good moment, and it keeps getting better as we learn what works for your account specifically.
It respects the rules you already set
Blackout windows are hard constraints. If you have told Content Drifter never to publish late at night or over the weekend, the queue skips those slots rather than filling them.
The low-friction path must never break a rule you set deliberately. Automation that ignores your own settings is worse than no automation, because now you have to check its work.
It also never double-books: a slot that already holds a post is simply passed over.
The number that actually matters
Every scheduler shows you how many posts are queued. Twelve queued tells you nothing you can act on today.
Content Drifter shows you the date it runs dry. "Runs out Tuesday" is a deadline, and a deadline is what gets the next post written. It is one sentence, and it is the most useful thing on the screen.
The ceilings it will not let you cross
Every network has a point past which posting more stops helping and starts costing you reach. The queue holds a limit per network and refuses to book a slot that would break it: a minimum gap between posts, a daily ceiling, and a weekly one.
| Network | Minimum gap | Per day | Per week |
|---|---|---|---|
| 8h | 2 | 7 | |
| X (Twitter) | 1h | 8 | 35 |
| 4h | 3 | 14 | |
| 4h | 3 | 14 | |
| Threads | 1h | 6 | 30 |
| YouTube | 12h | 2 | 10 |
| 1h | 10 | 50 | |
| Bluesky | 1h | 8 | 40 |
| TikTok | 2h | 4 | 21 |
These are our engine's values, not a number any platform publishes, and we would rather say that than dress them up as official. What is not a judgement call is that they are now enforced: they were modelled for months and read by nothing, and what exposed it was writing a page that claimed the queue honoured them. A field with no reader is a promise with no product behind it.
The queue view shows the holes, not just the posts
Every scheduler ships a queue view, and every one of them renders the posts you have. That answers "what is scheduled", which you can already see. The question you actually have is where the gaps are, and a chronological list is structurally unable to show you: the silence between two rows has nothing to draw, so it draws as nothing.
Four posts on Tuesday and then nothing until the following Monday is a worse week than one post a day, and in a list those eight rows look identical to a well-spread eight. Here the silence is a row of its own: 13 quiet days, Sat 22 August to Thu 3 September. A single quiet day is absorbed, because that is a normal week and flagging it would teach you to ignore the flags.
And the gap is the button. Looking at a hole in your feed, you already know what you want to do about it, so clicking it opens the composer on that day. Reporting a problem and making you go somewhere else to fix it would waste the only moment where the next action is obvious.
Move a lot of posts at once, and take it back
Select posts in the queue and move them together: a day, a week, or straight into your next free peak-engagement slots. A launch that slipped a week is one click rather than forty.
Moving forty scheduled posts is the most destructive thing a calendar can do, and it goes wrong invisibly: nothing is deleted, nothing errors, the posts are simply somewhere else. So you see exactly what will move before it moves, anything we refuse is named with the reason rather than quietly folded into the total, and every move can be undone. The undo puts each post back where it actually was, rather than shifting everything the other way, because those stop being the same thing the moment one post was skipped.
Still a calendar when you want one
The queue is an option, not a replacement. Pick an exact time whenever a post needs one: a launch, an event, an announcement timed to something outside the platform. The queue is for the other 90% of posts, where any good time will do and the real goal is that the post goes out at all.
If every slot in the next 90 days is taken or blacked out, we say so and tell you which, rather than quietly picking a worse time.
Frequently asked questions
How is this different from the Buffer queue?
The Buffer queue posts into time slots you configured yourself, so it is only as good as your guess about when your audience is around. Content Drifter fills measured peak-engagement windows per platform, personalised from your own posting history on paid plans, and it skips any blackout windows you set. So the next open slot is the next genuinely good moment rather than the next free row in a table.
What does "runs out" mean?
It is the date your last queued post publishes. Every scheduler shows you a count of queued posts, which tells you nothing you can act on. A date is a deadline, and a deadline is what gets the next post written.
Can the queue post during hours I do not want?
No. Blackout windows are treated as hard constraints, so the low-friction path cannot break a rule you already set. Automation that ignores your own settings is worse than no automation.
Can I see where the gaps in my schedule are?
Yes, and that is what the queue view is for. Every scheduler shows you the posts you have; a chronological list cannot show you the silence between them, because nothing is there to render. Content Drifter draws each quiet stretch as its own row, for example "13 quiet days, Saturday 22 August to Thursday 3 September", and clicking it opens the composer on that day. A single quiet day is absorbed rather than flagged, because that is a normal week and flagging it would teach you to ignore the flags.
What happens if the queue is full?
You get told, with the reason. If every slot for the next 90 days is booked or inside a blackout window, we say so rather than silently picking a worse time. Adding more slots or narrowing a blackout window fixes it.
Is the queue available on the free plan?
Yes, on every plan. Personalised slot ranking, where we re-rank the windows using your own engagement history, is a paid capability, but the queue itself is not gated. A queue nobody can use is not a feature, it is a paywall on a habit.
Keep reading
Related pages people usually open next.
Ready to try it?
Start for free and upgrade as you grow. No credit card required.