Modbot Docs
Companion

Clips

Keep the last few minutes of VRChat and its sound while it is running, and save them as a video file — from the settings page or from inside your headset — or let the group's Modbot ask for a clip of a ban, kick or warning you made. Off unless you switch it on.

Something happens in an instance and it is over before you could have started recording. Clips is the answer to that: while it is on, the companion keeps the last few minutes of VRChat, picture and sound, and Save a clip writes those minutes out as a video file on your PC.

This reverses something the companion used to promise

Until 19 September 2026 the companion said, in its own source and on this site, that it never captured the screen, by any route, for any reason — and then, for part of that day, that a clip had no sound in it at all. Neither is true now, and this page is the honest replacement rather than a patch over it.

A clip carries VRChat's sound, which in an instance is what the people around you said. That is the point of it — a silent picture of somebody being abusive shows nothing — and it means a clip is a recording of a conversation sitting on your disk until you delete it. Worth knowing before you turn it on rather than after.

The other half of that promise — that nothing the companion records leaves your PC — has been narrowed twice. Since 1 October 2026 a separate box, off until you tick it, can tell your group's Modbot that you saved a clip, with the file's fingerprint — see telling your group a clip exists. Since 24 October 2026 the companion has one way to send a clip, and only if you tick another box that is off: it can answer a request your group's Modbot made for a clip of a ban, kick or warning you made — see clips for your own actions. It cannot send a file any other way.

It records VRChat's window and VRChat's sound, not your screen and not your speakers. The sections below say exactly what that does and does not keep out.

It is off until you switch it on

A fresh install has it off. An existing companion updated into a version that can record has it off. While it is off there is no recorder at all — no recording, no sound, no video encoder, no extra thread, and nothing written anywhere.

Settings → Clips → Keep the last few minutes, with VRChat's sound is the whole of the consent. Discord's sound too is a second box beside it, and it is off as well. Tell the group's Modbot when I save a clip is the third, and it is off too; it records nothing, and is below. Send clips for my actions automatically is the fourth, and it is off as well; it is below.

What is recorded

VRChat's window. Not your screen.

The companion asks Windows for VRChat's own window, finds where it is drawn, and records that rectangle — shrunk to at most 1280 pixels wide, at 15 frames a second. A 2560×1440 window records at 1280×720; a 1920×1080 one at 960×540. It is deliberately modest: your frame rate in VRChat matters more than how sharp the clip is.

What a clip looks like

VRChat's picture, filling the frame. What you saw in VRChat is what you get, at a smaller size.

The frame's size is decided once, when recording starts, from VRChat's window as it was then. It cannot change after that — a video file cannot change size part way through, and starting a new one every time you resized a window would throw away the minutes you are about to want. So if the window changes size while Modbot is recording, the picture is scaled to keep filling the same frame rather than shrinking inside it.

The one thing that cannot be scaled away is a change of shape. If you go from a wide window to a tall one mid-recording, the picture keeps its proportions — nobody in a clip is ever stretched — so a strip is left over. It is as small as it can be and it is centred, not pushed into a corner. Go back to the shape you started at and it is gone.

If you have a clip that is a small picture in the corner of a black frame

That was a bug, fixed on 19 September 2026. Before the fix, Modbot drew the picture at whichever size its graphics card could halve it to and painted the rest of the frame black — and for a lot of window sizes that landed one halving too far, putting the picture in the top-left quarter of an otherwise black clip. Clips recorded after the fix fill the frame. Clips you already saved cannot be repaired; record a new one.

What can still end up in a clip

Being straight about this, because it is the one thing on this page where "records VRChat's window" is not the whole answer.

The companion takes a copy of a picture Windows has already drawn, and cuts VRChat's rectangle out of it. So anything drawn on top of VRChat while you are in VRChat is inside that rectangle and is in the clip:

  • A chat program's in-game overlay, and Steam's.
  • A Windows notification that pops up over the game.
  • A window you pinned to stay on top.
  • Modbot's own panel, if you have the window over VRChat open.

While you are working in another program, nothing new is recorded at all. Alt-tab to Discord and the clip holds the last picture of VRChat until you come back — it does not start recording Discord. That is the important half: VRChat's default is a borderless window filling the whole screen, so without this rule a clip would be your whole monitor every time you tabbed away, which is exactly when your private messages are on it.

