Growth

What to Send an Editor: A One-Page Press Kit for Indie Makers

By praneetbrar18 min readUpdated
What to Send an Editor: A One-Page Press Kit for Indie Makers

What to send an editor so they can write about your product: a one-page press kit with ten fields, real image sizes, a fill-in template and a 10-point check.

A one-page press kit is a single page (or a single email) that gives an editor every fact they need to write about your product without having to write back: a one-line description, who it is for, exact pricing, a short founder quote, three to five screenshots with alt text, logo files, only the numbers you can defend, one clean canonical URL, and a contact who answers. If an editor can draft a fair paragraph from that page alone, the kit works. If they have to ask what it costs or which logo to use, you have added a step between them and the story, and busy people skip stories with extra steps.

Last checked: November 17, 2026

This guide is about the prep work, the thing you build once and hand over every time. It is not about finding journalists or writing the pitch (the Aura++ guide to getting press coverage without a PR agency covers that), and it is not about where to get a short article written (IndieHunt has a separate guide to getting a short editorial write-up of your indie product). This one is about what goes in the envelope. You get the ten fields, the image sizes real platforms ask for, the gaps that quietly kill write-ups, a fill-in template, a made-up example, and a 10-point check to run before you hit send.

Why one page beats a folder of files

The indie games world worked this out years ago. Rami Ismail of the studio Vlambeer built a free tool called presskit() because, as its homepage puts it, when the press finds out about a game but doesn't have access to information and media for it, "they can't write about it." He says the tool was shaped with feedback from journalists, including Russ Frushtick of Polygon, and that a developer should be able to build a full press page in 30 to 60 minutes. That last number is the point: a press kit is a small, finite job, not a branding project.

What editors actually value backs this up. In Muck Rack's State of Journalism 2025 survey (1,515 journalists in the final analysis, surveyed in April 2025), journalists were asked what a PR person should ideally offer along with a story pitch. The answers:

  • Clear relevance to my beat: 66%

  • Interview access to relevant sources: 62%

  • Original data or research: 42%

  • High-resolution images: 36%

  • Exclusive or embargoed content: 33%

  • Pre-written quotes: 19%

  • Social media copy: 4%

Two things stand out for a solo maker. First, a person they can talk to (62%) matters far more than a polished quote (19%), so your kit should make it obvious that you are reachable, not just quotable. Second, real data (42%) and good images (36%) are each wanted by over a third of respondents, and both are things a press kit can hold in advance. Social media copy barely registers. The same survey found 86% of journalists disregard pitches irrelevant to their coverage, but that is a pitching problem. The kit's job is narrower: once someone is interested, remove every reason to stall.

A folder of 40 files fails that job differently: the editor has to open each file to learn what is in it. One page, with every fact written out and every file linked, can be read in two minutes.

The ten things an editor needs, in one place

Here are the fields, in the order an editor tends to use them. The first three answer "what is this?", the middle ones give them material, and the last ones let them publish without guessing.

1. A one-line description

One sentence that says what the product does, for whom, in plain words. Product Hunt's own guide to building a launch page gives a useful test: "if someone reads only your name and tagline, do they know what the product does?" It caps taglines at 60 characters and descriptions at 500, which is a sensible pair to keep ready: a short line and a longer paragraph. Write both, and then use them word for word everywhere so the editor doesn't find three versions. If you are stuck on the short one, the free launch tagline generator on IndieHunt gives you drafts to react to; edit whatever it gives you until it sounds like something you would say out loud.

Also write down the product name exactly as it should be spelled. Big companies take this seriously. Linear's brand page says the name is always spelled with a capital L and asks people not to write "Linear app". GitHub's logo guidelines spell out that GitHub is one word "with a capitalized G and H." If your name is camel-cased, lower-cased or has a dot in it, say so in the kit, or it will be "corrected" for you.

2. Who it is for

One or two sentences naming the actual people who use it, as specifically as you honestly can. "Freelance bookkeepers who chase invoices for 10 to 30 clients" gives an editor an angle. "Businesses of all sizes" gives them nothing. If you know who it is not for, add that too; a clear non-goal makes the description more believable.

3. Exact pricing

