Free Fire India settings: sensitivity range, HUD codes and graphics

This page collects the adjustable items for sensitivity, HUD and graphics, plus the official change record behind each one. Every feature description comes from Garena global-version patch notes and is not India-client testing; the India-version interface paths, available presets and device support need confirming in-game. It gives no “recommended sensitivity”, because no single value works across devices.

Why can’t you copy sensitivity values from the internet?

Because the number is not an independent parameter; it is tied to at least four things: device model and screen size, grip and number of fingers, network latency, the mode you play. The same set of values that is “just controllable” on someone else’s device may be “always overshooting” on yours.

There is a subtler reason too: the sensitivity scale has changed. An official patch raised the sensitivity cap to 200, while plenty of old guides still write for a 0–100 scale. The two sets of numbers cannot be compared directly, and you must not mechanically double your own values just because the cap doubled — later algorithms, devices and modes all affect the actual feel.

Evidence level: Global reference — The scale change comes from global-version patch notes, not India-version testing; the current India-version scale and interface are whatever the client shows.

What is the sensitivity cap, exactly?

An official patch explicitly raised the sensitivity cap to 200, and the same note also introduced recommended graphics and a 40-FPS option. What can be confirmed is that “the cap was raised at some point”; what cannot be confirmed is that “the cap in your client right now is definitely 200”, because version and region may differ.

There is only one practical suggestion: check the maximum value of the slider in your own client first, then decide which old guide to consult. If the maximum does not match the scale the guide writes about, that set of numbers does not apply.

Which groups are settings split into?

An official patch splits in-match settings into five groups — Controls, Information, Sensitivity, Auto Pickup, Vibration — and allows sensitivity and sound to be adjusted one unit at a time with buttons (instead of only by dragging a slider). The same note also mentions that the character page supports both brief and detailed skill descriptions, and that the preset page was reorganised.

That means two things:

• Fine-tuning by 1 unit is possible; you do not have to accept the slider’s minimum step.
• When you cannot find a setting, look by group first instead of scrolling through the whole page.

The exact path depends on your current local client — group names and hierarchy may change between versions.

Evidence level: Global reference — The groups and the unit-by-unit adjustment come from global-version patch notes; the India-version interface has not been verified.

What is a HUD share code, and what can it change?

The official OB49 note introduced HUD share codes, expanded the customisable range for button size and transparency, and added custom elements such as the vehicle entry, Gold and kill count.

Three limits when using them:

• A share code is not an account credential. Anyone who asks for your password or OTP on the pretext of “tuning your sensitivity” is behaving suspiciously; a share code itself should not be used as a login credential either.
• A share code solves “moving a layout”, not “fitting your feel”. After importing someone’s layout the button positions are right, but the sensitivity still has to be tuned by you.
• Setting button transparency too low means you cannot find the key during a fight; that is an expected side effect, not a bug.

Are HUD and sensitivity synced separately?

Not necessarily together. The official OB52 note mentions a new Settings → HUD recommended page where you can browse pro player layouts; a share code can contain both layout and sensitivity, and when applying it you can decide whether to sync the sensitivity.

This mechanic explains a common confusion: settings changing after you import a layout may be related to the sync option and is not necessarily a game fault. Before importing next time, check whether sync sensitivity is ticked.

Two more things to keep in mind: whether a given preset is usable in the current version, and whether the attributed author identity is genuine, both have to be based on the client record; you cannot go by the name shown on the share page alone.

Evidence level: Global reference — The recommended page and the sync option come from global-version patch notes; whether the India version has that entry has not been verified.

What can the Training Ground verify, and what can’t it?

The official OB50 note added a skill cooldown and shooting sensitivity settings panel to the firing range, and made special arrangements for Gloo production in the combat area. That leads to a direct conclusion: cooldowns, resources and revival rules in the Training Ground are not necessarily the same as in BR or CS.

So a test report must state clearly whether the scenario was “Training Ground / custom / ranked”. Being able to practise endlessly in the Training Ground does not mean skills are that frequent in a real match; sensitivity tuned in the Training Ground also has to be re-checked in live matches.

