Game requirements

This page describes the requirements for games and WebApps published in the Yandex Games catalog.

Games and WebApps are tested in environments similar to what users have. If we find an issue but it doesn't occur on the developer's device, the issue isn't considered resolved.

Note

The game passing moderation doesn't mean Yandex confirms that it complies with the law of any territory and/or that it doesn't violate the rights or legitimate interests of third parties.

Last updated: August 28, 2024.

Technical requirements
1. The Yandex Games SDK is installed in the game or WebApp. See more by going to Install and use the SDK.
2. You don't have to be registered or logged in to third-party services to launch and use the SDK. You can log in with your Yandex ID. Learn more
  1. You'll only be authorized after you perform a voluntary action like pressing a special button in the game or WebApp. The authorization prompt clearly and unambiguously explains the reason for authorization. Learn more
  2. The game has the guest login option or you can play it without logging in. If that's the case, in-game progress must be saved.
3. When you minimize the game or WebApp page on desktop and mobile devices, the sound stops playing.
4. Payments are only made through the Yandex Games SDK.
5. Ads are only called via the Yandex Games SDK.
6. The game or WebApp must meet the requirements for the device types you listed when applying for publication.
  1. For mobile devices:
    1. The game or WebApp is in full-screen mode during launch or gameplay.
    2. If the user can enter data like their player nickname or a document name in text boxes, the keyboard automatically appears when they select them.
    3. Visual elements aren't deformed or stretched disproportionally when the screen orientation and/or available area size are changed. If the game or WebApp only supports one orientation, select it when you're filling out the draft. In the other orientation, the user will be shown a prompt to rotate their device.
    4. The game or WebApp progress is saved when the screen orientation changes.
    5. The game or WebApp is entirely gesture-controlled. You can add the mobile device accelerometer to the control mechanics.
    6. The system player triggered by the game or WebApp doesn't appear in any browser.
    7. There's no WebGL notification when the user opens the game or WebApp.
    8. Long tap on an inner game field or WebApp does not lead to field selection or context menu opening.
  2. For desktop devices:
    1. The active area stretches vertically or horizontally to fit the available space (not counting sticky banners).
    2. The long-to-short side ratio of the active area should not exceed 1:2.
    3. Visual elements aren't deformed or stretched disproportionally when the available area size is changed.
    4. The game or WebApp is controlled using a keyboard or mouse.
  3. For TVs:
    1. The game or WebApp takes up the entire screen area. Full-screen mode is available.
    2. Arrows on the TV remote can be used to control the game. Arrows on the TV remote are enough to play the game or use the WebApp in its entirety.
    3. The Back and OK buttons on the TV remote are supported.
7. In the interests of the game or WebApp working correctly anywhere in the world, the program code doesn't use absolute URLs that link to the Yandex S3 servers.
8. The internal element, button, and graphics sizes are adapted for display and interaction in a way that avoids the possibility of accidentally pressing something and makes all elements easily accessible.
9. In games with internal progress (like new levels, records, achievements, and skills) and WebApps that involve saving data (such as notebooks or phone books), changes are saved right after the user performs an action or when they press the save button. Refreshing the page shouldn't affect the saved data. Learn more
10. The game or WebApp displays correctly, including when the window size is changed:
  1. The active area doesn't go beyond the screen area. No elements are cut off.
  2. The browser's page scroll (system scrollbar of the browser window) or swipe to refresh is missing. However, it's acceptable to implement custom content scrolling using game mechanics.
  3. Internal elements and texts don't overlap or cover other elements.
  4. It's possible to control the game with one hand and stay in the main scene without additional scrolling or swiping. The internal playing area may be moved in strategy games, RPGs, and other genres that feature a large playing area.
11. If you save data to a cloud, list it when you're filling out the draft.
12. Yandex Advertising Network (YAN) monetization is enabled.
13. For in-game purchases:
  1. The consummation method is enabled. For more information, see In-game purchases.
  2. The portal currency is used in keeping with the requirements in the In-game purchases section.
  3. The game or WebApp progress is saved on the server and available on different devices.
  4. All in-game purchases have a cost that's shown as a figure and portal currency name.
