How to Time a Product Hunt Launch: 12:01am Pacific and the Root-Domain Rule

A launch you get at most twice a year

Most launch channels forgive a bad day. Product Hunt doesn't, because it rations the slot.

Product Hunt's relaunch policy asks for at least six months between posts for the same product or company, plus a significant update. It also applies the gap across products that share a domain: "Products that share the same root domain must adhere to a six-month submission gap."

So a launch on a day you weren't ready for, or with a gallery you finished at 11pm, isn't a small loss. It's six months of waiting. This post covers the four timing decisions that matter: when you're awake, the weekday, the domain clock, and the weeks before. At the end there's a worksheet you can run against your own products.

The clock: when the ranking day starts

Product Hunt's help article on how to post a product says the site runs on 24-hour periods in Pacific time, and that a scheduled post goes live at 12:01am. The launch guide's preparation page recommends that slot because it gives you the full cycle.

You don't pick the hour any more. Product Hunt replaced its "Launch Now" option with Schedule and Create Draft (Where did Launch Now go?), and its scheduling article has you pick a day, up to 30 days ahead. The post then goes live at 12:01am on that day, without you.

The conversion still matters, for a different reason: you need to be awake, because the first hours are when you answer comments.

Converting 12:01am Pacific to your time zone

Product Hunt writes the zone as "PST", "Pacific Standard Time" and "Pacific Time". We read that as the Pacific wall clock, which is how LaunchBeam computes it: PDT (UTC-7) during US daylight saving, which runs from the second Sunday in March to the first Sunday in November, and PST (UTC-8) otherwise. Product Hunt doesn't say whether its day moves with daylight saving. If it stays on UTC-8 all year, the two PDT columns below run an hour later. A scheduled post goes live on its own either way; the table is for setting your alarm.

Here is 12:01am Pacific on three sample Tuesdays, computed from the IANA time zone database:

Your zone	Tue 15 Sep 2026 (PDT)	Tue 27 Oct 2026 (PDT, Europe on winter time)	Tue 8 Dec 2026 (PST)
UTC	07:01	07:01	08:01
New York	03:01	03:01	03:01
São Paulo	04:01	04:01	05:01
London	08:01	07:01	08:01
Berlin	09:01	08:01	09:01
India	12:31	12:31	13:31
Singapore	15:01	15:01	16:01
Tokyo	16:01	16:01	17:01
Sydney	17:01	18:01	19:01

All of these land on the same Tuesday. Your local hour moves with both clocks. Zones without daylight saving, such as India, Singapore, Tokyo and São Paulo, move an hour later from November to March. Southern-hemisphere clocks change the other way, so Sydney's gap swings by two hours over the year.

The middle column is the trap. From 25 to 31 October 2026, and again from 14 to 27 March 2027, the US and Europe are out of step, because the EU changes its clocks on the last Sundays of March and October. A founder in London who remembers "8am" is an hour late. Look the offset up for your actual date.

Weekday or weekend: the trade-off

Product Hunt doesn't name a best day. Its launch guide says "The best day to launch is the day on which you're most prepared."

The preparation page does describe the trade. It says larger companies, along with solo makers, tend to launch on weekdays, following business hours, and that weekends can suit smaller teams, side projects and personal apps. It gives one figure on the question: products launched on the weekend get 15% more "Visit" button clicks than those launched on weekdays (preparing for launch).

So a weekday puts you up against more big-name launches. A weekend has fewer, and by Product Hunt's number weekend launches get more clicks through to their sites. The page doesn't give traffic by day, so treat that as a per-product figure, not a measure of how many people are browsing.

LaunchBeam's default is Tuesday to Thursday. That's our view, not a Product Hunt rule. Our reasoning is that Monday inherits the weekend's backlog and Friday's ranking day runs into a weekend. We haven't found anything from Product Hunt that confirms it, and its weekend figure points the other way. If you're a small team with a consumer tool and the weekend is when you can sit in the comments all day, the weekend is a defensible pick.

The root-domain rule: one clock per domain, not per product

This is the rule that catches people with more than one product. The cooldown doesn't only attach to a listing. It also attaches to the root domain.

