What to Prepare Before Submitting Your Product
A submission checklist covering product copy, logos, preview images, and the website metadata BetterLaunch can import.
Preparing a reusable submission kit saves you from rewriting a tagline or recropping a screenshot in every form. Start with clear source copy and high-resolution assets, then export versions for each platform.
The sizes and lengths below are recommended working specifications, not universal upload requirements. Platform rules take precedence. We checked the cited rules on October 6, 2026; confirm the current form before submitting.
1. Gather the product essentials
| Asset | Recommended preparation | What to check |
|---|---|---|
| Name and links | Consistent product name, HTTPS website, trial or download links | Public access and the correct destination |
| Tagline | 6–12 words, plus an English version within 60 characters | Audience and task are clear |
| Short description | 40–80 words, plus a version within 260 characters | Purpose, workflow, and one useful distinction |
| Full description | 250–400 words | Use case, steps, features, pricing, and limitations |
| Logo | 1024×1024 square master; 512×512 and 240×240 PNG exports | Recognizable at 32×32 and 64×64 |
| Screenshots | 3–5 images; 1920×1080, 16:9 masters | One task per image, readable interface |
| Gallery and social images | Separate 1270×760 gallery and 1200×630 OG exports | Recompose rather than stretch |
| Demo video | 30–60 seconds, 16:9, 1080p MP4 master | Actual workflow, results, captions |
| Maker details | Name, avatar, bio, usernames, contact email | Login, verification, collaborators |
| Launch plan | Date, timezone, plan, offer terms, first comment | Confirmed publication versus submission or queue |
Word counts and character limits are different. Spaces and punctuation may count toward a form’s limit. For Chinese copy, a useful starting point is 15–30 characters for a tagline, 80–150 for a short description, and 400–800 for the longer version. Use the form’s counter to check what actually fits.
2. Prepare product copy and assets
2.1 Keep the name, links, and category consistent
Use the product name alone, without a slogan or unsupported superlatives. Keep its spelling consistent across the website, profiles, and files. Add a version number only when it identifies an actual release.
The primary link should lead to a public HTTPS page that explains the product and lets visitors continue to a trial, download, or signup. Keep app-store and demo links separately labeled. Check redirects and mobile access; a press article is not a substitute for the product link.
Browse BetterLaunch’s categories and tags to see how similar products are organized. Choose the closest primary category and prepare 3–5 relevant candidate tags, then respect each platform’s allowance. State whether the product is live, in private or public beta, or collecting a waitlist. An invitation to “try it now” should not lead only to a registration-of-interest form.
2.2 Write a tagline about the task
Start with the audience and what they can accomplish. Add the method or a meaningful distinction if space permits. Avoid repeating the name or using phrases such as “the ultimate all-in-one solution.”
For the fictional planner FocusPad, “Daily planning for independent makers” gives a clear starting point. It is a writing example, not a claim about a real product.
Keep both a short and a fuller version. BetterLaunch imports at most 200 characters, and its tagline field has the same limit. Edit deliberately before import rather than relying on automatic truncation.
2.3 Prepare descriptions you can shorten
The short description should explain the problem, how the product helps, and a reason to try it. For the same fictional example: “FocusPad gives independent makers a daily planning workspace to organize tasks and keep the day’s work in view.”
Build the full description around:
- Audience and problem: who needs it and what is awkward about their current approach.
- Workflow: the input, two or three main steps, and the result.
- Core features: three to five capabilities, each explained by what it does.
- Example: a reproducible scenario, clearly separated from real customer evidence.
- Pricing and limits: free tiers, trials, account requirements, quotas, release status, and unsupported features.
- Next step: where to try, download, or join.
Keep a plain-text master and apply formatting only where supported. BetterLaunch allows up to 5000 characters in the description, but that is a ceiling rather than a target. Save a much shorter version for compact fields instead of pasting a long description and letting the form cut it off.
2.4 Export a logo that works at small sizes
Keep an editable vector source and a square 1024×1024 PNG master, with 512×512 and 240×240 exports. PNG preserves transparency; also prepare a light-background version if the transparent mark disappears on dark cards. Do not assume every platform accepts SVG uploads.
Leave about 10% padding around the mark for circular crops. Avoid packing a slogan or URL into the logo. Inspect it at 32×32 and 64×64 on light and dark backgrounds.
Keep the logo, favicon, and preview image separate. The logo identifies the brand, the favicon serves browser tabs and icon retrieval, and the preview shows the product. A 32×32 favicon and 180×180 touch icon are useful additional exports.
2.5 Make screenshots explain the product
Prepare 3–5 screenshots in a useful sequence: overview, main action, result, and an optional distinctive feature. Lead with the product rather than a company introduction. Use demo data and remove private names, email addresses, keys, and billing information.
A 1920×1080, 16:9 master works well for landscape screenshots and recordings. Recompose for 1270×760 or 1200×630 instead of stretching the image. Enlarge the relevant interface area or split a crowded screen into two images. For a mobile app, retain portrait captures and place them in a landscape layout when needed.
Leave roughly 5%–10% edge clearance for important content. Check the export at card size: if the key interface or caption is unreadable, simplify it. Keep PNG, JPEG, or WebP versions as appropriate for the platform. Aim for static upload files under 2 MB while retaining uncompressed masters; this is a preparation target, not a shared platform limit. Check text quality after compression.
2.6 Record a short demo with a visible result
A 30–60 second demo can introduce the task, show the main actions, and finish with the result and trial link. Record a 16:9, 1080p MP4 master, with readable interface text, deliberate cursor movements, and captions for muted viewing.
Keep intros short. Label prototypes or planned features if the workflow is not yet available. Save both the local file and a publicly playable hosted link. Hosting requirements differ: an MP4 file or arbitrary video URL will not work in every form.
2.7 Prepare the maker account and launch details
Gather a name, clear avatar, short bio, platform usernames, and monitored email address. Confirm login access and email delivery; complete identity verification where required. Check collaborators’ usernames and product ownership before launch day.
State whether the product is free, paid, or paid with a trial or free plan. Include currency, billing period, quotas, and what happens after the trial. If offering a discount, spell out eligible plans, expiry, redemption steps, and restrictions.
Track the platform, selected plan, intended date, timezone, confirmed date, and responsible person. Draft a first comment explaining why you built the product, what it helps with, and what feedback you want. Submission, queue entry, and publication are separate states; coordinate announcements around confirmed publication.
BetterLaunch’s leaderboard includes weekly, monthly, and yearly rankings. Weekly results group products by launch batch; monthly and yearly results include products published in the UTC calendar period. Finalized results remain fixed. Plan around the confirmed publication time; the guide explains the rules.
3. Adapt the kit to each platform
| Platform | Check separately |
|---|---|
| Product Hunt | Recommended 240×240 thumbnail and 1270×760 gallery images; at least 2 gallery images for display; description within 260 characters; full, non-private YouTube video link |
| Indie Hackers | Prepare the product profile, maker bio, and updates separately; publish business figures only when accurate and intended for disclosure |
| Peerlist | Complete name, tagline, URL, images, tags, description, and category; verify launcher identity and the current launch window |
| BetaList | Early-stage eligibility, a distinct informative landing page, and a working signup or access path |
| Uneed | Schedule after import; queue, retention, and backlink conditions vary by launch option |
| Microlaunch | Check the basic queue and paid placement, promotion, or feedback services; plan follow-up time |
| TinyLaunch | Check free ranking, winner badges, and reciprocal-link requirements; confirm you can place a badge if needed |
| Firsto / OpenHunts | Check queue and paid scheduling, ranking-based link benefits, and any website badge requirement |
| BetterLaunch | Name up to 100 characters, tagline 200, description 5000, and at most 5 tags; free submission currently requires verified DR of at least 10 and is limited to 3 non-rejected free products per account in total |
Product Hunt’s image sizes are recommendations; the description cap and gallery-display threshold are constraints. Missing dimensions in this table do not mean other platforms have no upload limits. Refer to Product Hunt’s posting guide, Peerlist’s profile guide and verification announcement, BetaList’s criteria, Uneed’s rules, Firsto’s plans, and OpenHunts’ plans.
If you have not chosen your channels, compare the 10 launch platforms. If backlinks are a priority, read about backlinks and DR before checking each plan’s link conditions.
4. Organize a reusable submission folder
Name files by purpose: logo-512.png, logo-240.png, screenshot-01-overview.png, gallery-ph-1270x760.png, og-1200x630.png, and demo-1080p.mp4. Keep copy separately by language and length. Track which versions each platform uses, submission status, and the final listing URL.
When pricing or features change, update the master and then the published listings. Visitors should not find a free-product promise on a launch page after the website has switched to paid access.
5. How BetterLaunch reads your website
The submission form can fetch information from a public website URL. For the name, it prefers og:site_name, then og:title, then the page <title>. For the tagline, it prefers og:description and falls back to the standard meta description.
It also attempts to import og:image as the product thumbnail and retrieve a site icon for the logo. When the relevant services are available, the page content can be used to draft a description and suggest a category and tags. Domain Rating is looked up separately.
Review the imported details before submitting. Page titles can include extra branding, images may not crop well, and an automated summary can miss an important use case. If anything is missing or the import fails, you can enter the copy and upload images yourself.
5.1 Give your homepage standard metadata
Put meaningful metadata in the initial HTML <head> of your public landing page. Here is an example to adapt to your own product:
<title>FocusPad — A quiet workspace for daily planning</title>
<meta name="description" content="Plan your day in a simple workspace built for independent makers." />
<meta property="og:site_name" content="FocusPad" />
<meta property="og:title" content="FocusPad — Plan your day with less clutter" />
<meta property="og:description" content="A simple daily planner for independent makers." />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://example.com/" />
<meta property="og:image" content="https://example.com/images/product-preview.png" />
<link rel="icon" href="/favicon.ico" />
<link rel="icon" type="image/png" sizes="32x32" href="/icons/icon-32.png" />
<link rel="apple-touch-icon" href="/icons/apple-touch-icon.png" />
<link rel="canonical" href="https://example.com/" />
Use an absolute HTTPS URL for the Open Graph image. A 1200 × 630 image is a practical starting point for social previews, not a BetterLaunch upload requirement. Keep important content away from the edges so different crops remain readable. The icon should identify the product; the preview image should explain or show it.
Canonical URLs and touch icons are useful to include on your website, though BetterLaunch does not necessarily import them. An external favicon service may also still have an older icon cached.
5.2 Make the information accessible
Open your homepage and image URLs in a private browser window. Check that they work without a login or session cookie, and that signed URLs have not expired. Ordinary page requests should return your content rather than a challenge page. Include important metadata in the initial HTML instead of relying entirely on client-side JavaScript to add it later.
Next, fetch your website details in the submission form. Review the name and tagline, replace any unsuitable images, and check the suggested description, category, and tags. Open the website link too, so you know where new visitors will land.
For launch options and costs, see the BetterLaunch guide and current plans. Complete metadata saves you some typing, but you still need to check the final submission.