The cost of that rule is worth knowing too: if you spend the whole recording in another program, the clip is a still picture with the sound still running. A dull clip, not somebody else's messages.

The sound

A clip carries VRChat's own sound. In an instance, that is the voices of the people around you. It keeps running while you are alt-tabbed, so a clip of a frozen picture can still be a usable recording of what was said.

Discord's sound can go in as well, and that is a separate box, off until you tick it. Settings → Clips → Discord's sound too.

Nothing else this PC is playing is ever in a clip. Not music, not a video in a browser, not another chat program, not Windows' own notification sounds — and there is no setting that would turn any of that on.

That is not a filter and not a promise about behaviour. Windows can hand a program the sound one named program is playing, separately from everything else, and that is what the companion asks for: VRChat, and Discord if you ticked it. The call that hands over everything coming out of your speakers — the one every ordinary recording program uses — is banned everywhere in the client, including inside the file that records sound, and the build fails if it appears. Once sounds are mixed together they cannot be taken apart again, so "everything except your music" is not a thing anybody can honestly offer; asking for one program at a time is.

No microphone is opened for a clip. The companion can open your microphone for exactly one other thing — listening for a phrase — and that is a separate switch, off until you turn it on, that records nothing.

Think about the people in the instance

The point of the sound is that a clip shows what happened rather than what it looked like. The same sound is other people's voices, kept on your PC. Your group's rules about evidence apply to a clip exactly as they apply to a screenshot or a log, and this page is not advice about them — it is so that you know what is in the file.

What is not recorded

  • Nothing outside VRChat's window. Not a second monitor, not a window beside the game, not the taskbar, and not whatever you have alt-tabbed to.
  • No sound but VRChat's, and Discord's if you ticked it. Not your microphone, not your speakers, not your music, not your browser. See the sound.
  • Not the keyboard, not the clipboard, not a list of the programs you are running or of their windows. It asks Windows for one named window — VRChat's — and never for a list of what else is open. To record Discord's sound it has to know which program Discord is, and it asks that of the connection point Discord itself publishes for games to find it by, rather than by reading a list of what you have running. Nothing is sent to Discord and nothing is read from it.
  • Nothing read out of a folder. Not your Pictures, not your Documents, not your Desktop, not VRChat's own screenshot folder. The companion still never opens an image it did not make.
  • Nothing at all while VRChat is not running. See below.

It records only while VRChat is running

The companion knows VRChat is running because lines are arriving in VRChat's own log — the same file it already reads. It never goes looking for a running program; it cannot, and that ban has not moved.

So: VRChat closes, recording stops and what was kept is deleted. VRChat opens, recording starts again. The Clips card says which of those is happening — Off, Waiting for VRChat, Waiting for VRChat's window, Nothing recorded yet, or Recording.

Because a clip is VRChat's window, the companion also has to be handed that window before there is anything to keep. That takes a second or two after VRChat starts, and the card says Waiting for VRChat's window while it does.

If VRChat's window closes, is minimised or is moved to a monitor the companion is not recording, the clip holds the last picture of it rather than ending — and if you resize VRChat, or change your resolution, the clip keeps its size and the picture is fitted inside it. A clip is never left half written.

If VRChat is running but the companion has stopped understanding its log, it keeps recording. Lines are arriving, so you are in a world, and a client that needs updating should not also quietly lose the recording you switched on.

When a clip cannot be made

The companion will not hand you a file with nothing in it. Until it has captured one real picture of VRChat's window, there is nothing to save — it has not opened a recording, has not written a frame, and says Nothing recorded yet on the Clips card and on the overlay. Save a clip cannot be pressed while it says that.

That is the honest answer to a case that is easy to hit: the rule above is that nothing new is recorded while you are working in another program, so if VRChat has not been the window in front since you switched Clips on, nothing has been captured at all. Alt-tab to VRChat for a moment and it starts.

It clears itself. If it does not — if it stays on Nothing recorded yet while you are playing — the companion's own log file says what it is seeing: which graphics card and screen it is recording, where VRChat's window is, how many pictures it has copied. It is at %APPDATA%\Modbot\logs, and it is the thing to attach to a bug report.

