Best time to post
Sensible starting slots per network, converted between your audience’s timezone and your own — because the mistake is almost never the hour, it is whose hour.
These are starting points, not laws. They are worth exactly one week of testing against your own audience, then replace them with what your data says.
The mistake is whose hour, not which hour
Most “best time to post” advice gives you an hour without saying whose. If your audience is in New York and you are in Berlin, their 9am is your 3pm, and a queue built in local time posts to an empty feed every morning.
The second version of the same mistake is worse: a scheduler that stores 09:00 plus a timezone rather than an absolute instant. When daylight saving shifts, every future post moves an hour. A queue built in February quietly slides in March.
How to use these
- Take the three slots as a starting hypothesis, not an answer.
- Run them for two weeks without changing anything else.
- Compare against your own analytics and replace any slot that underperforms.
Per-network detail — why these hours, what the format changes, and what to test next — is on the per-network pages.
Questions
Where do these times come from?
They are consensus starting points from published platform guidance and widely-reported engagement studies, adjusted for the format each network rewards. They are deliberately conservative: three slots you can test, not twenty-one you cannot.
Should I trust them over my own analytics?
No. Your own data beats any general figure the moment you have two weeks of it. These exist for the period before you have that.
Does this handle daylight saving?
It uses the current offset of a representative city, which is right today and may drift by an hour across a DST boundary. Schedule against an absolute instant and the problem disappears entirely.
Is anything sent to a server?
No. The conversion happens in your browser.