How to Report or Block Someone in VRChat
Use VRChat's mute, hide, block, report, and Trust and Safety tools in the right order, preserve useful evidence, and understand what each control changes.
- Published
- Updated
- Reading
- 10 min read
Editorial maintenance
Reviewed, dated, and accountable
- Status
- current
- Reviewed by
- Mello Zone Editorial Team
- Last reviewed
- Next review
What changed: Published current VRChat blocking and reporting steps with evidence-handling and host-response guidance.
VRChat gives each user several ways to reduce an unwanted interaction. Muting, hiding an avatar, blocking a user, and reporting a violation are related, but they do not produce the same result. You can protect your immediate experience first and decide whether a platform report is needed without arguing with the other person.
This guide follows VRChat's current Help Center flow and adds a community-host perspective for organized furry meetups.
Interface note: VRChat changes menu labels and layouts over time. If a button has moved, use the current official Help Center article linked below rather than relying on an old screenshot.
Quick answer: protect your session first
If someone is disrupting or frightening you, create distance before documenting the incident.
- Move away, leave the instance, or ask a trusted host for help.
- Mute the user's voice or hide unsafe avatar features when that solves the immediate problem.
- Block the user when you do not want direct visibility or interaction.
- Report conduct that appears to violate VRChat's Community Guidelines.
- Use VRChat's ticket system when you have relevant screenshots or recordings to attach.
- Tell the event host separately when the incident occurred inside an organized community event.
You do not need to confront the person, announce the block, or collect perfect evidence before protecting yourself.
Platform and community reports are not emergency services. If an interaction includes an immediate, credible threat to someone's physical safety, leave the virtual space and contact the appropriate local emergency service or a trusted person who can assist in the affected person's region. Do not post a home address or other private identifying information in a public channel while asking for help.
Mute, hide, block, and report solve different problems
Mute stops a user's voice for you. It is useful for loud audio, unwanted commentary, or a conversation you do not want to hear.
Hide avatar features can suppress visuals, sounds, particles, animations, or other avatar behavior without removing every interaction. VRChat's Safety settings and Safe Mode provide broader ways to limit disruptive avatar features.
Block removes the other user from your personal VRChat experience. VRChat says blocked users in the same instance are not visible to you and cannot see or interact with you directly. Blocking is reversible.
Report sends a potential guidelines violation to VRChat's Trust and Safety process. A report is appropriate for harassment, abusive effects, crashing, hateful conduct, threats, sexual misconduct, or another violation. You do not have to block someone in order to report them.
A community host may also warn, remove, or ban someone from a group or group instance. That local action protects the event; it is separate from a VRChat platform report.
How to block someone in your current instance
VRChat's current instructions provide two common paths. Select the user directly, or open the Here tab in the Quick Menu and find the person in the instance list. Open the user's actions and choose Block User.
After blocking, do not remain nearby merely to test whether the block worked. Move to a trusted group, change instances, or take a short break if the interaction left you unsettled.
If a host is assisting, give the host the display name shown in VRChat and a short factual description. Avoid turning the moment into a public argument; public pile-ons can make evidence harder to interpret and expose more attendees to the disruption.
How to block someone outside your current instance
Find the account through user search, your friends list, or another in-app user list. Open the profile, choose Moderate User, and select Block User.
VRChat places the list of blocked users in the Social area of the Main Menu. You can select a blocked account there and unblock it later. Reversibility does not mean you owe anyone a second chance. Unblock only when you want to restore that visibility and interaction.
Blocking inside VRChat does not automatically block the same person on Discord, Bluesky, Telegram, or another service. Use each platform's own controls when unwanted contact crosses platforms.
How to report a VRChat user
For someone in your current instance, select the user directly or locate them in the Quick Menu's Here tab. Choose Report, select the most accurate reason, and provide a concise description.
For someone outside the instance, locate the account, open Moderate User, and choose Report User.
A useful report states what happened, where it happened, and approximately when. Describe observable behavior rather than guessing at intent. For example: "The avatar emitted repeated full-screen flashes after two attendees asked the user to stop" is more useful than "This person is evil."
Choose the closest reporting category. Do not submit several duplicate reports to force attention, and do not encourage a crowd to report an account based only on a secondhand claim.
Users are not the only reportable VRChat element. The platform provides reporting paths for avatars, worlds, and groups as well. Report the object that contains or enables the violation: a malicious avatar should not be described only as a personality conflict, and a group systematically operating against platform rules may require a group report rather than a report about whichever member happened to be visible.
If the same behavior crosses Discord, a website, or another service, use each service's official reporting route for what occurred there. A VRChat report should still stay focused on relevant VRChat conduct and verifiable off-platform context permitted by the current guidelines.
When to use a Trust and Safety ticket
VRChat directs users with screenshots, recordings, or other supporting material to its ticketing system. Select the moderation-report path and provide the requested context.
Use a ticket when the in-app fields cannot hold relevant evidence, the behavior occurred across instances, or the report needs a clearer timeline. VRChat says moderation requests sent through Discord are redirected to the official ticket form, so use the platform's published route rather than messaging unofficial accounts.
Not every report receives a personal response, and VRChat may not disclose the action taken against another account. That does not make the report pointless. The platform can still use it during review.
How to preserve useful evidence without escalating risk
Evidence should document the incident, not create a second privacy problem.
- Write down the display name, date, approximate time, world, instance context, and event name.
- Preserve only screenshots or clips that directly show relevant conduct.
- Keep original files when possible instead of heavily editing them.
- Note what happened immediately before and after the captured moment.
- Do not publish identity information, private messages, or allegations as a social-media callout.
- Share evidence only with the platform team or authorized community reviewers who need it.
- Follow announced recording rules and applicable law.
If capturing evidence would keep you in danger or intensify the interaction, leave. Safety comes before documentation.
Recordings can contain voices, display names, commissioned avatars, private conversation, or bystanders who did not agree to publication. Keep evidence private, collect no more than the report requires, and review applicable recording law before capturing audio. Evidence supplied privately to an authorized reviewer should not be repurposed into a public recap or callout post.
What a community host should do
A host's first job is to stabilize the event. Separate the reporter from the disruption, bring in another authorized moderator when available, and use the least severe action that safely restores the boundary. Immediate removal may be appropriate for credible threats, sexual misconduct, hateful conduct, crashers, or repeated refusal to stop.
Record the local action and the factual reason. Tell the affected attendee where to send a private follow-up. Do not promise a specific platform enforcement result, and do not share sensitive evidence with the wider host team when only designated reviewers need it.
Community reporting and VRChat reporting can happen together. The Mello Zone Safety Center covers community conduct, while VRChat remains responsible for its platform rules. For event preparation, see How to Organize a Safe VRChat Furry Meetup.
Hosts should also watch for enforcement evasion. A replacement account, repeated re-entry, or contact through another attendee can require a new local action and updated platform report. Document the observable connection without publicly accusing unrelated people, and revise invitation permissions when the access path itself was compromised.
What blocking does and does not do
Blocking changes your direct experience of the user. According to VRChat, a blocked user may remain in the same instance and interact with the world or its objects, even though the two of you are hidden from one another. Other people may still see both users.
That means a block is not the same as removing someone from an instance, banning them from a group, or submitting a platform report. If a blocked person continues disrupting a group event through world objects or effects that others can perceive, tell a host and consider a report.
Blocking also does not erase prior screenshots, recordings, messages, or contact on other services. Review connected-platform privacy settings if the situation is broader than one VRChat session.
After the incident
Once you are safe, write a short timeline while details are fresh. Submit any appropriate platform and community reports. Then stop monitoring the other person's profile unless the platform or reviewer requests specific follow-up information.
For community hosts, conduct a limited review: Did the access setting work? Were moderator roles clear? Could attendees find the reporting route? Did recording rules help or create confusion? Update the runbook without publishing the affected person's story.
Attendees do not need to earn the right to mute, hide, or block someone. Those tools exist so each user can shape a safer personal experience. Reports add platform accountability when behavior crosses the published rules.
