How to submit your startup to directories (the complete 2026 guide)

Startup directories are the least glamorous and most reliable distribution channel a small product has. A listing on AlternativeTo or SaaSHub keeps sending visitors for years. A Product Hunt or Uneed launch gives you a day of attention and a permanent page. Hacker News can give you a thousand signups before lunch. None of it requires an audience, a budget or a marketing hire. It requires filling in forms.

This guide is the process we use ourselves, after submitting real products to every directory in our list. It is written for someone doing this for the first time, but the last section is about doing it for the fifth product, because that is where most people give up.

1. Prepare everything before you open a single form

The single biggest time sink is opening a submission form, discovering it wants a 40-character pitch or a 512×512 logo, and stopping to write or resize on the spot. Do that once, up front, and every form after that becomes copy and paste.

At minimum you need:

• Name — the short product name, not "Acme – the best analytics tool for startups". Most forms cap it at 40 to 60 characters.
• Tagline — one line, under 60 characters. Product Hunt shows it everywhere. BetaList wants it under 40.
• Short description — one or two sentences, around 160 characters. AlternativeTo's "short pitch" lives here.
• Full description — two to four paragraphs, 600 to 1,000 characters. Product Hunt cuts at 260; AlternativeTo allows 1,000.
• Logo — square PNG, at least 512×512, and a version under 200 KB (TinyLaunch limits logos to 0.2 MB).
• Screenshots — three to five, 16:10 or 16:9, and a compressed set under 400 KB each for the picky sites.
• Pricing — model (free, freemium, paid, one-time), lowest price and period.
• Categories and keywords — a handful each. Directories index on these.
• "Alternative to" — two or three well-known products yours replaces. AlternativeTo, SaaSHub and most comparison sites ask for this and it drives most of their search traffic.
• Links and contact — website, X, GitHub, LinkedIn, a support email.

The full list, with the limits we have hit, is in the launch package checklist. If you build the package on Launch to Win, pasting your URL drafts most of this for you and the editor shows which fields overflow which directory.

2. Submit in the right order

Not every directory is equal, and some have queues measured in months. Order matters.

1. The long free queues first. Uneed, MicroLaunch, Open-Launch, StartupBase and similar sites put free submissions on a two-to-three-month waiting list. Submit to these on day one so the queue runs while you do everything else.
2. The evergreen directories. AlternativeTo and SaaSHub. No launch-day dynamics, just a permanent listing that ranks for "X alternative" searches. Fill these out completely — the "alternative to" field especially.
3. Your launch day. Product Hunt, and if the product is technical, Show HN on Hacker News the same morning. These reward preparation and timing; see the Product Hunt launch checklist.
4. The rest of the well-rated list. BetaList for new products, Peerlist Launchpad, Indie Hackers, TinyLaunch, Startup Fame, Huzzler, SoloPush and the others we rate Good. Work through the best-rated directories over the following week.
5. Niche and paid directories last, and only where the audience matches. See our notes on paid directories.
6. Then the places that are not directories. Subreddits, dev.to, AppSumo, app marketplaces. No form to autofill, but worth a morning each. We keep that list in startup communities, marketplaces and deal sites.

3. Expect to create an account almost everywhere

Very few directories accept anonymous submissions. Plan on a signup per site, usually with Google or GitHub. Use one email you check, because approval notices and "your listing is live" emails arrive weeks later. Some sites do odd things: a few make you subscribe to their newsletter to confirm the submission, and one sent us a signup SMS that never arrived. Our per-directory reviews mention these so you are not surprised.

4. Fill each form from your package, not from memory

Once the package exists, a submission is mechanical: open the directory's submit page, paste each field, upload the logo and screenshots, pick a category, submit. Two or three minutes per site.

Three ways to make it faster:

• Copy-ready fields. Each directory page on Launch to Win shows your package's fields already trimmed to that site's limits, one click to copy each.
• Chrome autofill. The extension fills the form in one click, including file uploads, and flags fields that are over the limit or empty. Forms it has never seen are mapped by AI on the spot. Details in the autofill guide.
• An AI agent. With WebMCP an in-browser agent can read your package and fill the form itself while you review.

5. Avoid the common rejections

• Backlink requirements. Some directories (Uneed's free tier, Fazier, Twelve Tools, Turbo0, Indie.Deals) require a badge or link back to them before they list you. Decide up front whether you will do this; it is also why their domain ratings look so high.
• Image rules. Oversized logos and screenshots are the most common silent failure — the form accepts the submission and then the listing never appears. Keep the compressed set ready.
• Category mismatch. Dev Hunt and Startup Stash only accept developer tools; We Use Rails only accepts Rails apps. Read the directory page before you submit.
• Thin listings. A one-line description with no screenshots gets rejected or buried. Directories reward complete listings because they look better on the directory.
• Existing products on new-product sites. BetaList is for products that are actually new. A two-year-old product will be declined.

6. Track what went where

Write down, per product and per directory: submitted date, status, and the listing URL when it goes live. It sounds trivial. It is not, three months later, when the free queue on a site clears and you cannot remember whether you submitted product two or only product one. A spreadsheet works for one product. Launch to Win's submission dashboard does it per package, which matters as soon as you have more than one.

7. Do it again for the next product

Everything above compounds. The second product reuses your directory accounts, your knowledge of each form and your list of which sites are worth it. What does not carry over is the copy and the assets — those are per product, and they are the reason most portfolios end up with one well-listed product and four that were never submitted anywhere.

The fix is to treat the package as the unit of work: one package per product, complete, and then the submission process is identical every time. That is the whole idea behind Launch to Win, and the multi-product playbook goes through it in detail.