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.
Use the ratio BF6 is actually running. 16:9 is common; 21:9 and 32:9 are ultrawide.
Width ÷ height × 100. The community guide lists 4:3, 16:9, 21:9, and 32:9; 16:10 follows the same rule.
Enter 177.7 in Zoom Sensitivity Coefficient.
Menu location: Settings → Mouse & Keyboard → Infantry → Control Settings
Use the decimal menu format (one decimal place). A PC profile edit is not required.
Only for the hipfire cm/360 estimate. It does not model zoom, FOV, or controller input.
Working range here: 0–200 in 0.1 steps. Confirm the live menu; zero has no cm/360 estimate.
What does this calculator give you?
Choose your aspect ratio and reference. You get a Zoom Sensitivity Coefficient in menu format—and, when needed, the raw PC profile value—plus the limits those numbers sit under.
EA lists 178 as a starting point. A separate community guide maps aspect ratios to decimal menu entries and PC profile values. Mixing those formats is the usual way to enter the wrong number.
Type a profile-style value into the menu, or stack per-zoom after a coefficient, and ADS feel will not match what you thought you set—then you chase the wrong fix in the Firing Range.
When the numbers are right
- A clear menu entry (or PC profile value) for the ratio you picked
- A side-by-side of menu vs profile formats so you do not mix them
- Dated sources and reported limits before you change a live setting
Which path does your BF6 menu offer?
Builds expose different controls. Pick the one your current menu has, test in the Firing Range, and treat the other path as optional—not something to stack.
Coefficient path — one setting
Use this when 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 page returns a reference format. It does not prove matching mouse travel, FOV response, or a best setting.
Manual per-zoom path — only if those sliders exist
Use this only when your menu exposes individual per-zoom controls.
Per-zoom is not an extra step after a coefficient. If you already set the coefficient, treat the table below as a boundary check—not another list to type in.
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 coefficient choice, not a monitor ratio. The guide says it lowers ADS feel as zoom rises—test it in the current build.
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
- The guide's decimal menu format truncates 16 ÷ 9 × 100 to 177.7. EA's separate 178 is a rounded starting point.
- Action
- Use the decimal menu entry, then test your optics in the Firing Range.
- Applies when
- Your menu offers the coefficient control 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 use a value your menu accepts and test it.
- Applies when
- BF6 at 32:9 with the coefficient menu still capped at 300. Coefficient and per-zoom are alternative paths—not settings to stack.
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 should you read this BF6 coefficient?
This page gives formats and limits you can check—not a best setting.
EA starts at 178. A community guide maps aspect ratios to menu entries and PC profile values. Keep those sources separate when you compare numbers.
What does the setting change?
EA calls Zoom Sensitivity Coefficient your sensitivity while zoomed, and recommends testing in the Firing Range.
No source establishes one coefficient for every player, optic, input method, or update.
Why do 177.7, 177.8, and 178 differ?
16 ÷ 9 × 100 equals 177.777…—that is the raw math.
The cited PC guide writes 177.7 as the decimal menu entry and 1.777777 as the raw profile value.
EA publishes 178 as a rounded starting point.
Do not copy the unrounded calculation as if it were a separate menu setting.
How do you pick a starting point you can verify?
Pick the reference you intend to test. Record DPI and menu sensitivity. Then test the optics you use in the Firing Range.
The cm/360 here is a single-anchor hipfire estimate. It cannot verify ADS, scoped feel, FOV, controller response, or a future update.
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
What does Zoom Sensitivity Coefficient control in Battlefield 6?
EA describes it as your sensitivity while zoomed and lists 178 as a starting value. The setting is adjustable; neither EA source says one value is best for every player.
Why do I see 177.7, 177.8, and 178 for a 16:9 display?
177.777… is the unrounded 16:9 math. The cited PC guide gives 177.7 as a decimal menu entry and 1.777777 as the raw profile value. EA's 178 is its rounded starting point. Do not treat them as identical settings.
Can I use the raw profile value on every platform?
No. PROFSAVE_profile is a PC file format in the cited community guide. Use the in-game menu on other platforms and verify which values the current menu accepts.
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.
Should I apply manual per-zoom values after setting a coefficient?
No. Use manual per-zoom only when your menu exposes those individual controls. The table is a theoretical boundary check—not an extra preset for the coefficient path. Values above the reported 200 maximum are not enterable as that same number.