A save that fails for any other reason — a folder that cannot be written to, a recording that stopped — says so too, on the card and on the overlay, rather than leaving you with a file you find out about later.

Sound is the one thing that can be missing without stopping anything. If VRChat is not playing anything, if Discord is not running, if your Windows is older than version 2004, or if Windows refuses to hand a program's sound over at all, the clip is recorded exactly as it would have been and that part of it is silent. Nothing fails, nothing is said on the card, and the companion's own log file at %APPDATA%\Modbot\logs says which programs' sound went in.

Saving a clip from inside VR

Save a clip is on the overlay panel, under the tabs, above whichever screen is showing. From the roster, from the events list, from a person's card — it is one press. It is on the headset panel and on the window over VRChat alike, so it works whether you play in a headset or on a monitor.

It is only there when Clips is switched on. Turn Clips on and the control appears; leave it off and the panel is exactly as it was.

It tells you what is actually happening rather than looking pressable and doing nothing:

What it saysWhat that means
Save a clipThe last few minutes are being kept. Press it.
Waiting for VRChatVRChat is not running, so there is nothing to keep.
Waiting for VRChat's windowVRChat is starting. This clears itself in a second or two.
Nothing recorded yetNo picture of VRChat has been captured. See when a clip cannot be made.
The folder cannot be usedClips cannot be written where they are pointed. The Clips card on the Settings page says why.
Not available on this machineRecording does not work here. See Windows only.
Recording stoppedSomething went wrong. The Clips card says what.

Only the first of those can be pressed. Nothing happens if you press any of the others, and the control is not drawn as though it could be.

After you press it, it tells you how it went — Clip saved or Clip not saved, for about eight seconds — because with a headset on there is no other way to find out. The clip is in your clips folder, waiting for you when you take the headset off.

Or say it

If reaching the panel is still too much in the middle of something, Listening lets you say "Modbot, clip that" out loud instead, and the companion tells you whether it worked. That is a separate switch, off until you turn it on, and it opens your microphone while VRChat is running — that page is the whole of what it does and does not do.

There is no keyboard shortcut for this, on purpose. The companion asks Windows only for the keyboard combinations you set yourself: the one that brings up the window over VRChat, and the Talk hotkeys if you record them. It never reads any other key, and that is how it can say it does not read your keyboard. A shortcut for this would be one more combination taken from every other program, for a control that is already on the panel.

How many minutes

Between 2 and 10, on the slider. Anything else in the settings file is brought inside that range, so a typo cannot put an hour and a half of video on your disk. A rule that needs Clips ready needs the 10-minute setting, so that a clip it saved holds at least five minutes.

A saved clip covers at least half the length you chose, and up to all of it. The companion keeps two overlapping recordings and hands you the longer one; that is what removes the case where you press Save a moment after a recording started and get nothing. Save twice within a minute and the second clip is short, because the first save is what started it.

Where clips are written

By default, your own Videos folder plus Modbot Clips — Windows is asked where that is, so a profile on another drive or a Windows in another language lands in the right place.

Change it in Settings → Clips → Folder. Leave it blank for the usual place. A folder that cannot be written to — a read-only drive, a USB stick that is not plugged in, a typo — is shown as a message on that card. Nothing else in the companion stops: it carries on reading VRChat's log and reporting to your servers exactly as before.

While it is recording, the two rolling recordings live in the companion's own folder, %APPDATA%\Modbot\clips, never in your Videos folder. They are deleted as they are replaced, when VRChat closes, and when you quit the companion.

What a clip is called

The Black Cat_98874_2026-09-19 18-02-29.mp4

The world, the instance number, and the date and time you saved it — your own local time, so it matches when you remember it happening. Underscores between them, and .mp4 at the end.

  • The world is its readable name, the one VRChat shows you. If the companion has not been told it yet, the world's id stands in; outside an instance the name is just the date and time.
  • The instance number is the number VRChat puts at the front of an instance's id — 98874 above. A group that has set its instance to something readable gets that instead.
  • Anything a file name cannot hold is taken out of the finished name, so a world named with a slash or a colon in it still saves. Non-Latin world names are kept as they are; they are perfectly legal in a file name.
  • Two clips saved in the same second in the same instance do not land on each other — the second gets (2).

What stops the folder filling your disk