Write the real numbers: plan names, price, billing period, currency, and what the free plan includes, if there is one. "Freemium" or "affordable" forces a follow-up email. "Free for one project; Pro is $9 a month or $90 a year, billed in USD" does not. If pricing is changing soon, give the price that will be live when the article is likely to run, and say from when. If you have usage limits that matter, list them. Editors hate correcting a wrong price after publication, so a dated, exact price helps.

4. A short founder quote, plus a way to reach you

Give one or two sentences in your own voice about why the product exists. Not a slogan. Something a person would actually say: what annoyed you, what you decided to do differently, or what surprised you once people started using it. Mark it clearly as approved for use, so the editor knows they can print it.

Then, right under it, offer yourself. Given that only 19% of journalists in the Muck Rack survey wanted pre-written quotes and 62% wanted access to a source, the line "Happy to do a 15-minute call or answer questions by email, usually same day" may do more for you than the quote itself.

5. Three to five screenshots, with alt text and sizes

Pick the few screens that explain the product: the main view, the one action people come for, and the result. Use demo data, never a real customer's names or emails. Export them as PNG or high-quality JPG, landscape, at a decent width, and name the files so they make sense out of context (pantrybell-shopping-list.png, not Screenshot 2026-11-03 at 14.22.png). For how to stage and design the screens themselves, MakerHunt already has a full guide to making product screenshots that get clicks; this section is only about packaging them for an editor.

There is no single press standard for image size, but the platforms you probably already use publish theirs, and matching one of them means you only export once:

Where

What they ask for

Source

Product Hunt gallery image

Recommended 1270x760px

Product Hunt launch guide

Product Hunt logo (thumbnail)

Recommended 240x240px; JPG, PNG or GIF, up to 2MB

Product Hunt launch guide

Mac App Store screenshots

16:10, one of 1280x800, 1440x900, 2560x1600 or 2880x1800

Apple App Store Connect

App Store screenshots in general

JPEG, JPG or PNG; up to 10 per device size; no transparency

Apple App Store Connect

Google Play app icon

512x512px, 32-bit PNG, max 1024KB

Play Console Help

Google Play feature graphic

1024x500px, JPEG or 24-bit PNG (no alpha)

Play Console Help

Google Play screenshots

Min 320px, max 3840px per side, long side no more than twice the short side

Play Console Help

Sources for the table: Product Hunt's launch page guide, Apple's screenshot specifications, and Google's help page on Play store preview assets, all read on November 17, 2026. Note the Product Hunt logo limit: 2MB, not 3MB, whatever older checklists say.

A practical rule for a web product: export landscape screenshots at 1270x760 or larger in the same ratio, keep each file under 2MB, and list the pixel size next to each file so the editor knows whether it fits without downloading it.

Write alt text for every screenshot and put it in the kit next to the file. Editors who publish on the web need it, and if you don't supply it, someone in a hurry will type "screenshot". The W3C's alt decision tree says an image that adds meaning should get "a brief description of the image in a way that conveys that meaning," and that text shown inside an image should be in the alt if it isn't present anywhere else. For a product screenshot, that means saying what the screen shows and what matters on it, in one sentence: "Pantrybell's shopping list, with three items flagged as running low."

6. Real numbers, and only real ones

Numbers make a story concrete, and original data was wanted by 42% of journalists in the Muck Rack survey. But the rule here is strict: include only numbers you can defend if the editor asks how you got them, and date every one. "1,240 registered accounts as of November 1, 2026" is useful. "Thousands of happy users" is not a number.

If you don't have numbers yet, leave the section out. A kit with no metrics is completely normal for a young product, and a missing number does far less damage than a soft one that a reader later questions. Good candidates, if you have them: active users or paying customers (say which), how long the product has been live, a usage figure tied to what the product does (lists created, invoices sent), and team size. Don't round up, don't mix "signed up" with "active", and don't put revenue in unless you are comfortable seeing it in print.

7. One canonical URL

Give the editor the exact URL you want in the article, and make it clean: https, your preferred version of the domain (with or without www, whichever your site redirects to), no tracking parameters, no link shortener. If you want to track clicks, do it on your side, not by putting UTM tags in a journalist's link.

This matters beyond tidiness. Google's documentation on specifying a canonical URL explains that canonicalization helps consolidate signals, such as links, from duplicate URL variants into one preferred URL. You make that job easier by handing out the preferred URL in the first place. If you want the link to point somewhere other than your homepage, such as a pricing page or a specific feature page, say which and why.

