Frequently Asked Questions

FyeBeats is a producer-development community built around sharing beats, receiving useful feedback, competing, connecting with other creators, and improving over time.

Get better. Every beat.

FyeBeats is built primarily for music producers, but listeners can join too. Producers can upload beats, receive structured critiques, compete, build XP and REP, and grow their producer profile. Listeners can discover music, comment, and take part in supported community features without affecting official producer ratings.

FyeBeats is primarily focused on producer development, feedback, discovery, community, competition, and measurable progress. It is not designed around beat sales as the main experience.

FyeBeats supports Listener accounts and Producer accounts. Your role determines how you participate on the site, while FREE or PRO describes your membership level.

• Listener: discover beats, comment, and participate in supported community features.
• FyeBeats FREE: the core producer experience with ads and without a paid membership.
• Listener Ad-Free: $2.99/month or $29.99/year with no display ads or Discover Radio audio ads, while keeping Listener permissions.
• FyeBeats PRO: an optional producer upgrade at $6.99/month or $69.99/year, including no display ads or Discover Radio audio ads plus the benefits shown on the live membership page.

No. You can create a Listener account if you want to discover music and participate in the community without using producer-only features.

No. Listener comments are separate from official structured producer critiques. This keeps producer ratings focused on producer-to-producer feedback.

Yes. Supported account settings include password changes, and password fields can include a show/hide control while you type.

Yes. Supported email notifications can be turned on or off from your account settings.

Discover is where you browse beats from producers across FyeBeats. Supported search and filtering can help you narrow results by beat title, producer, genre, BPM, key, rating activity, and recency.

Depending on the view, a beat card can show the beat title, producer, artwork, BPM, key, genre, rating information, playback controls, and the beat-version indicator such as V1 or V2.

• Top Rated: prioritizes beats by rating performance.
• Most Rated: prioritizes beats with more rating activity.
• Most Recent: prioritizes newer uploads or current entries.

V1 means Version 1. It is the first version of that beat on FyeBeats. The V does not mean Verified.

Producers improve beats. You may change the mix, arrangement, sound selection, drums, structure, or another part of a track. Versioning lets you show that progress without erasing the history of the beat.

The beat advances to the next version number. The newest version becomes the current version, while previous versions can remain connected to the beat's history.

No. Feedback belongs to the version that was actually heard. A V1 critique remains a V1 critique, while V2 can receive fresh feedback based on the improvements in V2.

No. Beat-version labels and account verification are completely separate. V1, V2, V3, and so on only identify the version of the beat.

A beat can include supported metadata such as title, genre, BPM, key, cover artwork, audio, and critique preferences.

No. Custom cover artwork is optional. FyeBeats can still present a beat when custom art is not supplied.

Not necessarily. If it is the same beat with meaningful improvements, the version system is designed to preserve that progression instead of forcing you to erase the original.

Eligible producer accounts can leave structured feedback using the critique categories available for a beat. The goal is useful producer-to-producer feedback, not simply deciding whether a beat is good or bad.

Yes. Producers can disable supported critique categories for an individual beat. This is useful when a category is not ready to be judged yet.

Users cannot submit an official Mix rating for that beat while the category is disabled. The beat can also display a label such as “No Mix Feedback” or “Mix Feedback Off.”

No. A disabled category is excluded from the applicable aggregate score, so you are not penalized for intentionally choosing not to request that type of feedback.

Yes. Supported critique categories can be controlled individually when uploading or editing a beat.

XP stands for Experience Points. XP tracks your producer progression on FyeBeats. It is separate from REP: XP measures progression, while REP measures community reputation.

Producers progress from Level 1 up to Level 100. Level 1 starts at 0 total XP. Moving from Level 1 to Level 2 requires 100 XP. After that, each next level requires 25 more XP than the level before it.

Example: Level 1→2 requires 100 XP, Level 2→3 requires 125 XP, Level 3→4 requires 150 XP, and Level 4→5 requires 175 XP.

No. Your total XP is cumulative. The progress bar calculates how much of your total XP falls inside your current level and how much remains before the next level.

Producer levels are grouped into seven larger achievement tiers:

Level 100 is the top of the current producer-progression ladder.

XP is awarded through qualifying producer activity and achievements on FyeBeats. Beat Battles are a major progression path: advancing farther in a competition carries more progression value, and major accomplishments such as winning a battle carry the strongest rewards.

Qualifying uploads, revisions, listening, votes, community contributions, profile completion and Sound Kit activity also earn XP. Active Pro, Owner and current promotional Pro access double qualifying rewards on Friday, Saturday and Sunday in America/New_York. See the XP reward guide for amounts and daily limits.

Your live profile and progression panel are the source of truth for your current XP total, level, and progress.

Reaching a later round represents a larger competitive accomplishment. FyeBeats is designed so deeper tournament progress matters more than simply entering a battle.

XP is designed as a progression measurement representing earned experience and accomplishments. It is not intended to behave like a popularity score.

