How to Get Your Game Approved on PixelPicked

Submitting a game to PixelPicked is straightforward, but your game page needs to contain enough accurate information and material for the team to review it properly.

PixelPicked reviews submitted games before they appear in the platform's discovery experience. The review is focused on the game and the information you provide: what the game is, where it is in development, what it looks like, and whether the submission meets the platform's requirements.

This guide explains what to prepare, what the review checks, what can lead to a rejection, and what to do if you need to resubmit.

How the review works

After you submit a game, PixelPicked reviews the information and materials attached to the submission.

The review can consider:

The game title
Description
Genre
Development stage
Platform target
Screenshots and other visual material
Trailer or gameplay footage, if provided
Developer or studio information
Other information included on the game page

The purpose of the review is to make sure there is enough clear, relevant information to publish the game appropriately on PixelPicked.

A playable build is not required simply to create a game presence on PixelPicked. Games can have a page while they are still in development, and developers can use that page to publish updates, build a community, and share progress.

If a submission does not meet the requirements, the developer can make the necessary changes and resubmit.

Submission requirements

Before submitting, make sure your game page contains the required information.

1. Game title

Provide the name of the game you are submitting.

Avoid using temporary placeholder text if you already have a public-facing title.

2. Short description

Provide a concise description explaining what the game is.

A useful description should make the core experience understandable without relying on generic phrases such as "fun," "exciting," or "immersive."

For example:

A one-thumb puzzle game where you rotate a collapsing city to guide stranded characters toward safety.

This gives players and reviewers something specific to understand.

3. Screenshots

Provide real visual material from the game.

Screenshots should represent the actual game rather than unrelated promotional artwork or generic mockups.

If the game is still early in development, early-stage visuals are acceptable as long as they accurately represent the project.

4. Development stage

Select the stage that best represents the current state of your project.

For example:

Concept
Prototype
Alpha
Beta
Near launch
Released

The development stage gives context to the material being reviewed. A prototype should not be evaluated as though it were a finished release.

5. Platform

Specify where the game is intended to be available:

iOS
Android
Both

If the game is currently targeting only one platform, select the appropriate platform rather than implying availability on both.

6. Genre

Choose the genre that most closely describes the game.

Genre classification helps players find games through discovery and rankings. Select the category that best represents the actual gameplay rather than choosing a category simply because it is popular.

What can cause a submission to be rejected

A rejection does not necessarily mean the game itself is permanently unsuitable for PixelPicked. It can mean that the current submission is incomplete, unclear, or does not meet the platform's requirements.

Common issues include:

Incomplete submission information

If important fields are missing or the provided information is insufficient to understand the game, the submission may need to be completed before it can be approved.

Examples include:

Missing game description
Missing development stage
Missing platform information
Missing required visual material
Placeholder information that does not explain the actual project

Misleading or inaccurate information

The information on a game page should accurately represent the game.

Avoid:

Misleading screenshots
Descriptions that do not match the actual game
Incorrect platform claims
Incorrect development-stage information
Promotional material presented as gameplay when it is not

Content that does not meet platform requirements

Submitted games and their associated pages must comply with PixelPicked's applicable content and platform requirements.

If something on the game page violates those requirements, it may need to be removed or changed before approval.

Insufficient material to evaluate the submission

A game can be early in development, but the submission still needs enough information for the review.

If the page contains very little information or visual material, the reviewer may not have enough context to understand what is being submitted.

In that situation, adding clearer descriptions, screenshots, gameplay footage, or development information can make the submission easier to evaluate.

Duplicate or substantially copied submissions

If you are submitting a game that substantially duplicates another submission or uses misleadingly similar presentation, you may be asked to clarify the relationship between the projects or revise the submission.

Games can be inspired by existing genres and mechanics. The important requirement is that the submission accurately represents the game being published.

Your genre does not determine approval

PixelPicked is intended to cover a broad range of mobile games.

That includes genres such as:

Puzzle
Strategy
RPG
Action
Adventure
Arcade
Simulation
Narrative
Casual
Platformer
Roguelike
Sports
And others

Choosing a familiar genre is not, by itself, a reason for rejection.

What matters is whether the submitted game and its page meet the platform's requirements and provide enough accurate information for players to understand what they are looking at.

A playable build is optional

You do not need to have a finished mobile game available for download before creating a presence on PixelPicked.

A game can be represented on the platform during development through:

A game page
Development updates
Visuals
Devlogs
Community discussion
Follows and engagement
An optional browser-playable demo

If you do have a playable demo, you can use it as another way for interested players to experience the game.

