BerLIN Valorant Settings

BerLIN gear breakdown: what each piece actually changes

Mouse: Razer Viper V4 Pro Green at 4000Hz polling. At 4000Hz+ the mouse reports position every 0.25ms, which smooths micro-corrections on high-refresh monitors — but only if Raw Input Buffer is on in Valorant, otherwise the extra reports mostly add CPU load. DPI 100 with sens 0.41 means the in-game multiplier does the fine work while the sensor stays in its clean tracking range.

Display: ZOWIE XL2540K at 1920x1080. Lower resolutions like 1280x960 stretch targets wider and can make heads feel easier to hit, at the cost of peripheral clarity; native 1920x1080 keeps UI and minimap sharpest. Pair this with multithreaded rendering on, V-Sync off, and NVIDIA Reflex on+boost if available — frame latency matters more than texture detail for holding angles.

Supporting gear: Wooting 60HE+ for movement keys, VAXEE PA Little Devil under the mouse, and Razer BlackShark V2 Pro White for footsteps, none of which change eDPI, but all of which change consistency: a familiar pad glide and audible footsteps cut down unforced errors more than any sens tweak. If you copy one thing, copy the eDPI (328), not the brand names.

BerLIN crosshair explained: Green no center dot, inner lines (length 1, offset 0), outer lines off, outlines off

Import code: 0;P;c;1;h;0;0t;1;0l;1;0o;0;0a;1;0f;0;1b;0. In plain terms this is a Green no center dot, inner lines (length 1, offset 0), outer lines off, outlines off setup. Small inner-line crosshairs like this reward centered head-height placement — you see more of the target around the lines, which helps one-taps at range. The tradeoff is visibility on bright maps (Icebox snow, Breeze sand): if you lose the lines, switch the color to cyan or green rather than enlarging the gap, which would cost precision.

To try it: copy the code above, then in Valorant go to Settings → Crosshair → Import Profile Code, paste, and test in the Range against strafing bots before taking it into ranked. Full per-background preview lives on the crosshair preview page.

BerLIN vs other pros: same game, different mousepad math

BerLIN at 328 eDPI is 48 points above the pro average (280). As a mid-range hybrid aimer, BerLIN needs roughly 9.4 cm per 360° turn — plan mousepad space around that number, not around anyone else's brand of mouse.

Reading the table: lower eDPI favors calm angle-holding and spray control; higher eDPI favors entry swings and fast clears. None is "best" — pick the row whose turn-distance fits your desk, then use the converter at the top to match it on your own DPI.

How to copy BerLIN's settings without ruining your aim

1. Match eDPI first. Enter your DPI in the converter above and set the sens it gives you — that reproduces BerLIN's turn-distance exactly.
2. Keep your old crosshair for one session if BerLIN's lines feel alien; change sens and crosshair on different days so you know which change helped.
3. Set scoped sens to 1.3 only if you play the same scoped weapons; otherwise leave yours — scoped multipliers are personal.
4. Give it 3–5 ranked games, then adjust in 5–10% steps. One bad deathmatch is not data.

Data on this page is compiled from public pro-settings listings and community-verified corrections (see Suggest an edit above — 3 matching votes auto-updates a field). Last reviewed against our settings snapshot; if a value changed on stream, submit the correction and it ships after review. Source listing on ProSettings.net ↗

BerLIN settings FAQ

What sensitivity does BerLIN use?

BerLIN plays on 100 DPI with 0.41 sens — eDPI 328, scoped 1.3.

What is BerLIN's crosshair code?

0;P;c;1;h;0;0t;1;0l;1;0o;0;0a;1;0f;0;1b;0 (Green no center dot, inner lines (length 1, offset 0), outer lines off, outlines off).

What mouse does BerLIN use?

Razer Viper V4 Pro Green Polling rate 4000Hz.

Should I copy BerLIN's eDPI of 328?

Only if the turn-distance fits your space: about 9.4 cm per 360°. Match eDPI with the converter, test 3–5 games, then tune ±10%.