REP means Reputation. It reflects helpful participation in the FyeBeats community. REP does not measure production skill, industry status, account verification, or how famous a producer is.

REP is built by contributing constructive feedback that other producers find helpful. FyeBeats tracks constructive critiques and Helpful marks so the reputation system rewards useful participation instead of empty activity.

No. Producer tiers are connected to your producer level and XP progression. REP has its own separate community-reputation levels.

Charts highlight producers and music based on supported FyeBeats ranking signals. They are separate from XP, REP, and your permanent progression.

Chart Status indicates that a producer currently qualifies for an applicable FyeBeats chart. If the producer moves off that chart, the status indicator can be removed.

• Charts: current ranking or chart performance.
• Ratings: feedback on an individual beat or version.
• XP: producer progression.
• Level: your numeric progression level.
• Tier: your larger Bronze-to-Legendary achievement band.
• REP: community reputation.

Beat Battles are producer competitions hosted through FyeBeats. Each battle has its own rules, deadlines, entry requirements, and voting structure.

Every battle needs three valid votes before an official result. Voting stays open after its original deadline until the minimum is met. Votes and submitted beats remain locked. Reaching three votes before the deadline never closes a battle early; unresolved ties follow the published tiebreaker policy.

Participating producers must vote in every eligible matchup in their current round, excluding their own. Listen to both beats for at least 30 seconds before casting one locked vote. Your dashboard shows the actual remaining requirements. A win with incomplete participation holds advancement for staff review; documented exceptions and approved grace periods are available. Missing votes never automatically give your opponent a win. Eliminated producers have no new mandatory obligations in later rounds.

FyeBeats can support standard competitive battles and creativity-focused battles. Specific formats and requirements are shown on each battle.

Supported battles can require a listener to hear at least 30 seconds of each competing entry before voting. The goal is to reduce blind voting and make battle results more meaningful.

No. AI-generated beats are not allowed in FyeBeats Beat Battles. Battle entries are intended to represent the producer's own creative production work. Suspected violations can be reviewed and may result in battle removal or additional restrictions.

Yes. Battles are a major producer-progression path. Advancing deeper into a competition carries more progression value, with major accomplishments receiving the strongest rewards.

The first FyeBeats tournament is a free 16-producer competition. Producers are selected rather than automatically accepting the first 16 signups.

The winner receives a Producer Spotlight feature. Producers handpicked for the first tournament also receive first access to FyeBeats.

A producer profile can show supported information such as your producer name, profile image, cover image, beats, DAWs, genres, bio, ratings, REP, XP, level, tier, achievements, Chart Status, verification indicators, and other FyeBeats activity.

Your Profile is the public-facing view of your producer identity. Your Dashboard is your private control center for supported account information, analytics, progression, and producer tools.

Producer Spotlight is featured placement for a selected producer and their music. The Spotlight experience can include a music player featuring a beat from that producer.

Industry verification is an account-status indicator recognized by FyeBeats. It is completely separate from V1/V2/V3 beat-version labels.

Community is where supported users can participate in discussions, connect, share knowledge, and interact outside individual beat pages.

Yes. Listener accounts can participate in supported community features while producer-only critique and competition features remain restricted to eligible producer accounts.

Supported community interfaces can display role labels such as PRODUCER or LISTENER so users know which account role they are interacting with.

Yes. Supported private messaging allows producers to communicate directly for networking, collaboration, and community interaction.

Yes. Producer Challenge features are designed to let producers compete and interact directly under the rules of the specific challenge.

The notification system surfaces supported account activity such as feedback, beat interactions, updated versions, battles, challenges, Producer Spotlight activity, community activity, and other relevant events.

Yes. Supported site notifications can also be delivered through email, and email notification preferences can be managed in account settings.

FyeBeats uses a persistent player experience so supported audio can continue while navigating between pages. Playback should stop and the authenticated player should disappear after logout.

Yes. FyeBeats supports Dark, Light, and System appearance modes. System follows your device preference.

Yes. FyeBeats can release producer resources, downloads, tools, and care packages for the community, including the Producer Care Package when it is available on the site.

Yes. Voice Tag Gods is the dedicated voice-tag extension of FyeBeats, giving producers and DJs a direct path to custom voice tags and drops. AI voice-tag options are also part of the Voice Tag Gods roadmap.

Voice Tag Gods is the dedicated voice-tag extension of the FyeBeats ecosystem. It operates on its own website so the voice-tag experience can stay focused, while FyeBeats treats it as a core producer service alongside tools such as Beat Battles, Sound Kits, Community, and producer resources.

FyeBeats is built around useful feedback, fair competition, and producer development. Moderation helps protect those systems from spam, abuse, manipulation, harassment, and competition violations.

Depending on the situation, action can include content removal, battle-entry removal, feature restrictions, upload restrictions, account restrictions, or other moderation measures.

Applicable enforcement decisions can include a review or appeal process when supported by the feature or rule involved.

Yes. Certain competitive features can use identity-verification measures when needed to protect the integrity of a battle or tournament.