Say you run app.example.com and plan to ship two more tools this autumn as sign.example.com and forms.example.com. Each launch plan looks valid on its own. Together they're impossible, because Product Hunt sees one root domain. Launch the first in October and the second can't go up until April. The third waits until the October after that, a year from first launch to last. Add a fourth tool and it's at least eighteen months.

Working out your root domain

Product Hunt's relaunch article doesn't define "root domain". The standard definition is the registrable domain: the public suffix plus the label in front of it. The Public Suffix List is the community-maintained list of suffixes under which people can, or historically could, register names.

In practice:

1. Strip the scheme, the path and any www.. https://www.app.acme.com/login becomes app.acme.com.
2. Take the last two labels: acme.com.
3. If those last two labels form a suffix people register under, such as co.uk, com.au or co.jp, take three instead. app.acme.co.uk becomes acme.co.uk, not co.uk.

There's one ambiguous case. Shared hosting domains such as vercel.app and github.io appear on the Public Suffix List, so by the strict definition a.vercel.app and b.vercel.app are different sites. Product Hunt doesn't say how it treats them. If two products you care about sit on a shared host, email [email protected] before you build the second launch around a guess. The relaunch article invites exactly that.

Relaunching early, and launching several products

The six months has an exception, and it's narrower than most people hope. Under the relaunch policy, an earlier relaunch needs a significant update. Product Hunt's examples of significant are a new mobile app, or a complete redesign with new functionality. New UIs and pricing changes don't count.

You submit a relaunch request, describe what changed since your last launch, and Product Hunt's team reviews it. An approved relaunch isn't guaranteed a place on the homepage.

For several products, Product Hunt's advice runs against the usual plan: if you have several to post in a short time, the policy says it's best to combine them into one post. So the choice for a small studio isn't which tool goes first. It's whether the tools make more sense launched as one suite, with each one given a proper launch on channels that don't ration the slot.

The policy's first sentence also covers posts from the same company, not only the same domain. A separate domain removes the root-domain match but not the company clause, so it isn't a loophole. If both products come from one company, ask Product Hunt before you plan around it.

Assets that are ready before midnight

Have everything below done before the post goes live, because the first hours go on comments, not on cropping screenshots. These are Product Hunt's own specs, with one conflict between its pages.

Asset	What Product Hunt says
Tagline	Max 60 characters (launch guide)
Description	The launch guide says max 500 characters. The posting help article, last updated May 2025, says 260. Writing to 260 fits both.
Gallery	At least 2 images before the post is viewable. 1270×760 recommended.
Thumbnail	Square, 240×240 recommended. Static or GIF, GIF under 3MB.
Video	Optional. YouTube links only, full URL, not set to private.
Topics	A few that most strongly relate to the product.
First comment	Kick off the conversation yourself.

Specs and policies checked on September 10, 2026.

The first comment is easy to leave until last. Write it first. Product Hunt's preparation page says that of the products that reached Product of the Day, Week or Month, 70% had a first comment from the maker. Say who it's for, why you built it, and what you'd like people to tell you.

Hunting it yourself

You don't need a hunter. Product Hunt's launch guide encourages makers to hunt their own products and says there's no discernible advantage to using a third-party hunter. Its before-launch guide adds that paying people to hunt your product goes against its guidelines. It's also free: the how it works page says the site is free for everyone to use, and that its ads are separate from the leaderboard.

The before-launch guide also says a new account must wait a week before it can post. Don't create yours on launch eve.

Feedback, not upvotes

The easiest rule to break on launch day is the one against asking for upvotes. The launch guide says you can't ask people directly to upvote, and to ask them to visit and comment instead. The help centre's answer on asking friends to upvote spells out the cost: asking for or incentivising upvotes may drop the product down the rankings or remove it from the homepage entirely. The community guidelines list requests for upvotes, mass messaging, bots and incentives as unacceptable.

So the ask spends the ranking it was meant to buy. It also misses what the leaderboard reads. Product Hunt says the homepage moves on upvotes, comments, time since submission and other factors. Comments are on that list, and asking for them is allowed.

