Requested page is not yet translated to the selected language (polski). Showing English version.
This article sets rules and guidelines that beatmaps must follow in order to progress through the ranking procedure.
Rules must not be broken under any circumstance.
Guidelines may be ignored and broken under exceptional circumstances. When doing so, a sufficient explanation should be provided by the mapper either upfront or when prompted during the modding process.
Changes to any part of the ranking criteria are proposed through the Ranking Criteria forum.
Create a proposal in the Ranking Criteria forum. Try to be as detailed as possible while explaining your idea and the change's impact.
Come to a consensus. If you think you are at that point, reach out to a member of the
NAT to see if your proposal can be implemented. To an extent, the NAT can act as the arbiter in contentious cases, but proposals without a general consensus will likely not pass.
Create a pull request on the osu!wiki GitHub repository. Usually, this is done by a member of the NAT involved in finalising the discussion.
Wait on approval from peppy.
Changes that do not alter the meaning or intention of the ranking criteria, such as improvements to spelling, grammar, or organisation, may not need a forum proposal. It is still recommended to check with experienced community members that the changes are helpful and welcome.
Parts of the Ranking Criteria have their own articles while still applying to all beatmaps regardless of game mode, length, or any other restrictions.
Simplified ranking criteria: This article summarizes the big picture of the ranking criteria articles, because this set of articles is complicated. Please note that this article is not exhaustive and the corresponding ranking criteria articles should be used when in doubt.
Metadata: Rules and guidelines on crediting the beatmap.
In addition, each game mode has specific ranking criteria that specifically apply to just beatmaps of that gamemode.
It is highly recommended that you use Mapset Verifier (MV) to aid in checking these criteria. AiMod from the old client (stable) is outdated and unmaintained, and beatmap verification in osu!(lazer) is work in progress.
Important to understand before using:
No tool entirely replaces the necessity to read this page or check manually.
Be critical about what they point out and do not follow them blindly.
They exist to help you, not replace you.
No two hit objects can be placed on the same tick. This includes hit circles and the durations of sliders and spinners. osu!mania difficulties are exempt from this.
There must be at least 10 milliseconds between a hit circle and the next object, and at least 20 milliseconds between the end of a slider and the next object. osu!mania and osu!catch difficulties are exempt from this.
All beatmap content must be cleared regarding content usage permissions. For artists or tracks which are listed as disallowed on the page, their songs may only be ranked if explicit permission for the track is given to the beatmap host. Proof of permission must be presented in the beatmap description or the discussion page.
There must not be any obscene imagery in the background/storyboard/video content. This includes nudity, near-nudity, sexual references, violence, drug abuse, etc. See
Visual Content Considerations for more detailed rules.
Difficulties that contain repetitive strobes, pulsing images, or rapid changes in contrast, brightness or colour in the storyboard or video must use an epilepsy warning. If the warning interferes with gameplay, audio lead-in must be made longer. Strobing effects at 3 Hz (i.e. 3 flashes per second) and below are unlikely to cause concern. When in doubt, add the warning and confirm its necessity during the modding process.
There must not be any unused files or 0-byte files in the beatmap's folder. 0-byte files prevent other files in a beatmap's folder from properly uploading. Automatically generated thumbs.db files are the only exceptions.
The Letterbox during breaks setting must be consistent between difficulties of the same mode if they contain break periods and if included, the same storyboard.
Beatmaps containing spoilers for other media must be marked with a spoiler warning in the beatmap's description.
Creators of the media used in a beatmap should be credited in the beatmap's description. Per the
Content Usage Guidelines, media used in beatmaps should be permitted for use in osu!, and their licensing will likely detail how to credit their creators. Common reasons to omit credits from the description include exceeding difficulty in sourcing, creators' wishes to remain uncredited, and presence of credits in the artist, title, or source fields.
Directly re-using your own Ranked difficulties in other Ranked beatmaps is discouraged. This is to avoid unnecessary bloating of Ranked content.
Slider tick rate should not be modified through the .osu file. Most custom values result in unsnapped slider ticks, however tick rates 0.5, 1.333, and 1.5 have practical use and can be applied only when they do not cause slider ticks to be unsnapped.
Kiai should start on a sound in the music. Doing so otherwise causes the kiai flash to feel unrelated to the song.
The Enable countdown setting should be consistent between difficulties of the same mode. If a difficulty does not have a long enough intro period for the countdown to occur, this setting does not need to be consistent.
Note: Each osu!mania key mode and playstyle is considered to be a separate game mode throughout this section.
All game modes within a beatmap must form a spread starting from the lowest difficulty level dictated by the song's drain time. For difficulties above the lowest required difficulty level, the spread cannot skip any difficulty levels and there cannot be any drastically large difficulty gaps between any two difficulties.
Each difficulty must comply with its mode's difficulty-specific ranking criteria. See the
osu!,
osu!taiko,
osu!catch, and
osu!mania ranking criteria for more information.
Every difficulty of a beatmap must have a minimum drain time of 30 seconds.
A beatmap of 2 songs combined together must follow the minimum spread requirements corresponding to the length of the longer song. This is to avoid artificial extension of songs as an evasion of the above time limitations. Exceptions can be made for songs that were exclusively released together.
Difficulty names in a beatmap must be clearly progressive and accurately indicating of their respective difficulties, excluding:
The highest difficulty of each game mode.
The highest difficulties of each game mode with a similar level of difficulty, applying only to Insane and Extra difficulties (e.g. the Insane difficulties of a ENHIIII set or the Extra difficulties of a ENHIIXXX set).
A beatmap's custom difficulty naming must follow a common theme or pattern related to the song or difficulty and must not be misrepresentative. A difficulty name is misrepresentative if it implies a different difficulty level (e.g. naming an "Expert" difficulty as "Normal").
A difficulty's name must not solely consist of one or more usernames. Words that happen to be usernames are acceptable within difficulty names as long as they relate to the song.
A beatmap host cannot indicate possession in a difficulty's name. (e.g. Beatmap Host's Insane). Conflicts caused by beatmapping multiple songs with the same metadata and
collaborative difficulties are the only exceptions.
Guest difficulties, however, may indicate possession with its creators' username or nickname.
A beatmap host must have beatmapped equal or more difficulties than any guest difficulty creator. This is to provide credit where credit is due.
Collaborative difficulties are only considered partial difficulties, and
drain time will be used to determine the amount of contribution when a guest has beatmapped significantly more than the host.
A beatmap host and guest difficulty creators can make changes to their respective difficulties as they wish. If there is a disagreement between both, the beatmap host must delete the guest contribution upon request. If a guest difficulty creator cannot be contacted for a month, they will be assumed to agree with any changes.
Beatmaps cannot contain significant portions of difficulties belonging to other users without their explicit involvement or permission.
Uninherited timing points must be used to accurately beatmap the song's time signatures. If an incorrect time signature lasts for more than one bar, an uninherited timing point must be added on the next downbeat to reset the time signature. For #/4-signatures unsupported by the editor, metronome resets or editing of the
.osu file are acceptable. For other unsupported time signatures, refer to this
exemplary chart, and see the
Timing songs with #/8-signatures guide for further information.
Beatmaps must be perfectly timed. This means
BPM and offset of each
uninherited timing point are exactly synchronised with the song. Beatmaps with constantly changing BPM may be impossible to perfectly time and should instead be as accurate as possible without negatively affecting gameplay. Complex timing during breaks or spinners is optional.
Uninherited timing points must be the same in every difficulty of a beatmap. Each point must have the same
BPM and offset in each difficulty.
Uninherited timing points should only be used when required for timing purposes. Unnecessary timing points may unintentionally affect main-menu pulsing, add unwanted sounds to the
Nightcore mod, or cause timing to shift. Acceptable uses include:
No two uninherited or two inherited timing points can be placed at the same point. Having two uninherited or two inherited timing points on top of each other will cause unintended behaviour for slider velocity and volume settings.
An inherited timing point cannot be placed before the first uninherited timing point. Without having any settings to inherit, an inherited timing point does not function properly. If you wish to alter hitsounds or slider velocities before the first uninherited timing point, it must be moved back one full measure so that inherited timing points may be used.
A beatmap's first uninherited timing point cannot be used to toggle kiai. Doing this will cause the kiai to flash before objects appear. An
inherited point in the same position as the first uninherited point must be used to toggle kiai instead.
Hit objects must be snapped within less than 2 ms of any timeline tick. AiMod will report these issues, as well as rare false positives. False positives mainly occur on slider ends and reverses, and should be verified manually or with other tools. Objects in a musical section requiring unsupported beat snap divisors (e.g. 1/11) can either:
An object which is wrongly snapped due to passing through or ending slightly before a new uninherited timing point must have its tail snapped within the new timing section. For spinners and osu!mania long notes, this can be achieved through dragging the end of the object in the timeline. For sliders, this can be achieved through slider velocity manipulation or editing of the
.osu file.
The audio file of a beatmap must...
...use the .mp3 or .ogg file format.
...have an average bit rate no greater than 192 kbps for .mp3 files, or 208 kbps for .ogg files.
...have an average bit rate no lower than 128 kbps, if such a source exists. Otherwise, use the highest quality available.
...not be encoded upwards from a lower bitrate.
A beatmap may only contain one song file used by all difficulties. Multiple song files within a single beatmap are unsupported and result in unexpected behaviour with preview times, metadata, etc.
Beatmaps must be hitsounded. Hitnormals give feedback to the player, and additions (whistles, claps, and finishes) accent the most important parts of the music.
All clicked parts of objects must have at least one hitsound which both...
...has a clear impact, whose peak is delayed no more than 5 milliseconds. normal-hitfinish.wav from the default skin is exempt from this.
...uses the .wav or .ogg file format. .mp3 should not be used here as it is inherently delayed.
This ensures instant audible feedback when clicking objects, synchronising with the song in a way that enables players to determine how early or late they are clicking. osu!mania is exempt from this due to its concurrent objects.
Hitsounds must be audible. Their purpose is to provide feedback, so hitsounds with extremely low volume or samples that blend with a song's samples are unacceptable. Specific game modes list exceptions to this rule on their respective ranking criteria.
Preview points must be set and consistent between all difficulties of a beatmap. This is used for both the song selection menu and the online thumbnail preview.
Every hitsound file must be at least 25ms long. Shorter files can result in no sound being played in-game.
Completely silent sound files must use this 44-byte file. Other files have unnecessarily large file sizes, and 0-byte files do not function.
Storyboarded hitsounds cannot be used as replacements for active hitsounds. These give an inaccurate form of player feedback. Storyboarded hitsounds in other situations are acceptable, but discouraged. osu!mania is exempt from this rule.
The audio file and hitsound files of a beatmap should not feature any audible and unwarranted sound distortions, like clipping, muffling, or crackling that is clearly not intended by the artist or part of the song's identity. This is best determined by listening to the audio, rather than using software on its own.
The audio file of a song should not be artificially extended in order to meet a time limitation in the beatmap section of this criteria. This can include (but is not limited to) looping sections of the audio file, lowering the
BPM of the song or section of the song, or adding small amounts of music to the song without incorporating it throughout the entire song. This does not apply to
song compilations or audio files less than the minimum rankable beatmap length.
If you do not beatmap the last 20% of your beatmap's audio file, it should be cut. The intro time is not included. This does not apply if more than 20% of the outro is occupied by a storyboard/video, or if more than 20% of the song's audio is not able to be mapped due to fade-out or timing issues.
Song compilations or other medley-style tracks should aim to be cleanly mixed with proper transitions, and should not include abrupt breaks or long fades between different songs. The songs used for the compilation should be similar in audio quality, volume and length. This is to ensure compilations achieve the same cohesive gameplay experience as other beatmaps. Cross-faded transitions are acceptable, but should be used sparingly and generally be no longer than 5 seconds. Beat-matched and well-planned transitions are always a better option than cross-fading.
Combinations of 2 songs should be clearly and closely related. Examples of this include, but are not limited to, being iterations of the same series of songs, related in lyrics or motifs, similar in tone and/or genre, etc.
Cut songs should maintain the general impression and intensity of the full song. Cuts that change the structure of the full song (such as excluding or rearranging a song's intro/verse/chorus/outro) can lead to misrepresentation of it and often cause unsatisfying playing experiences. This does not apply to official cuts or recreations of official cuts.
Gameplay sounds excluding active hitsounds should use the .mp3 or .ogg file formats. These files usually have long durations and
.wav files are unnecessarily large in comparison, however
.wav should be used when it results in a smaller file size.
Avoid replacing the hit finish in soft/normal samplesets with frequently used custom hitsound samples. Using these finishes to represent snare/bass drums or a song's melody can sound obnoxious for anyone disabling beatmap hitsounds. Replacing hit whistles/claps is recommended because those samples are used more often. osu!taiko beatmaps are exempt from this guideline and have their own mode-specific hitsound sample guideline.
Video and background
You must have a background image on every difficulty of your beatmap. Different background files for different difficulties is acceptable.
The following are requirements for background images:
Minimum width: 160px
Minimum height: 120px
Maximum width: 2560px
Maximum height: 1440px
Maximum file size: 2.5MB
A video's dimensions must not exceed a width of 1280 and a height of 720 pixels. Additionally, upscaling lower resolution video to a higher resolution should be avoided. This ensures video files do not become excessively large or resource intensive.
A video must be encoded in H.264.
A video's offset must be correct if it synchronizes with the song. An incorrect offset can result in a misleading visual representation of the song. If the same video appears in multiple difficulties, it must always have the same offset(s).
A video's audio track must be removed from the video file. The audio track in a video is not used in osu!, and removing it reduces the file size of the beatmap. This includes videos with muted audio tracks.
If you are using any elements created by another community member, ask permission beforehand. Respecting the work of others is paramount and most people will be delighted to have their work featured in your projects! Thus, if you do not know who made the elements you plan on using, you must not use them.
Gameplay elements must be visible. You cannot make any element that will impair the playability of the beatmap invisible as it will make the beatmap unintuitive or even impossible to play (
cursormiddle.png is an exception as it affects the behaviour of cursor trail). Elements that are not relevant for gameplay may only be transparent if there is a valid reason for this and the action itself does not impair the usage of interface elements negatively.
Skinned elements must be cropped cleanly so they do not have pixelated artifacts around them or half-cropped shadows.
Skinned elements cannot exceed dimensions to the point where they overlap other skin elements which they would not normally overlap in the default skin. This applies only to the visible parts of an image, which could distort the gameplay experience by visually obstructing normally visible elements.
When skinning gameplay elements, complete sets of elements need to be skinned in order to avoid conflicts between user-specific and beatmap-specific skins. When skinning an element that is marked as optional, you need to include all the required elements of the respective set, but you are free to skip other optional elements unless they are grouped with the element you are skinning. However, if a required skin element in a set would be unused or the default skin is forced, the element is not necessary to include.
Storyboard image: This refers to the image in the song folder that the storyboard uses.
Sprite: An object in a storyboard representing an image, or a series of images.
Time: A millisecond representation of a timeline position. This representation is seen within the design section of the editor.
Command: These affect a sprite in various ways. Some examples of commands are Move, Scale, Fade and Rotate. Each of these have a starttime and endtime.
Axis-specific command: A command which only applies to one specified spatial axis, for example MoveX and MoveY.
Active: From the first start time to the last end time of commands in the object.
Rendered: Often referring to an on-screen sprite that is not completely faded out.
osu!pixel: The smallest dimension of the design tab. Seen in the top right corner of the editor screen, e.g. x: 104; y: 88.
Storyboarded images must not exceed an area of 17,000,000 pixels to keep loading times of large images within reasonable ranges for most computers to handle. Additionally you may need to rescale your images accordingly to the internal maximum dimensions of the storyboard editor of 854 x 480 osu!pixels when using them.
The difficulty must not throw parsing errors upon loading. This means the parser cannot read part of the storyboard instructions.
The Widescreen support setting must be consistent between storyboarded difficulties in a beatmap, unless difficulty-specific storyboards are designed for different aspect ratios.
There should be no active sprites and commands after the end of the song. This is flexible up to a few extra seconds depending on the storyboard effect, but more than that should not be necessary.
Consider leaving a one pixel border of transparency around storyboard images of rotated sprites for interpolation to work properly. osu! does not utilise anti-aliasing around images, and as such this becomes very noticeable if the edges are visible and the sprite is rotated.
Avoid any noticeable performance issues as much as possible. Even being optimised, having consistent frame rates is crucial for the playing experience of the difficulty. Test play the difficulty during the modding process to confirm this.
Refrain from usage of storyboard sound samples in ways that are easily confused with hitsounds during gameplay. This goes against the concept of audible feedback, as the sound samples will play independently of any input from the player.
Avoid illogical, conflicting and obsolete commands. Commands that have their ending time before their start time or are bound to impossible to reach triggers are either not working as intended or obsolete, and should either be removed or adjusted to work as intended. Commands of the same type whose intervals overlap should have their intervals and parameters adjusted so that they no longer overlap.
The Widescreen support setting should be turned on if the difficulty contains a widescreen storyboard. Alternatively, if the storyboard is designed for 4:3 resolutions, widescreen support should be turned off. This setting will not affect anything within the difficulty without a storyboard being present.
Make sure the storyboard is optimised as much as possible, within practical means.
Avoid having sprites, or the background of the difficulty, completely visually obstructed while rendered. Fading these out when otherwise not visible is preferable for the sake of performance. To fade out the background of the difficulty, turn the same background image into a sprite, with Background or 0 as second parameter, and fade accordingly.
Avoid sprites being partially off-screen or visually obstructed for the entire time they are used. In these cases the respective parts of the images should be cut unless this is necessary for an effect within the storyboard.
Avoid unnecessary transparency around storyboard images. For the sake of performance, images should be cropped as much as possible for their desired effects.
Use loops for commands that repeat themselves many times, unless this goes against what is visually intended. Using the loop command will often reduce the line count considerably, which in turn reduces file size.
Avoid using two axis-specific commands when the same effect can be achieved with one regular command instead. Using one command instead of two will mean less overall file size.
Use whichever image file format takes up the least file size whilst maintaining reasonable quality. .png format often takes up more file size for larger images due to the lossless compression method, unlike .jpg.
Avoid any duplicate image files. Having two instances of the exact same image adds unnecessary file size.
Refrain from having multiple sprites active while not rendered. Active sprites will still process commands regardless of whether they are visible or not. Should this be the case for longer periods of time, instantiate new sprites instead, for when visibility is regained.
When using many commands of the same type on a sprite, try leaving at least 16 ms between their start times. 60 commands per second is often more than enough for any sprite to make smooth transitions on an average setup. This is for the sake of reducing file size and loading times.
Fade out sprites activated from triggers after usage. Triggers will activate from their first possible command and stay active until the end of the difficulty, which is why fading these out when done is preferable.