14. There are no technical notifications, errors, crashes, or freezes after the user opens the game or WebApp or completes a particular action. For example, rotating the screen, long-tapping in the game or WebApp, completing a gesture or swipe, minimizing the browser, opening an ad, or going to a page from the browser history.
15. The game or WebApp are complete and not in the development or preliminary testing stage.
16. The content and appearance of embedded ad units aren't changed. Service ad units can't be imitated, for example, by creating custom full-screen units or RVs with your own buttons.
17. (No longer applicable)
18. There are no technical ways of restricting gameplay based on the URL where the game is open.
19. Initializing the Yandex Games SDK and using its methods must be done in strict accordance with the documentation and game requirements:
  1. The SDK must be initialized exactly as described on the Installation and Use of SDK page.
  2. At the moment when the user can start playing the game, the ready() method from gameReadyAPI must be called.
  3. Using GameplayAPI is optional, however, if GameplayAPI methods are used in the game, then the moments of sending the start() and stop() events strictly correspond to those described in the Gameplay section.
20. The game or WebApp works correctly in browsers and on platforms with the environment selected in the draft. List of browsers and platforms:
  1. In browsers: Yandex Browser, Google Chrome, Mozilla Firefox, Opera, Safari, and the Yandex mobile app.
  2. In OS: Windows Vista, Windows 7, Windows 8, Windows 10, and Mac OS X 10.6 and above (Snow Leopard, Lion, Mountain Lion, Mavericks, Yosemite, El Capitan, Sierra, High Sierra, and Mojave).
  3. In mobile OS: Android 5.0 and above and iOS 9.0 and above.
  4. On Android TV.