8. Logo files that work on any background

Include your logo as an SVG and as a PNG with a transparent background, in a version for light backgrounds and one for dark backgrounds, plus a square icon. A logo pasted into a Word document, or a JPG on a white box, is the most common file problem editors run into, because it looks broken on any page that isn't white.

Look at how established companies present theirs. Stripe's newsroom offers "logos, badges, product screenshots, and executive team photos" for download, and says its wordmark comes in three colors: slate and blurple for light backgrounds, white for dark ones. You don't need a brand guide that detailed. One line telling an editor which file to use where is enough.

9. A founder photo and a two-line bio

If the story mentions you, the editor may want a photo. A clear, well-lit head-and-shoulders shot is plenty. Add a two-sentence bio: your name, your role, and one relevant fact about why you built this.

10. A contact who answers

An email address you check, your name, and your time zone. A phone or messaging handle is optional. If the person who answers press questions is not the founder, name them. The worst gap in any press kit is a contact form that sends to an inbox nobody reads.

Overhead view of hands about to write on a blank sheet of paper next to a black notebook and a laptop

The gaps that quietly stop a write-up

Most kits don't fail because something is badly written. They fail because one small thing is missing and the editor moves on while waiting for an answer. The usual gaps:

  • "Contact us for pricing." For a self-serve indie product, this reads as hiding something. Even a starting price helps.

  • Numbers without a date or a definition. "10,000 users" with no date and no explanation of what counts as a user invites a question nobody has time to ask.

  • Images locked behind a permission request. A shared drive folder that says "request access" is a dead end at 11 p.m. on deadline. Test every link in a private browser window.

  • Screenshots with real customer data. An editor won't publish someone else's email address, and blurring it themselves is extra work.

  • The product name spelled three ways. The kit, the site title and the app store listing should all agree.

  • A quote that is really ad copy. "Revolutionizing the way teams collaborate" won't get printed. A real sentence might.

  • Attachments that bounce. Twenty megabytes of screenshots attached to a first email can trip size limits or spam filters. Link to the files; don't attach them, unless the editor asks.

  • No "who it's for". Without it, the editor has to guess your audience, and a wrong guess can make the product look like a poor fit for their readers.

The copy-paste press kit template