Video is large, so three things bound it:

  1. The rolling recordings are not clips. There are only ever two, each replaced as it fills, and all of them deleted when recording stops. At five minutes they come to about 120 MB together (about 240 MB at ten), sound included.
  2. The clips folder has a limit — 5 GB by default. Before a clip is saved, the oldest clips are deleted until the folder plus the new one fits. Set it with keepGigabytes in settings.json; there is no control for it on the screen.
  3. The newest clip is never deleted to make room. A limit smaller than one clip will not delete the thing you just saved.

Only .mp4 files the companion wrote are ever counted or deleted. Your own videos sitting in the same folder are not Modbot's to touch.

What leaves your PC

A clip you saved yourself stays a file on your PC until you choose it in a browser. No frame of it and no second of its sound is sent anywhere. Not to Modbot Cloud. Not to us.

The one way a clip can leave your PC by itself is the answer to a request your group's Modbot sent to your companion, for a ban, kick or warning you made, and only if you ticked Send clips for my actions automatically. It goes to that Modbot and nowhere else — never to Modbot Cloud. The companion has no way to send a file unasked.

The token it holds after pairing can submit what it observes, read what the overlay needs, and answer a clip request the server already sent to that device with a file. It cannot start an upload on its own, it cannot ask for a clip, and it cannot read anything that is attached.

Until 1 October 2026 not even the fact that a clip existed left your PC. It still does not, unless you tick the box below.

Telling your group a clip exists

Settings → Clips → Tell the group's Modbot when I save a clip. Off until you tick it.

Ticked, when you save a clip in one of your group's instances, the companion tells that group's Modbot — and nobody else — one thing: this moderator saved a clip here, at this moment, and this is its fingerprint. Exactly these fields:

SentNot sent
Your VRChat user id and display nameThe clip, any picture from it, any of its sound
The world and the instanceThe clip's file name, or where it is on your PC
When you pressed Save a clipAnything at all about a clip saved outside your group's instances
The file's SHA-256 and its sizeAnything to Modbot Cloud

Your group's Modbot takes it only from a companion paired to your Modbot account, about your VRChat account, so your Modbot account needs your VRChat account linked. It is shown as saved on your PC, by your Modbot username, whatever name the companion sent. Without a linked VRChat account the companion's Audit Log page shows the event as failed, with a note saying the server refused it because it is not about the VRChat account linked to your Modbot account, and nothing is kept.

A SHA-256 is a fingerprint: 64 characters worked out from every byte of the file. The same file always gives the same fingerprint and any other file gives a different one, and nothing about the video can be worked out from it. It is worked out once, on your PC, after the clip is written.

What your group gets from it:

  • The instance's audit log says "Alex saved a clip in The Black Cat #98874 on their PC. It was not uploaded."
  • The case file of anybody who was in that instance then lists it — Clip saved on Alex's PC at 9:14 PM (not uploaded) — with an Attach beside it. See below.
  • When the clip is attached, Modbot knows it is the clip rather than any video somebody chose, because its fingerprint matches. It keeps where and when it was saved, and whose PC it came from, with the file.

The companion's Audit Log page shows the line it sent, the same as every other event. Pausing a server stops this too: a paused server hears nothing.

Attaching a clip you saved yourself to a ban, a kick or a case

In Modbot's web app, in your browser, signed in as yourself. (A clip Modbot asked your companion for is attached by that answer, not by you — see the next section.)

If you ticked the box, open the case file. Under Evidence, each clip saved while that person was in the instance has a line of its own: Clip saved on Alex's PC at 9:14 PM (not uploaded), with the instance and the file's size. Press Attach and choose the clip from your clips folder; the file's name has the world, the instance and the moment in it, so it is easy to find. Modbot checks the file's fingerprint against the one your companion sent. The right file is attached and marked as a clip, with where and when it was saved. Any other file is refused, and nothing is attached.

If you did not, attach it the way you attach anything else: choose the file. video/mp4 is an accepted kind of evidence, so a saved clip needs nothing special.

Either way the companion writes a line into its own Audit Log page saying a clip was saved.

Clips for your own actions, sent automatically

Settings → Clips → Send clips for my actions automatically. Off until you tick it.