21. No game or WebApp files are more than 100 MB when uploaded as an archive.
22. An index.html file is added to the root of the archive. Cyrillic characters and spaces are not used in file or folder names.
23. Interactive artificial intelligence cannot be used in games or WebApps. Materials that were generated beforehand using AI can be used in the game.
UX requirements
1. The game or WebApp is well-designed in terms of gameplay content, convenience, and quality. We control the quality of games and WebApps and may refuse to publish them if they don't pass our quality check.
2. The controls are fully described in the game, the WebApp, or their accompanying descriptions.
3. The game or WebApp matches the genre you listed in the description.
4. The game matches one of the following criteria:
  1. There's game progress (levels).
  2. There are interaction and game engagement mechanics (controlling a machine or character, changing a character's outfit, assembling objects using parts or recipes, dealing or turning over cards, word games, number games, and/or acquiring game resources).
  3. There's a story (gradual unfolding game events, selecting actions, and achieving story results).
5. (No longer applicable, see item 6)
6. If the game mechanics involve gradually moving through a story or levels, game progress can be saved. If the game is endless or there's a competition for the highest score, records can be saved.
7. The age tag matches the game content.
8. The game difficulty increases gradually. The story/setting are clear.
9. Playing through the entire game takes more than 10 minutes. For example, a casual game with 10-20 levels, a quiz game with multiple topics and 15-20 questions for each topic, or a puzzle game with multiple tasks. For the gameplay to take at least 10 minutes, quizzes and tests must have at least 100 questions. The questions can't be repetitive or extremely similar (different answer options or different wordings of the same question). Learn more
10. The game or WebApp is localized into at least one language selected in the draft. The recommended minimum for publication is localization into Russian for RU, BE, KK, UK, and UZ, and English for all other languages.
11. (No longer applicable, see item 1.8)
12. The WebApp offers practical value for users.
13. The game or WebApp is popular among users: the number of unique players or users over the past 100 days is at least 100, and the total play or use time in the past 100 days is at least 1000 minutes.
14. It's easy for players to choose a language even if one they don't know is enabled.
  1. When the language is automatically detected, it must match the i18n.lang parameter from the SDK environment variables.
  2. If the game only offers manual language selection (without automatic detection), players can choose their preferred language without knowing the game's current language.
    1. Languages are denoted by icons with corresponding country flags or the language name in that language (such as Русский, Беларуская, English, and Español).
    2. All menus and settings that lead to language selection are clear without text and represented by standard icons (such as a gear for settings and a globe for localization).
Content requirements
1. (No longer applicable, see item 8)
2. (No longer applicable, see item 8)
3. (No longer applicable, see item 8)
4. The game or WebApp doesn't contain:
  1. (No longer applicable, see item 8)
  2. Materials about magic or divination.
  3. Realistic depictions of violence and/or cruel treatment of children or animals.
  4. Images of references to politics, political situations, political figures, intrastate or interstate conflicts, or wars.
  5. Images or references to religion, religious figures, or religious symbols.
  6. Conclusions or predictions regarding a player's life and health, including predicting diseases, as well as predicting the date, time, or circumstances of death.
5. The creator owns the copyright to all materials. If needed, you can include the developer's "Privacy Policy" and "License Agreement" in text form within the game. All materials are sent for moderation by the creator or another authorized person.
6. The game or WebApp isn't partially or entirely a copy of another game or WebApp in the catalog or another game or WebApp by the same developer. If the game is a sequel or part of another game, it's only accepted as a separate game if the game graphics and mechanics are completely changed. Otherwise, update the previous game by adding the new content. The WebApp can't be divided into multiple separate entities that are used simultaneously or sequentially to perform the user's task. Learn more
7. There are no operations with non-game valuables or real money:
  1. The user can't win or withdraw real money or prizes that aren't in-game valuables, including physical objects, subscriptions, non-game content, or a monetary equivalent of a prize.
  2. The game or WebApp aren't an online store, gambling game, or online lottery.
  3. There are no microtransactions or external purchases of any kind. Only internal purchases via the Yandex Games SDK are allowed.
8. The portal currency is determined automatically, SDK methods are used for its designation. For more details, see the Portal Currency Designation section.
9. Video clips can only be integrated into the game or WebApp such that they don't allow visiting external resources to use the interface. Video integration via the YouTube player doesn't meet that condition. Because of that, games or WebApps featuring integration with YouTube aren't accepted. If you need to integrate videos, we recommend using your own hosting or embedding the video in an archive.
Ad requirements
1. There are no ads from third-party advertisers, including static ad images and text.
2. If a user clicks an ad and returns to the game afterwards, their progress is saved.
3. The orientation of all ad units matches the game or WebApp orientation.
4. Ads don't get in the way of the user interacting with the game or WebApp:
  1. Ads are displayed during logical breaks. Learn more
  2. When the user wants to press an element or get information from it, interacting with the element doesn't call an ad unit.
5. If you use rewarded ad mechanics, the user can watch a rewarded video if they want to (for example, by pressing a special button) and receive a reward in a game or WebApp.
  1. The button to watch a rewarded ad must be linked to a text or another button that clearly indicate:
    - The user is about to watch an ad in exchange for a reward.
    - The specific reward the user will receive.
  2. The reward for watching an RV ad is an extra bonus (for example, boosters, extra moves, level skips, bonus levels, and others) that enhances the core game experience and doesn't affect the player's ability to continue playing.
6. Additional ad unit placement rules:
  1. Additional ad units can only be sticky banners.
  2. Custom RTB banners are prohibited.
7. During fullscreen ads (interstitial or rewarded videos), the game sound and gameplay must be paused.
Description and promotional material requirements
1. Promotional materials must meet the following requirements:
  1. The elements and materials used are from the game or WebApp or directly related to it. Foreign elements and images can't be used.
  2. The materials show what the game or WebApp is about, demonstrating its features, advantages, and uniqueness to attract users.
  3. The game/WebApp name, for each language selected in the draft, must be identical across the game/WebApp and all draft materials, including text fields and all promotional materials.
2. All required application fields are filled out: Title, Description, How to play, Version, Categories, Icon, Cover, Sources, Supported platforms, and Orientation. Screenshots are added in keeping with the instructions.
3. Text field data and promotional files follow the standards for content, length, size, format, and duration specified in the draft according to the requirements for each field. The current standards are specified in the draft form.
4. The tags and keywords match the topic and content.
5. (No longer applicable, see item 8)
6. Screenshots from the game can't be used as icons/covers.
7. (No longer applicable, see item 8)
8. (No longer applicable, see item 8)
9. On all media materials (video, icon, cover, screenshots, gifs) a black background (on the sides or top and bottom) may be displayed if it is part of the game or WebApp, and not a fill when scaling.
10. (No longer applicable, see item 8)
11. Repeating symbols like spaces and hyphens can't be used to reach the minimum threshold for the draft's text fields. Duplicate texts in different draft fields can't be used either.
12. The game name in the catalog is unique for all languages selected in the draft.
Recommended requirements
1. The developer's or publisher's email address is provided.
2. The sound can be turned off.
3. Gameplay can be paused.
4. The Games Console opens without errors.
5. The game/WebApp name doesn't contain the words "game" or "WebApp" unless they're an integral part of the name.
6. The name is short.
7. There are no buttons or controls that aren't used to interact with the game or WebApp on the specified platforms. For example, a game exit button in the main menu.
8. For games or WebApps with complex mechanics, we recommend adding a tutorial upon launch.
Additional WebApp requirements
1. The WebApp doesn't violate the rights or interests of third parties:
  1. The WebApp is not being passed off as an official product of another app or brand.
  2. The WebApp doesn't use brands unrelated to the developer to attract an audience.
2. If the WebApp works with user data, it explicitly asks the user's consent to process their data.
3. The WebApp doesn't contain any information that:
  1. Could lead to violations of law by misleading users or abusing their trust.
  2. Promotes criminal activity or provides advice, instructions, or manuals for committing crimes.
  3. Helps users break the law or encourages them to doing so.
  4. Features realistic images of violence against people or animals; erotic or, pornographic content; images of items imitating sexual organs and/or references to sexual intercourse; content that offends a person or a group of people based on sex, nationality, or religion; or obscene language and swearing.
  5. Describes ways or methods of committing suicide or in any way encourages users to commit it.
  6. Promotes or incites racial, religious, or ethnic hatred or discord.
  7. Promotes fascism or an ideology of white supremacy.
  8. Contains extremist materials, violates other rights and interests of individuals and legal entities, or violates the laws of the Russian Federation or other countries.
4. If the WebApp has the option of creating or uploading user content, it also has terms and conditions of use that are available and easy to find:
  1. Before creating content and uploading materials to the WebApp, the user must explicitly agree to its terms and conditions.
  2. If other WebApp users can view materials uploaded by the user, the WebApp must have a way to report inappropriate content.
5. The WebApp isn't a placeholder without functionality and doesn't open an external resource in its window.
6. (No longer applicable, see item 8.4.4)
7. The WebApp doesn't restrict its functionality if the user doesn't agree to complete additional actions like subscribing to emails, allowing notifications, sharing on social media, downloading files, registering, or following external links. The WebApp can unblock some functionality after users watch RVs or make an in-app purchase with the portal currency in accordance with item 4.5.2 of the requirements.
8. (No longer applicable, see item 3.6)
9. (No longer applicable)
10. (No longer applicable, see item 6)
11. (No longer applicable)
12. (No longer applicable)
13. The WebApp fits one of the following categories:
  1. Business:
    1. Business calculators.
    2. Currency converters.
    3. Report and standard document generators.
  2. Health and fitness:
    1. Health, body parameter, and workout tracker apps.
    2. Fitness programs and trackers.
    3. Stress relief and meditation.
  3. Tools:
    1. Household tools like stop watches, timers, distance and angle meters, compasses, and internet profilers.
    2. Graphics, design, and drawing apps.
    3. Apps that display time, time zones, and locations.
    4. Note-making and to-do list apps.
    5. Genealogy.
  4. Reading:
    1. Reference books.
    2. Translators.
    3. Graphic novels.
    4. Horoscopes (no purchases).
    5. Funny stories.
    6. Congratulations, aphorisms, quotes, proverbs, sayings, facts.
  5. Education:
    1. Education and training apps.
    2. Memory, attention, and skill improvement apps.
    3. Playful learning apps.
    4. Learning languages and traffic rules.
    5. Pre-school, school, and vocational education.
    6. Raising children.
  6. Traveling and guidebooks.
  7. Dating apps except social media and messengers.
  8. Entertainment:
    1. Sound, object, and situation simulators.
    2. Karaoke.
  9. Lifestyle:
    1. Beauty.
    2. Pets.
Text and media content requirements
1. The following rules apply to text and media content (images, videos, and game objects) for all Yandex Games objects, including game descriptions, promotions, purchases, and games. If the game/WebApp doesn't meet the requirements, it may not be published or may later be removed from publication.
2. Text requirements:
  1. The text follows the grammar and punctuation rules of the selected language.
  2. The text's meaning matches the selected object (game or promotion name, description, how to play).
  3. The language-specific fields are translated into the necessary language(s). Non-English languages should not use English words, including but not limited to start, exit, stop, online, offline, off, on, go, Cam, Rec, hp, and mph. Exceptions:
    1. The game name in English in any localized version of the game. The game name doesn't have to be in English for all localization languages and may also be translated.
    2. Acronyms and abbreviations. For example, including but not limited to: ad, ads, adv, VIP, VS, all forms of OK, and v for version. Full versions of acronyms and abbreviations should be translated (for example, the word "version").
    3. International currency denominations like USD and RUB.
    4. Descriptions of some control elements like Ctrl, Alt, Shift, W, A, S, and D. The Space key is an exception and should be translated into the appropriate language.
    5. Proper names and trademarks that have no official translation in the target language.
    6. All texts that the user does not interact with during the game, including, but not limited to: logos, slogans, names of game engines (for example, powered by Unity), background images (a shop sign on the game background, inscriptions on buildings, etc.).
  4. The text contains no profanity in any language.
  5. The text doesn't contain prohibited materials.
3. Media content requirements:
  1. Good quality, no visual artifacts (pixel compression artifacts, excessive shadows, monochrome frames, truncated text in icons/covers).
  2. The media reflects what the object is about (icon, color, ad clip, or purchase). It's not a random image or video.
  3. The content has no borders or rounded corners.
  4. There are no system interface elements like status bars, charge indicators, and others. Game elements (such as a health bar, timer or others) are allowed.
  5. There is no pornographic or erotic content, no images of items imitating sexual organs and/or references to sexual intercourse, and no materials that offend an individual or a group of people based on sex, nationality, or religion. Learn more
  6. The content is safe, ethical, appropriate for users of all ages, and complies with the service rules. Otherwise, Yandex Games reserves the right to refuse to feature the game on the main page, in thematic sections, collections, or other platform materials, or to prohibit its publication on the platform. Learn more
  7. There are no other prohibited materials.
4. Links in texts and media content:
  1. Links to the developer's other games or WebApps (More Games and similar sections) only published in the Yandex Games catalog. The pages must open in the same domain as the game or WebApp the user has open.
  2. Links that don't lead to any external resources, such as the creator/game/WebApp's site, stores, studios, external games or WebApps, partner sites, file downloads, or malicious pages. Links cannot be part of logos or other graphic elements. Permitted exception: the partner company's or creator's graphic brand without the domain or other URL elements. For example, the name for "CompanyName.Com" can be displayed as "CompanyName".
  3. Links to social media groups are allowed if:
    1. The group is dedicated to one or more games or WebApps published by this developer in the Yandex Games catalog.
    2. The group name mentions Yandex Games.
    3. The group doesn't publish links to external resources or any other materials unrelated to the game or WebApp.
  4. Redirecting users to external sites is prohibited, whether through automatic redirection (triggered by user action or inaction) or by suggesting they visit external resources (for example, "search online" or "view full version").

Game requirements

Was the article helpful?