Battlefield 6 Zoom Sensitivity Coefficient Calculator
Pick your aspect ratio, get the coefficient to type in—then check menu vs PC profile format and the current limit before you change anything.
The ratio BF6 is running now.
Width ÷ height × 100.
Zoom Sensitivity Coefficient → 177.7
Settings → Mouse & Keyboard → Infantry → Control Settings
Hipfire cm/360 (optional)
Hipfire estimate only. Not zoom, FOV, or controller.
0–200 in 0.1 steps. Confirm the live menu.
Is 177.7 the same as 178?
No. On 16:9 the menu entry is 177.7. EA lists 178 as a starting value. They are not the same number to type.
0 is the other common reference. Posts tell you to put 0 so ADS feels slower as you zoom in. That is a different starting point, not a correction of 177.7.
Type the menu number at Settings → Mouse & Keyboard → Infantry → Control Settings. The six-decimal profile value (1.777777 on 16:9) is only if you edit PROFSAVE_profile on PC.
21:9 uses 233.3 in the menu. 32:9 is 355.5, which sits above the reported menu maximum of 300. The slider cannot take that number.
On PlayStation, Xbox, or a controller, use the menu number. There is no PC profile to edit. This page does not pick a best coefficient for you.
Is this the same as infantry zoom aim sensitivity?
No. Zoom Sensitivity Coefficient is one control. Per-zoom sliders—sometimes labeled infantry zoom aim sensitivity—are the other path. Use the one your current menu shows. Do not fill both.
Coefficient path — one setting
Use this when Uniform Infantry Aiming is on and the menu shows Zoom Sensitivity Coefficient.
Pick a reference above, enter the decimal menu value if the menu accepts it, then test the optics you actually use.
This is a reference format. It does not prove matching mouse travel or a best setting.
Per-zoom path — only if those sliders exist
Use this only when the menu exposes individual zoom / infantry zoom controls.
These sliders are not an extra step after a coefficient. If you already set the coefficient, treat the table below as a boundary check.
Reported per-zoom max is 200. A theoretical value above 200 is not the same as entering 200. Type only what the live menu accepts, then test.
What values match each aspect ratio?
Menu entries use one decimal. PC profile values use six. The unrounded ratio is math context—not a third number to enter.
| Aspect Ratio | Menu Entry | Raw PC Profile | Evidence Scope |
|---|---|---|---|
| 4:3 | 133.3 | 1.333333 | Listed in the community guide |
| 16:10 | 160.0 | 1.600000 | From the guide's aspect-ratio rule; not listed separately |
| 16:9 | 177.7 | 1.777777 | Listed in the guide; EA separately starts at 178 |
| 21:9 | 233.3 | 2.333333 | Listed in the community guide |
| 32:9 | 355.5 | 3.555555 | Listed in the community guide |
Zero is a reference, not a monitor ratio. See the first section if you are choosing 0 instead of a screen-edge value.
When do manual per-zoom values hit the max?
Only for the manual per-zoom path. Comparison is zoom × 100—a math boundary, not a verified preset or equal cm/360 proof.
| Comparison Zoom | Theoretical Value | Reported Menu Maximum | Boundary |
|---|---|---|---|
| 1x | 100 | 200 | Within reported max |
| 1.25x | 125 | 200 | Within reported max |
| 1.5x | 150 | 200 | Within reported max |
| 1.75x | 175 | 200 | Within reported max |
| 2x | 200 | 200 | Within reported max |
| 2.5x | 250 | 200 | Above reported max |
| 3x | 300 | 200 | Above reported max |
| 3.5x | 350 | 200 | Above reported max |
| 4x | 400 | 200 | Above reported max |
| 5x | 500 | 200 | Above reported max |
| 6x | 600 | 200 | Above reported max |
| 8x | 800 | 200 | Above reported max |
| 10x | 1000 | 200 | Above reported max |
A community report describes the per-zoom maximum above. When the comparison exceeds it, do not treat that max as an equivalent substitute—enter and test only what your current menu accepts.
What do two common setups look like?
Worked inputs you can reproduce—not player results or universal recommendations. Match them against your live menu before changing your own setting.
16:9 menu coefficient
- Input
- 16:9 display, Screen-edge ratio.
- Output
- Enter 177.7 in Zoom Sensitivity Coefficient.
- Reason
- 16 ÷ 9 × 100 is 177.777…. The cited guide truncates that to 177.7 in the menu and 1.777777 in the PC profile. EA's 178 is the rounded start, not a third setting.
- Action
- Enter 177.7, then test the optics you use in the Firing Range.
- Applies when
- Your menu offers Zoom Sensitivity Coefficient and accepts 177.7.
32:9 ultrawide profile boundary
- Input
- 32:9 display, Screen-edge ratio.
- Output
- Math gives 355.5 (menu format) and 3.555555 (PC profile).
- Reason
- 32 ÷ 9 × 100 is 355.5 in the documented decimal format—above the reported 300 menu maximum.
- Action
- Do not enter 300 as if it were the same coefficient. On PC only, use raw 3.555555 and restart BF6; otherwise type a value your menu accepts and test it.
- Applies when
- BF6 at 32:9 while the coefficient menu is still capped at 300.
Where do these rules come from?
Each game-facing rule names a public source, check date, what it covers, and what it does not. EA can change live settings; community posts are not official docs.
- EA Help: BF6 PC and controller settings
Covers: the BF6 settings menu. Names Zoom Sensitivity Coefficient and gives 178 as a starting value for mouse and controller.
Does not cover: raw PC profile values, a coefficient formula, or per-zoom limits.
Checked: 2026-07-29
- Jotunn's BF6 PC Sensitivity Guide
Covers: PC PROFSAVE_profile and the guide's own testing. Documents 177.7 / 1.777777 for 16:9 plus listed values for 4:3, 21:9, and 32:9.
Community material—testing includes Labs and Open Beta. Verify the current release before editing a profile. The cm/360 here scales only its published hipfire anchor.
Checked: 2026-07-29
- EA: Game Update 1.1.3.0
Covers: mouse sensitivity range. EA says this update doubled Infantry and Vehicle mouse-sensitivity range. With the guide's earlier range, this calculator derives its working input boundary.
That boundary is an inference, not a menu screenshot. The note does not state coefficient precision, profile serialization, or a per-zoom maximum.
Checked: 2026-07-29
- EA Forums: Uniform Infantry Aiming test at 300
Covers: the infantry coefficient control. A player reports testing Uniform Infantry Aiming from 0 through 300 in BF6.
EA-hosted community post, not an EA spec. Confirms 300 is testable; does not call it the maximum.
Checked: 2026-07-29
- Community report: 300% Zoom Sensitivity Coefficient maximum
Covers: the 0–300 coefficient boundary used in the result. A separate BF6 player report describes the same coefficient maxed at 300.
Vehicle-context player report, not an EA menu spec. With the infantry test above, it supports this working boundary—recheck the infantry menu after updates.
Checked: 2026-07-29
- Community report: 200% per-zoom maximum
Covers: the per-zoom boundary shown above. The report describes a current in-game maximum of 200% during a 6x test.
One player report, not an EA rule. It does not validate zoom × 100 or guarantee equal mouse travel.
Checked: 2026-07-29
How to Use
- 1
Choose the ratio BF6 is using
Select the aspect ratio on your active display. The result is a reference format—not a claim that every ratio feels the same in-game.
- 2
Choose a coefficient reference
If the menu offers Zoom Sensitivity Coefficient, pick screen-edge, fixed 4:3, or zero. Read the source scope before treating a value as current.
- 3
Use only the control your menu shows
Coefficient or individual per-zoom—not both. Do not add the per-zoom table after setting a coefficient; that table is a boundary check for the manual path.
- 4
Match the format you are editing
Coefficient path: use the decimal menu entry in BF6. Only PC profile edits use the raw PROFSAVE_profile value—and the guide says restart after that edit.
- 5
Test what you actually changed
Check the live menu boundary. Test hipfire and your real optics in the Firing Range. Keep a note of DPI, menu sensitivity, coefficient, and game build.
Frequently Asked Questions
Does this cm/360 result prove that all scopes match?
No. It is a hipfire estimate scaled from one community-guide example. It does not model ADS, optics, FOV, controller input, or game updates.