Compare two messages to your list on launch morning:

• "We're live on Product Hunt, an upvote would mean the world." This is a vote request, however polite.
• "We launched on Product Hunt today. I'd like to know whether the onboarding makes sense to someone who's never seen it. Tell us in the comments." This asks for feedback, with a question people can answer.

The second gets comments you can reply to, and replies keep the thread moving. Reddit has its own version of this problem; our Reddit self-promotion guide covers it.

The weeks before

Product Hunt recommends joining well ahead of your launch, three months or more, and building a presence in the community, according to its before-launch guide.

LaunchBeam's own heuristic concentrates that into the final stretch. For the 14 to 28 days before launch, be visibly present: comment on other people's launches, answer questions in your category, and don't mention your product. That window is our planning estimate, not a Product Hunt number. The point is that people have seen your name before, when you weren't asking for anything.

Product Hunt is one day in a longer sequence. Our launch directories guide orders the rest by lead time, so the listings with long queues go in before your Product Hunt day, not after it.

A date-picking worksheet

Run this against every product you own.

1. List every product and its URL. Include old launches. A product you launched in March still holds the clock.
2. Reduce each URL to its root domain using the steps above.
3. Group by root domain and sort by date. A launch that happened beats a planned one.
4. Check each gap against the launch before it on the same domain. Compare with the nearest earlier launch, not the first one. Add six calendar months, not 180 days. The two differ by a few days, and the rule says months.
5. Pick the weekday, then convert 12:01am Pacific for that specific date using the table above.
6. Resolve any collision in one of three ways: combine the products into one launch, request an early relaunch if the change genuinely qualifies, or move the date.

A hypothetical worked example, for a founder with three tools on acme.co:

Product	URL	Root domain	Product Hunt date	Earlier launch on this domain	Earliest allowed
Acme Forms	forms.acme.co	acme.co	Tue 9 Jun 2026 (launched)	none	any date
Acme Sign	sign.acme.co	acme.co	Tue 13 Oct 2026 (planned)	9 Jun 2026	Wed 9 Dec 2026
Acme Notes	notes.acme.co	acme.co	not yet dated	9 Dec 2026, if Sign moves there	Wed 9 Jun 2027

Acme Sign's October plan fails by eight weeks. The earliest date six calendar months later is a Wednesday, which suits a Tuesday-to-Thursday preference anyway. (A 180-day count, which is what LaunchBeam uses, would say 6 December, a Sunday. The calendar-month date is the safer one.) If Sign moves to 9 December, Acme Notes can't launch on Product Hunt until June 2027. At that point, one combined launch looks better than three staggered ones.

Afterwards, our post on working out which launch channel worked covers how to measure whether Product Hunt earned its place.

Where LaunchBeam fits

On plans that allow more than one product, LaunchBeam checks the whole workspace for Product Hunt root-domain collisions. When two products share a root domain and their Product Hunt dates fall less than 180 days apart, the Products page shows a banner naming both and the earliest date the later one can go up, and the plan task is marked "Blocked by another launch". A recorded submission counts over a planned date. It never blocks a submission; whether your update qualifies is Product Hunt's call. The check has limits. It counts 180 days, not six calendar months. It covers only the root-domain half of the rule, so two products from one company on different domains won't be flagged. And its short built-in suffix list errs toward warning, so products on a shared host such as vercel.app are flagged too, which is your prompt to email Product Hunt.

Product Hunt's public API can't create a post (its v2 mutations cover following users and nothing else), so LaunchBeam doesn't post there; our API guide covers which platforms allow it. Instead, LaunchBeam writes the tagline, a description of up to 260 characters, the first maker comment and topics, plus a checklist of gallery and thumbnail sizes, and emails them to a workspace owner or admin at the time you scheduled. Once you've set a launch date, the plan gives its go-live time in Pacific and UTC, daylight saving included, and suggests the next Tuesday, Wednesday or Thursday if your date falls outside them.

The Free Trial allows one product, so there's nothing to compare there, and Product Hunt is one of six premium directories locked on it: the submit task and the tracker row where you record the submission need a paid plan. Pricing lists what each plan includes.