Why Steam Pages Get Rejected

Common rejection reasons based on developer reports and Steamworks documentation — and how to fix each one.

Jump to Section

Content & Description Issues

Placeholder Text

Descriptions containing "coming soon", "TBD", "to be announced", or incomplete sections.

Fix: Replace all placeholder text with actual content. If features aren't finalized, describe what's confirmed.

Description Too Short

The "About This Game" section lacks sufficient detail about gameplay, features, or content.

Fix: Aim for 300+ words minimum. Describe what players actually do, list key features, mention content scope.

Misleading Description

Claims about features, content, or gameplay that don't match the actual build.

Fix: Only describe features that are implemented and working. Mark planned features clearly as "planned" or remove them.

Image & Video Problems

Non-Gameplay Screenshots

Screenshots showing concept art, pre-rendered cinematics, or marketing materials instead of actual gameplay.

Fix: Use only actual in-game screenshots. Concept art can go in the description, not the screenshot gallery.

Capsule Image Missing Title

The main capsule image doesn't include a readable game title or logo.

Fix: Ensure your game's name is clearly visible and legible on all capsule images.

Wrong Image Dimensions

Capsule images, screenshots, or headers don't match required dimensions.

Fix: Check capsule image requirements for exact dimensions.

Marketing Text in Screenshots

Screenshots containing awards, review quotes, or promotional copy.

Fix: Screenshots should show gameplay only. Marketing materials go elsewhere.

Early Access Disclosures

Missing Early Access Disclosures

Early Access games without answers to the five required disclosure questions.

Fix: Answer all five questions: Why EA? Current state? Timeline? Pricing changes? Community involvement? See Early Access requirements.

Vague Timeline

Early Access timeline says "when it's ready" instead of an estimate.

Fix: Provide a realistic estimate like "6-12 months" or "approximately 1 year."

Technical Requirements

Missing System Requirements

System requirements section incomplete or using placeholder values.

Fix: Fill in all five required fields: OS, Processor, Memory, Graphics, Storage. Use specific values.

Build Doesn't Match Store Page

Features listed on store page aren't implemented in the submitted build.

Fix: Only list features that work in your current build. Remove or clearly mark planned features.

Game Doesn't Launch

The submitted build crashes or fails to start on supported operating systems.

Fix: Test on clean machines for all supported OS versions before submission.

Links to Competing Storefronts

Store page contains links to Epic, GOG, itch.io, or other competing stores.

Fix: Remove all links to competing storefronts. Social media and Discord are generally fine.

Trademark Issues

Using other companies' trademarks inappropriately, or making unfair comparisons.

Fix: Use genre terms ("souls-like") instead of trademarked names. See legal guidelines.

Undisclosed Mature Content

Game contains violence, nudity, or other mature content not flagged in the content survey.

Fix: Complete the mature content questionnaire honestly. Under-reporting causes problems.

Broken External Links

Discord invite links expired, or website URLs not working.

Fix: Use permanent Discord invites. Test all links before submission.

Timing & Process Issues

Store Page Submitted Before Build

For adult content games, both store page and build must be submitted together.

Fix: For adult content, prepare both store page and playable build before submitting for review.

Insufficient Coming Soon Period

Trying to release without the required 2-week Coming Soon period.

Fix: Plan for at least 2 weeks in Coming Soon state before release. Use this time to build wishlists.

Catch Issues Before Submission

Don't wait for Valve's feedback. Check your page now.

Run Free Check →

What Happens After Rejection?

When Valve rejects your store page, you'll receive feedback explaining what needs to change. Common next steps:

  1. Read the feedback carefully — it usually points to specific issues
  2. Make the requested changes
  3. Re-submit for review
  4. Each re-submission goes back into the queue (typically 3-5 business days)

Multiple rejections can delay your launch significantly, which is why catching issues before submission matters.

Related Resources