IMemory
Where a clipper's memory goes, and why Glint keeps so little of it.
An instant-replay clipper holds the last minutes of your game somewhere. Most of its memory is that footage, the encoder that makes it, and the window you look at it through. Here is what Glint does with each, with figures we measured and a calculator for your own settings.
IIWhere it goes
Three parts, and one of them is most of it.
10 minutes at 50 Mbps, with sound. By default only the newest 30 seconds are in RAM; the rest is in temporary files on disk. You can also keep all of it in RAM, or all of it on disk.
Measured while buffering, from 1080 × 720 to 2160 × 1440, 60 to 280 fps.
The program without its window. Closing the window frees the window's browser engine completely.
Measured on one PC: RTX 5060 Ti, Core i5-11600, Windows 11, 2160 × 1440 at 280 Hz, with video, desktop sound and microphone. The bars are to scale; the buffer's size is worked out the same way as the calculator below.
IIIHow
The choices that keep it small.
-
Recent seconds in RAM, the rest on disk
By default only the newest 30 seconds stay in RAM (15 seconds to 2 minutes, your choice). Everything older goes to temporary files in 64 MB pieces, deleted as the buffer moves past them. A clip up to the RAM length is saved straight from RAM.
-
No browser engine in the background
Glint's window is drawn by WebView2, the engine Windows already has. When you close the window, Glint destroys it, so the interface costs nothing while you play. The recorder is a small native program written in Rust.
-
A still screen costs almost nothing
Glint never makes up duplicate frames. When the picture does not change, nothing new is encoded, and silent audio is not written at all.
-
The graphics card does the work
Video is encoded by NVENC, AMF or Quick Sync, so the buffer holds compressed video, never raw frames. Without a hardware encoder Glint falls back to the processor, and the log says so.
IVWork it out
What your settings would hold.
The size of a buffer is bitrate times length, for every clipper. What changes is where it is kept. Move the controls to see where Glint keeps yours.
Glint in total: — of RAM, with the encoder and the program.
The calculator assumes the bitrate is used in full, as in a busy game at a fixed rate; a quiet screen fills the buffer more slowly. Desktop sound and microphone add about 0.38 MB a second, as measured. In Disk only, RAM keeps about one second of video and ten of audio. The encoder figure is the 131 MB measured at 2160 × 1440.
VComparison
Glint next to Medal, the NVIDIA app and Outplayed.
The things people ask about when they choose, including where Glint does less. None of the three publishes memory figures with a method behind them, so this table does not guess at any.
| Question | Glint | Medal | NVIDIA app | Outplayed |
|---|---|---|---|---|
| Memory and recording | ||||
| Where the replay buffer lives | RAM and disk by default; all RAM or all disk | RAM or disk, your choice | Disk (temporary files) | RAM by default; disk option |
| Memory figures published with a method | Yes, in the manual | None found | None found | None found |
| Interface while you play | Closed; window engine freed | Electron app; not documented | Not documented | Runs inside the Overwolf client |
| Graphics cards | NVIDIA, AMD, Intel; processor fallback | NVIDIA, AMD, Intel | GeForce only | NVIDIA, AMD, Intel |
| Record only the game's window | Yes, GAME mode | Yes, game capture | Not documented | In supported games |
| Separate audio tracks | Game, desktop, microphone | Game, microphone, Discord | Microphone apart | Not documented |
| Automatic clips of kills and highlights | No | Yes, about 15 games | Yes, supported games | Yes, supported games |
| Editing and sharing | ||||
| Timeline editor | Yes | Yes | No editor documented | Trim and combine; full editor paid |
| Vertical 9:16 export | Yes, with saved layouts | Yes | Not documented | Not documented |
| Cloud upload and share links | No, files only | Yes; auto sync paid | No | Yes, hosted for 3 to 12 months |
| Phone apps | No | Android and iOS | No | No |
| Cost and trust | ||||
| Price | Free | Free; Premium tier | Free | Free; Premium tier |
| Ads in the free version | None | Yes | None found | Yes |
| Account to record | None | Asked for at setup | Not needed | Not needed; watermark without a free login |
| Source code you can read | Yes, on GitHub | No | No | No |
Sources, checked November 2026
- Medal: recording buffer, Premium FAQ, auto clipping, editor, 9:16, audio tracks, recording method, account, Electron (job posting).
- NVIDIA app: features and login, FAQ (GPUs), sharing removed, temporary files location.
- Outplayed: FAQ (RAM buffer), account plans, app page (ads), encoders, Overwolf framework.
- Glint: the manual, sections Replay buffer and Measured.
Products change. If a row is out of date, say so on GitHub and it will be fixed.
VICheck it
Measure it on your own PC.
Numbers from someone else's computer only go so far. Compare clippers with the same settings, on your machine.
- Match the settingsSame resolution, frame rate, bitrate and buffer length in each clipper.
- Play for ten minutesA buffer fills over its length. Measure once it is full, in the same game.
- Open Task Manager, DetailsRight-click a column header, Select columns, tick Memory (private working set).
- Add up every processCount the clipper's helpers and encoder too. Glint's status bar shows its own total, buffer included.