But a playable demo is not a prerequisite for having a game page or building an audience around a project that is still in development.

What can strengthen your submission

These materials are not substitutes for required information, but they can make the game easier to understand.

Gameplay footage

A short gameplay video can communicate mechanics and overall feel more effectively than screenshots alone.

It is particularly useful for games where movement, interaction, combat, or another mechanic is difficult to explain through still images.

Additional screenshots

More screenshots can help communicate different parts of the game, such as:

Core gameplay
Levels or environments
Characters
Menus
Progression systems
Different game modes

Only include screenshots that add useful information.

A detailed description

A longer description can provide context that does not fit into the short description.

You can explain:

The core gameplay loop
The game's premise
Major mechanics
What stage development is currently in
What you are working on next

Specific information is generally more useful than generic marketing language.

Development updates

If development is already underway, devlogs can show how the game is progressing.

You can document:

New mechanics
Art changes
Level development
Design decisions
Prototypes
Problems you are solving
Major milestones

This also gives players a reason to follow the game before release.

Studio or developer information

Include relevant developer or studio information so players can understand who is building the game.

A clear developer identity can also make the game page more useful as the project develops.

How to prepare before submitting

Use this checklist before you press submit:

Confirm the game title is correct
Write a clear short description
Add the required screenshots
Select the correct development stage
Select the correct target platform
Select the closest genre
Check that screenshots accurately represent the game
Remove placeholder or misleading information
Add gameplay footage if it helps explain the game
Add additional development information where useful
Check that developer or studio information is accurate

The goal is simple: a reviewer should be able to understand what you are submitting and what stage the project is in without having to guess.

What happens if your game is rejected?

If your submission is not approved, review the feedback provided with the rejection.

Look for the specific issue rather than treating the rejection as a judgment on the entire project.

For example, the problem may be:

Missing information
Incomplete visual material
An unclear description
Incorrect platform or genre information
Information that does not accurately represent the game
Content that needs to be changed to meet platform requirements

Once you understand the issue, make the necessary changes to the game page or submission materials.

How to resubmit

The resubmission process should be treated as a new review of the updated submission.

Step 1: Read the rejection feedback

Identify the specific requirement or issue that needs attention.

Do not assume that every part of the submission needs to change.

Step 2: Make the requested changes

Update the relevant part of the submission.

For example:

Add missing screenshots
Rewrite an unclear description
Correct platform information
Update the development stage
Remove inaccurate material
Add enough information to explain the project

Step 3: Review the entire page

Before resubmitting, check the rest of the page as well.

Make sure the updated information is consistent and that there are no remaining placeholders or inaccuracies.

Step 4: Resubmit

Submit the updated game for another review.

If the project has changed substantially since the previous submission, include the new information and material that reflects its current state.

Step 5: Continue development if necessary

A rejection does not prevent you from continuing to develop the game.

If the project is still early, you can improve the game and its presentation and submit again when there is more useful material to review.

A simple example of a strong submission

Imagine you are submitting an early-stage puzzle game.

Instead of:

Title: Puzzle Game
Description: An exciting and immersive puzzle experience.
Stage: Beta
Platform: Android
Genre: Puzzle

A clearer submission might say:

Title: Fold
Description: A minimalist puzzle game where players fold the environment itself to create paths between disconnected areas.
Stage: Prototype
Platform: Android
Genre: Puzzle

Then include several screenshots showing the actual prototype.

The second submission is easier to evaluate because the reviewer can immediately understand the game's basic concept, development stage, platform, and visual direction.

The same principle applies regardless of genre.

Quick reference

Required

Game title
Clear game description
Required screenshots
Development stage
Target platform
Genre
Accurate submission information

Helpful

Gameplay video
Additional screenshots
Detailed game description
Development updates
Developer or studio information
Optional playable demo

Before submitting

Check that all required information is complete
Make sure the visuals represent the actual game
Remove placeholders
Verify platform and genre information
Check descriptions for accuracy

If rejected

Read the feedback
Identify the specific issue
Update the relevant material
Review the complete page
Resubmit
Continue improving the project if additional development is needed

The goal of the review

The purpose of the submission review is to maintain a useful and understandable game discovery environment for players while giving developers a clear way to present their projects.

You do not need a finished game to start building a presence on PixelPicked.

You do need a submission that accurately explains what you are building, includes the required information and visuals, and follows the platform's requirements.

If your game is still in development, use that stage to your advantage. Publish progress, document decisions, build a community around the project, and improve the page as the game evolves.

And if your first submission is rejected, treat the feedback as a checklist for the next version rather than the end of the process.