Product launch kit: everything a directory will ask you for

Every startup directory asks for roughly the same twenty things, in slightly different shapes. If you prepare them once, at the right lengths and sizes, every submission afterwards is copy and paste. If you do not, you will write your tagline eleven times and resize your logo four. This is the list, with the limits we have actually hit while submitting to these directories.

Copy

Field	Target	Why that length
Name	Under 40 characters	Product Hunt and 10Words cap at 40; BetaList and Indie Hackers at 50; AlternativeTo at 60.
Tagline	Under 40 characters, with a 60-character variant	BetaList's pitch is 40. Product Hunt's tagline is 60. Write the short one first; it is harder.
Short description	100 to 160 characters	Huzzler wants 100, AlternativeTo's short pitch 160. 10Words wants the entire pitch in 70 characters.
Medium description	Around 260 characters	Product Hunt's description field. Many "about" fields land here.
Full description	600 to 1,000 characters	BetaList allows 600, AlternativeTo 1,000. Two to four short paragraphs: what it is, who it is for, what makes it different, pricing in a line.
Maker name and bio	Name plus one sentence	Indie Hackers, Peerlist and launch platforms show the maker. One sentence is enough.

Write the shortest versions first. A 40-character tagline forces you to decide what the product actually is; the 1,000-character description is easy once that is settled.

Images

Asset	Prepare	Notes
Logo	Square PNG, 512×512 and 1024×1024, plus a version under 200 KB	TinyLaunch rejects logos over 0.2 MB. Transparent background where possible; some sites put it on dark.
Screenshots	3 to 5, 1600×1000 or 1280×800, plus a compressed set under 400 KB each	Joinly rejects screenshots over 400 KB. Show the product, not a marketing collage. First screenshot is the one that gets used as the thumbnail.
Social preview	1200×630	Your own site's Open Graph image; some directories pull it automatically, so make sure it exists.
Gallery or video	Optional	Product Hunt and Dev Hunt support video. Dev Hunt will generate one from your description and screenshots.

Directories with odd requirements exist — Resource.fyi wants a non-standard dimension, AI Depot allows neither logo nor screenshots — and you will not know until you are on the form. Keep the originals at high resolution so you can produce whatever size is asked. If you use Launch to Win, the package's press-asset download gives you the common sizes in one go.

Metadata

• Categories — two or three from the usual taxonomy (AI, developer tools, productivity, marketing, SaaS, no-code and so on). Every directory has its own list; pick your nearest matches ahead of time.
• Keywords — five to ten. Directories with search use these. Think in terms of what someone types, not what your product is called.
• Alternative to — two or three well-known products. AlternativeTo, SaaSHub and comparison sites index on this, and "X alternative" searches are where directory traffic actually comes from.
• Platforms — web, iOS, Android, Mac, Windows, Chrome extension, CLI. Several forms have checkboxes for these.
• Pricing — model (free, freemium, paid, one-time), lowest paid price, currency, period. Structured, so it can be pasted consistently.
• Launch date and status — some sites (BetaList) only take new products; some ask whether it is live, in beta or coming soon.
• Tech stack — optional, but MakerThrive, We Use Rails and similar sites ask.

Links and contact

• Website URL, ideally with UTM parameters per directory so you can see which listings send traffic.
• X / Twitter, GitHub, LinkedIn, and any of Facebook, Instagram, YouTube you actually use.
• A support or contact email you check. Approval emails arrive weeks after submission.
• Product Hunt page URL once it exists; several directories ask for it.

Accounts

Not part of the package, but part of the preparation: nearly every directory requires an account. Set aside the first ten minutes of a submission session for signups. Use one email, prefer Google or GitHub sign-in where offered, and store the logins — you will be back for the next product.

On Launch to Win the package editor has a field for each of these, shows the character count against every directory's limit as you type, and resizes assets for download. Build one from your URL, then follow the submission guide.