Is the frame rate boost available on every device?

No. The official OB52 note announced the Experimental Frame Rate Boost in High FPS mode. The announcement does not therefore guarantee that every device can reach 120 FPS or hold a steady high frame rate.

The visibility of this feature, its thermal behaviour, battery drain, screen refresh rate and chip capability all need testing. There is also no verified complete device-requirement list for the India version yet, so this site gives no conclusion such as “model X can run at Y frames”.

Evidence level: Unverified — There is no test data for frame rate, heat or battery drain on specific device models in the India version.

Do vehicle HUD and first person need separate tuning?

• Official patch notes have described a custom vehicle HUD, which shows that vehicle-related button layouts can be configured separately.
• Another patch described the CS first-person experience and a separate first-person sensitivity setting.

So do not treat first-person sensitivity as a universal value for third person; and do not assume that because first-person settings existed historically, every mode currently offers first person. These are two different things.

Weapon data and Gunsmith: why does screenshot testing go wrong?

Official patch notes added stats, upgrade changes and acquisition paths to the Armory, and announced that Gunsmith can combine a single gun’s skin appearance and stats under the rules in force at the time.

The conclusion is practical: you cannot judge in-match stats from a gun’s appearance alone. When producing screenshot-based testing you must record the skin and stat scheme equipped, otherwise the difference between two runs of “the same gun” gets misread as a version balance change. Current specific unlock conditions and available skins are whatever the client shows; for weapon categories see Weapon categories and official descriptions, and for the relationship between range and recoil see Range roles, recoil and attachments.

What creator capture features are there?

The official OB52 note added character lock, camera lock, filters, multi-camera templates and Highlight Photos; automatic photos can be triggered by events such as a CS team wipe, consecutive eliminations or headshots, and the number saved is limited. The OB54 note then announced BR review routes, events, nearby enemies and hot zones, and improved the free spectator camera.

These tools suit original tactical commentary, but there are two limits: a limited save count means you cannot count on every piece of footage being kept automatically; and being able to capture a screenshot does not mean the screenshot material has unlimited commercial licence. Before using game footage and trademarks, you still need to check the applicable authorisation.

A reusable test-record template

Record every adjustment in the table below, and when comparing change only one variable, otherwise the effect cannot be explained:

Field	What to record
Version and region	Client version, the region the account is in, date recorded
Mode	Training Ground / custom / ranked / other
Device	Model, OS version, screen size and refresh rate
Graphics and frame rate	Graphics preset, FPS option, whether frame rate boost is on
HUD and sensitivity	Layout source (own / imported code), sensitivity group values
Weapon	Gun, skin, attachments, stat scheme
Training goal	The specific action you want to verify this session
Network	Network type and approximate latency
Duration	How long you practised
Result	What happened, screenshots, whether it reproduced

This template is editorial advice, not an official performance conclusion. Anyone installing the game for the first time and unsure where to start adjusting can read Beginner training flow and India server basics first to get the order straight before touching settings.

Sources and limitations

Official sources (all global-version patch notes, not India-version testing):

• Global patch 1332: higher sensitivity cap, vehicle HUD
• Global patch 1456: settings groups and unit-by-unit adjustment
• Global patch 1357: CS first person, Armory and Gunsmith
• OB49: HUD share codes and button customisation
• OB50: firing range skill cooldown and shooting sensitivity panel
• OB52: HUD recommended page, sync option, frame rate boost, capture features
• OB54: BR review tools and spectator camera

Still unverified:

• The current India-version sensitivity cap, settings group names and hierarchy: not tested.
• Any specific sensitivity value, DPI, button size or transparency: deliberately not given, because no cross-device universal value exists.
• Whether a given device model can enable the frame rate boost, and how many frames it can reach: no test data.
• Whether the India version has the HUD recommended page, capture features and review tools: not verified.
• The real author identity behind share-code presets: has to be based on the client record.
• The commercial licensing scope of screenshots: no explicit authorisation statement obtained.

Evidence level: Unverified — Every interface and preset description on this page needs confirming item by item in the India client; definitions of evidence levels are in Research method and evidence levels.