If you’re trying to “publish a press release on The Verge,” the most important thing to know is this: The Verge is an editorial newsroom, not an open press-release publishing platform. You don’t upload a release and automatically appear on the site. Instead, you submit a news tip / pitch and provide your press release as supporting context.
The Verge explicitly tells readers how to reach them: email tips@theverge.com.
This guide shows you exactly how to submit to The Verge professionally—and improve your chances of being covered.
Where to submit to The Verge
1) Email (fastest and most common)
The Verge’s official “How to tip The Verge” guidance says you can send tips to:
tips@theverge.com
2) Web form (“Tip us” style submission)
The Verge also provides a submission form via their Contact page where you can summarize your tip in one sentence and add details.
3) If you need anonymity / safety
Their tip page includes safety guidance (e.g., avoiding work devices if you’re at risk) and outlines options for secure tipping.
Step 1: Check if your story fits The Verge
The Verge tends to respond best to stories that have:
- Clear consumer-tech or internet impact
- A strong “why this matters now” angle
- Specific, verifiable details (not hype)
Good fits often include:
- Major product launches with real public value
- Platform changes (policy/algorithm changes)
- Meaningful security/privacy events
- Notable creator economy / social platform developments
- Big moves by major tech companies
Not great fits:
- Generic corporate announcements
- Minor feature updates with no broader relevance
- Pure marketing language with no proof
Step 2: Pitch a story—don’t “submit a topic”
The Verge explicitly advises pitches should be stories, not broad topics. They even call out a common mistake: pitching a subject instead of a specific story with details.
Think:
✅ “We found X change affecting millions of users, here’s evidence and the timeline.”
❌ “We want to talk about AI trends.”
Step 3: Write a Verge-friendly email (copy/paste template)
Subject line examples (be specific):
Tip: [Company/App] changed [policy/feature] affecting [users]Launch: [Product] solves [problem] for [who] — here’s what’s newData: New report shows [finding] about [platform/industry]
Email body template:
Hello The Verge team,
One-sentence summary (required):
In one line: [What happened] and why it matters ([impact]).
Key details (3–6 bullets):
- Who: [company/product/people]
- What: [the change/launch/event]
- When: [date/time + timezone]
- Evidence: [screenshots, links, documents, demo access]
- Impact: [who is affected / how big]
- Context: [why this is significant now]
Assets / links:
- Press release (link or PDF)
- Press kit (logo, screenshots, photos)
- Spokesperson availability (name + time window)
Best regards,
[Name]
[Role / Company]
Email / Phone]
Send to: tips@theverge.com
Step 4: Include proof that makes the editor’s job easy
The Verge is more likely to engage when you provide verification-ready materials, such as:
- Product screenshots / release notes (clean and dated)
- Docs, policies, or official announcements
- Real numbers (users affected, rollout percentage, pricing)
- A short “what’s changed vs. before” comparison
- Demo access (if relevant)
Step 5: Use the Contact form when email isn’t ideal
If your team prefers a structured workflow, The Verge’s Contact page includes a form that asks for:
- A one-sentence summary
- A detailed explanation
- An option to request anonymity
This can be helpful when multiple stakeholders need to review the submission content.
Step 6: Follow up professionally (without spamming)
Recommended cadence:
- Send once
- Follow up once after 2–3 business days if time-sensitive
- Add new information in the follow-up (don’t just re-send)
Avoid:
- Daily pings
- Multiple people emailing the same tip repeatedly
Common mistakes that get ignored
- “Exciting announcement” subject lines (no news)
- Long pasted press releases with no quick summary
- No evidence, no links, no timeline
- Pitching a broad topic instead of a story (The Verge warns against this)