Without a box ticked, nothing here happens. With it ticked, Modbot can ask your companion for a clip of a ban, kick or warning you made, so the case has the footage without you pressing anything.

Which actions ask for a clip

Your group's leads choose this in Settings, Ask for a clip on: bans, kicks and warnings, each on or off, for the whole group. A clip is asked for only when:

  • the action is one of those, and you made it — in Modbot, or in VRChat's own menu (Modbot sees that in the group's audit log and matches it to the Modbot account with your VRChat account linked);
  • your companion was in the same instance as the person the action was taken against, at some point in the last 10 minutes;
  • your group has evidence storage set up, because that is where the clip is kept.

Otherwise no clip is asked for. When your companion was not there, the action shows Not in the instance, and that is not counted as a missed clip: nobody could have recorded it. Modbot only ever asks the companion of the moderator who made the action, never anybody else's.

While any moderator's companion is in one of your group's instances, Modbot reads the group's audit log at least once a minute, so a request does not wait for a slow check.

What the companion does

The request comes down the connection the companion already holds to your group's Modbot. The companion keeps that connection open the whole time it runs, whether or not you are in an instance and whether or not this box is ticked, which is how Modbot knows a companion is open and paired. The request names the action and the moment it happened, and nothing else.

  • Clips is off, or the box is not ticked: the companion answers that, and nothing is cut.
  • Otherwise it waits until it has 30 seconds recorded after the action, finds the moment in the longer of its two rolling recordings, and cuts a copy: 30 seconds after the action, and as much before it as fits under 100 MB. It checks the copy opens and is as long as expected, then sends it.
  • If it cannot cut one, it sends the whole recording if that is under 100 MB. If it is not, it says Clip couldn't be cut.

Each clip it sends is written to the companion's Audit Log page, like every other thing it sends.

How the server takes it

A file is accepted only as the answer to a request the server sent to that same device, for that request's id, within 15 minutes of the request, once, and no larger than 100 MB. Anything else is refused. The clip is kept as evidence on the action, marked as a clip, with where and when it was saved, whose PC it came from and its SHA-256.

What shows on the action

Each action Modbot asked for a clip shows one of these:

StatusWhat happened
Clip attachedThe clip arrived and is kept as evidence.
Clip failed to uploadThe companion had a clip and could not send it.
Clip couldn't be cutThe companion could not make a clip of that moment.
Companion didn't answerNothing came back within 15 minutes.
Clips was offThe companion answered that Clips was not recording, or the box was not ticked.
Not in the instanceYour companion was not there, so no clip was asked for.

Every one of those except Clip attached and Not in the instance counts as a missed clip. A group's automatic role can need Clips ready — Clips on, the 10-minute setting, this box ticked, and Discord's sound too ticked — and the companion reports those four when it checks in. The box alone counts; Discord does not need to be running.

What a stolen sign-in can and cannot do

Somebody who steals your companion's device sign-in can answer a request the server already sent to that device, with a file, once, inside the 15 minutes. It cannot upload anything nobody asked for, ask for a clip, start a recording, or read anything it could not read before. It still reaches no case file and no other evidence. Revoking the device ends even that.

Untick the box and the companion answers every request with Clips was off.

What it costs while you are playing

The companion records at a low frame rate and a small size, uses your graphics card's own video encoder when it has one, and does the work on a thread below everything else. On a machine that can run VRChat this should be a percent or two of your graphics card's encoder and about as much of one processor core. The sound adds about a megabyte a minute to the file and very little else; asking Windows for one program's sound costs that program nothing and does not change how it sounds to you.

That is an estimate, not a measurement. If it costs you frames, switch it off; the switch takes effect immediately and nothing else about the companion changes.

Windows only

There is no recording on the Linux companion, and there is no plan to add one. The Clips card says so rather than failing quietly, and everything else on Linux works exactly as it does on Windows.

The reason is the video encoder, not the recording. Windows has one built in, which is what the companion uses. On Linux the usual answer is to run ffmpeg as a separate program, and this client never starts another program — that is one of the things it can point at when somebody asks why it should be trusted on a personal machine, and it was not going to be given up for this. The other route, bundling a video library of its own, means shipping and maintaining something large for a feature a few people would use.

A half-working recorder that wrote files nobody could open would be worse than one honest sentence, so it is one honest sentence.

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page