Copy this into a page on your site (a plain /press URL is fine) or into a document you can link to. Replace everything in square brackets. Delete any line you can't fill honestly rather than padding it.

  • Product name (exact spelling): [Name, with notes on capitalization]

  • One-line description (under 60 characters): [What it does, for whom]

  • Short description (under 500 characters): [What problem it solves, for whom, and the two or three features that matter most]

  • Who it is for: [Specific audience] / Not for: [Optional non-goal]

  • Pricing (as of [date]): [Free plan details]; [Plan name] [price] per [period], [currency]

  • Canonical URL: [https://yourdomain.com/, no tracking tags]

  • Founder quote (approved for publication): "[One or two sentences in your own words]" [Name, role]

  • Numbers (only if real; each with a date): [Metric, figure, as of date, how it is counted] or delete this line

  • Screenshots: [file name, pixel size, alt text] for each of 3 to 5 files, linked

  • Logos: [SVG and transparent PNG links; light-background and dark-background versions; square icon]

  • Founder photo and bio: [Photo link]; [Two-sentence bio]

  • Contact: [Name, email, time zone; "available for a call or email questions, usually same day"]

  • Last updated: [Date]

The "last updated" line is easy to forget. It tells the editor whether the prices and numbers are current, and reminds you to revisit the kit.

An illustrative example: a made-up maker fills it in

Everything in this section is invented for illustration. Pantrybell, its founder and its figures are not real.

Pantrybell is a made-up web app that tracks what is in a household pantry and builds a shopping list when items run low. Its imaginary founder, Asha, spends one evening filling in the template. Here is what her kit looks like, and the choices she makes:

  • Product name: Pantrybell (one word, capital P only).

  • One-line description: A pantry tracker that writes your shopping list. (49 characters.)

  • Who it is for: Households of two to five people who shop once a week and keep forgetting what they already have. Not for restaurants or inventory teams.

  • Pricing (as of November 2026): Free for one pantry and one shared list; Household is $4 a month or $40 a year, USD, for unlimited lists and up to six members.

  • Canonical URL: https://pantrybell.example/ (she removes the ?ref=newsletter tag she had been using).

  • Quote: "I built it after buying a fourth jar of cumin in one year. The app is mostly a very polite way of telling you to check the cupboard first." Asha, founder.

  • Numbers: She has 310 households with at least one list, but she isn't sure how many are active each week, so she lists only "310 households have created a list (as of November 10, 2026)" and leaves out anything about active users until she can measure it properly.

  • Screenshots: Three files at 1270x760, all under 2MB, using a demo pantry with made-up items, each with one-line alt text.

  • Logos: SVG and transparent PNG, light and dark, plus a 240x240 square icon she also uses on Product Hunt.

  • Contact: Her email, "UK time, I reply the same day."

Two decisions are worth copying: she cut a weak number instead of guessing, and she reused one image size everywhere, so she only exported once. None of this guarantees coverage; it just means nothing in the kit gets in the way.

A man holds a printed one-page document while a laptop beside him shows charts

Where the kit gets used

Once it exists, the same page does several jobs. Link it from your site footer as a press page. Paste the link at the bottom of any pitch, so the email can stay short and the details live one click away. Send it straight back when someone replies "tell me more". And use it whenever a publication asks you to submit product details for a write-up, because most submission forms ask for the same fields.

That last case is where a kit turns into an article fastest. As one example, a news-style story on Hed Press is written from the facts you send: who the product is for, what it does, and the URL. Its pricing page, checked on November 17, 2026, lists a free reciprocal plan (your site credits hedpress.com while the page is live), a free nofollow plan with no credit, and a $29 editorial package; the product link is dofollow on the reciprocal and $29 plans, and the page says it does not promise a ranking or traffic. Disclosure: Hed Press is run by the same team as IndieHunt, so treat it as one example among many places that need the same facts.

Your 10-point check before you send it

  1. The product name is spelled the same way in the kit, on your site and in any store listing.

  2. The one-line description fits in 60 characters and says what the product does without a buzzword.

  3. "Who it is for" names a specific group of people.

  4. Pricing is exact, has a currency and a billing period, and is dated.

  5. Every number is real, dated and defined, and you deleted any you couldn't defend.

  6. The quote sounds like a person, is marked as approved, and sits next to an offer to talk.

  7. Three to five screenshots use demo data, each has a pixel size, a sensible file name and alt text, and each file is under 2MB.

  8. Logos come as SVG and transparent PNG, in light and dark versions, plus a square icon.

  9. The canonical URL is clean: https, your preferred domain version, no tracking tags or shorteners.

  10. Every link in the kit opens in a private browser window without a sign-in or access request, and the contact email gets a reply within a day.

FAQ

Do I need a PDF press kit?

Not usually. A web page is easier to keep current, easy to link from a pitch, and lets the editor copy text and download only the files they need. If someone asks for a PDF, export the page. Keep the page as the master copy.

What should I send a journalist in the first email?

A short note about why the story fits what they cover, plus a link to the press kit, not the kit pasted in full and not a pile of attachments. The Muck Rack 2025 survey found 69% of journalists prefer pitches under 200 words, so let the kit carry the detail. How to write that note and who to send it to is covered in the Aura++ press coverage guide linked at the top.

What if I don't have any metrics yet?

Leave the numbers section out. Use the space for something you can stand behind instead: a specific "who it's for", exact pricing, and a quote about why you built it. An honest kit with no figures is much better than one with a figure you can't explain.

No kit can promise that. Editors decide what to cover, and search engines decide what to do with any link. What a good kit does is remove the reasons an interested editor might stall, so the decision comes down to whether the story fits their readers.

Do it in one sitting

Block out an hour. Write the name, the one-liner and the "who it's for" line first, because everything else hangs off them. Add pricing, the URL, the quote and the contact, then export three screenshots and your logos, write the alt text, and date the page. Run the 10-point check and you are done until something changes.

press kitstartup press kitindie maker press kitwhat to send a journalistmedia kitpress pageproduct screenshotsfounder quotePR for startupsGrowth
IndieHunt

Launch on IndieHunt

Submit your product to get featured in the weekly launch and reach indie founders looking for new tools.

Submit your project

Recommended next steps