Skip to content

Best Free Fire HUD Settings & Import Codes (2026)

Free Fire HUD settings and import codes for 2-, 3- and 4-finger layouts in OB55: the exact menu path, the button changes that actually matter, community share codes with vote counts, and what really breaks a code after a major update.

Gamermir Editor
Published Nov 13, 2026Updated Nov 19, 2026

Free Fire runs on Unity, and on a phone the HUD is not decoration. It decides how many things you can do in the same second, and most lost fights come down to fire, aim and a Gloo Wall competing for one thumb. This guide covers the OB55 menu paths, the HUD settings worth changing, the 2-, 3- and 4-finger import codes that are currently circulating, and the honest limits of those codes: what expires, what breaks, and what was never true in the first place.

Quick Settings Cheat Sheet

DecisionStart HereWhy

Base layout

HUD 1, then edit it

Big fire button bottom right, second fire button top left, minimap top left. The least retraining for most players.

Finger count

2 on phones under 6 inches, 3 on mainstream phones, 4 on tablets

More fingers means more simultaneous actions, but also more strain and more mistaps on a small screen.

Fire button size

78% as a baseline

The in-game editor shipped with the right fire button at 78% on a sample account. Push it higher only if you drag upward for headshots.

Fire button opacity

Keep it near 100%

You need to find it without looking down. Fading the fire button is a net loss.

Left Fire Button

Always

The other setting only shows the top-left fire button while scoped, which quietly breaks any 3-finger layout.

Rarely used buttons

Lower opacity, do not shrink them

You still need to hit them; you just do not need to read them.

Sensitivity on import

HUD only, first time

You are testing a layout, not adopting a stranger's aim settings.

Code format

22 characters starting with #FFHUDT

Anything shorter, or any string without that prefix, is not an in-game share code.

How the HUD Fits Your Device Tier

Free Fire is a Unity title built with IL2CPP and shipped only on Android, iOS and iPadOS. There is no DX11, DX12 or desktop graphics menu to argue about here: every option you tune lives inside the mobile client. That makes the device tier the first decision, not the last.

TierOfficial reference specHUD approach

Low

Android 4.4, dual-core 1.2 GHz, 1 GB RAM, 1.5 GB storage; iOS 9, iPhone 5s, 1 GB RAM

2 fingers. Fewer buttons, larger targets, fade everything you rarely press.

Mid

Android 7, octa-core 1.8 GHz, 3 GB RAM, 3 GB+ storage; iOS 11+, iPhone 7, 3 GB RAM

3 fingers. Full HUD with crouch and Gloo Wall on the left index.

High

Anything above the recommended spec, including tablets

4 fingers. Both index fingers take fire and scope, thumbs stay on movement and camera.

The two rows above are the official minimum and recommended requirements, not performance benchmarks. What they tell you is how much headroom your phone has for a crowded HUD. A 1 GB device running a four-finger layout with thirty visible buttons is fighting the hardware and the screen at the same time.

Where the HUD Menu Lives in OB55

The entrance moved, and most older guides still point at the old one. Since OB50, HUD settings sit under Settings > In-Match > HUD. The Recommendation System, which lets you browse layouts shared by other players, arrived in OB52 inside that same HUD screen.

The share-code tool moved with it. From OB52 onward it sits in the bottom-left corner of the HUD Recommendation System page; the bottom-right position used in OB51 is obsolete. Tutorials that send you to Settings > Controls > Custom HUD > Import are describing a path from before that reshuffle. Some builds still keep an Import button inside Custom HUD, so if you cannot find the newer entry, check there before assuming your version is broken.

OB55 has been the live build since the 10 September 2026 patch, and no OB56 date has been announced. Every path in this guide is written against OB55. If your client is older, expect the menu to look different, not the concepts.

Importing a HUD Code Step by Step

  1. Open Settings > In-Match > HUD.
  2. Enter the HUD Recommendation System and open the shared-layout list, labelled MORE HUD.
  3. Tap Use Share Code at the bottom-left of that page.
  4. Paste the full code, starting with #FFHUDT, with no spaces. It should be 22 characters.
  5. When asked about sensitivity, choose HUD only for your first test.
  6. Apply, then load into Training to check button reach before you queue for ranked.

If the field rejects the code, the problem is almost always the string, not your account. A "code" that asks you to download an APK, install a helper app or visit another page to unlock it is not a HUD share code. The official feature needs nothing installed. Garena neither publishes nor verifies community codes, so treat every list, including the one below, as a starting point rather than a guarantee.

Best HUD Settings to Change First

Work down this table in order. Each change is reversible, and none of them require touching game files.

SettingRecommended ValueWhy

HUD preset

HUD 1 for most players; HUD 4 if you want the minimap right

HUD 1 keeps the main fire button bottom right, a second one top left and the minimap top left. HUD 4 moves the minimap top right and the weapon panel to the bottom centre.

Right fire button size

78% baseline, higher for drag shots

The stock editor sample used 78% size at full opacity. A bigger button helps upward drags but eats screen space over the play area.

Right fire button opacity

100%

The button you press most should be the one you never have to hunt for.

Left Fire Button

Always

The alternative only reveals the top-left fire button while scoped, which removes your left-index trigger mid-fight.

Left index assignment

Fire and crouch, or Gloo Wall

Pick one job per finger. A left index that shoots and also drops walls will do neither cleanly.

Gloo Wall button

Under the index finger that is not shooting

Walls go down under pressure; the button has to be reachable without moving a thumb off the stick.

Scope button

Right index on 4-finger, right thumb on 2- and 3-finger

Keep scope and fire on separate fingers once you have the fingers for it.

Secondary fire button

Keep visible at reduced opacity

Useful for peeking, harmless if it is faint.

Minimap

Top-left on HUD 1, top-right on HUD 4

Match the preset you picked and keep it clear of your aim area.

Weapon panel

Bottom centre

Central switching costs less thumb travel than a corner panel.

Button nudging

Four arrows, one or two taps at a time

Small increments beat redoing the whole layout; you cannot judge a 40-pixel move in one go.

Smart Adjust

On, then review the suggestions

Added in OB53, it proposes adjustments based on your tap data and HUD usage. It suggests, it does not decide.

Sensitivity Included

Off on the first import

You are evaluating button placement, not inheriting someone else's six sensitivity values.

Unused buttons

Lower opacity to taste

Fading removes visual noise without removing function.

The single most common mistake is shrinking a button you actually use to make room for one you do not. Fade it instead, and spend the freed space on a larger fire button or a wider Gloo Wall target.

What 2, 3 and 4 Fingers Actually Change

A two-finger layout puts movement, aiming and shooting in your thumbs. It is the fastest to learn and the least tiring, which is why it still suits small phones and casual play. Nothing about it is a compromise on accuracy; it is a compromise on how many actions can happen at once.

Three fingers add one left index, usually for the fire button, crouch or a Gloo Wall, while the right thumb stays on aim and camera. Community players describe it as most of the claw advantage without the hand pain, and it is the sensible landing spot for a mainstream phone. Give it three to five days in Training before you judge it.

Four fingers split fire, scope and utility across both index fingers and leave both thumbs for movement and camera. That is what makes jump-shots possible: jump with one index, aim with a thumb, fire with the other index. On a phone under 6 inches the grip cramps your hands and produces mistaps, so the layout only pays off on a tablet or a large-screen phone.

One more data point worth having: a breakdown of ten FFWS players put six on three fingers, three on four fingers and one on six. The claim that every pro runs four fingers is a popular line, not a measured one; the more accurate statement is that four fingers dominates among players who have moved to claw grips at all.

HUD Import Codes by Finger Count

These are community-list layouts, ranked by the votes they carry on the list they were compiled from on 19 November 2026. Votes reflect one site's audience, not global usage, and none of these codes could be tested against a live OB55 client for this guide. Verify in Training before you commit.

Community HUD share codes, OB55 era

SetupCodeVotesBest for

2-finger

#FFHUDT6O3jDTj2NZPo7eM

1645

Most-voted two-finger layout: large fire button, easy first step

2-finger

#FFHUDT6O3j8fkQ4FPo7eO

380

Updated for the newer HUD buttons, same grip you already use

2-finger

#FFHUDT6O3jAfOU1JPo7eO

186

Small phones, buttons kept low on the screen

2-finger

#FFHUDT6O3jr1C60xPo7eO

126

Headshot drags, fire button placed higher

3-finger

#FFHUDT6O3jEmm9vhPo7eP

992

Most-voted three-finger layout, all-purpose claw

3-finger

#FFHUDT6O3j8SCTkxPo7eM

389

Index finger fires, right thumb only aims and steers the camera

3-finger

#FFHUDT6O3j5MO8u9Po7eO

329

Moving up from two fingers, left index on fire

3-finger

#FFHUDT6O3jRoP1WVPo7eN

n/a

Mid and long range: rifle fights and peeking

4-finger

#FFHUDT6O3jDdnzOhPo7eM

1682

Most-voted four-finger layout

4-finger

#FFHUDT6O3jo9PUcZPo7eO

662

Gloo Wall under the right index, close-range builds

4-finger

#FFHUDT6O3jHo5vXRPo7eP

317

Tablets and ranked play, scope and fire split between indexes

Read the vote column as a popularity signal only. A layout can be the most-liked entry on a community list and still fight your hand size, your screen ratio or your grip. The only test that matters is whether your thumb reaches the fire button without shifting your palm.

Custom Opacity, Size and Smart Adjust

Tap any button in the editor to select it. You get an Opacity slider, a Size slider and four arrows for nudging position. The right fire button on a sample account sat at 100% opacity and 78% size, which is a reasonable baseline rather than a rule.

Move in small steps. Two or three arrow taps, then a Training run; a layout that looks right in the editor often feels wrong when your thumb is already moving. Since OB53, Smart Adjust watches your tap data and HUD usage and suggests changes, which is genuinely useful when you cannot tell why a button keeps getting missed. Treat it as a second opinion.

If a 3-finger layout feels broken the moment you scope, the cause is usually Left Fire Button set to the scoped-only option. Set it to Always.

Sensitivity Included and What to Sync

A shared code can carry six sensitivity values: General, Red Dot, 2x Scope, 4x Scope, Sniper Scope and Free Camera. One popular shared HUD carried General 92, Red Dot 135, 2x 150, 4x 110, Sniper 21 and Free Camera 150. Those are the creator's numbers, not recommendations, and they were tuned for a different screen, grip and finger count.

Sync sensitivity only when you are deliberately copying a player whose setup matches yours. Otherwise import the HUD alone, keep your own sensitivity, and change one value at a time in Training. Mixing a stranger's HUD with a stranger's sensitivity makes it impossible to tell which change broke your aim.

Do HUD Codes Still Expire?

Time-based expiry was removed in OB50, effective 30 July 2025, so a share code no longer dies simply because it is old. Structural compatibility is a separate issue: a major OB update can change internal button structures, and codes built on the old arrangement can report invalid.

SymptomWhat to do

Code rejected straight away

Re-copy it. The string must be 22 characters and start with #FFHUDT.

Looks like the right length but fails

Check positions 8 to 11. They read 6O3j or 7O3j with a capital letter O, not a zero.

Still fails after a fix

Try the next code in the same finger count. Do not jump to a 4-finger code to make a 3-finger layout work.

Worked last season, dead now

A major update likely changed the button structure. Rebuild from the closest surviving code.

Region is the other persistent myth. Garena does not label share codes by server, and a video titled for the India server usually just means the creator plays there. The same string imports for everyone. Free Fire India launched as a separate app on 28 October 2026 and shares an account with Free Fire MAX, but whether HUD codes travel between the two has not been confirmed, so export your own layout inside FFI rather than assuming a code will cross.

Codes do work across Free Fire and Free Fire MAX, and PC emulators such as BlueStacks and GameLoop can import them. A phone layout still feels wrong with a mouse and keyboard, because none of the reach assumptions hold.

Testing a Layout Before Ranked

  1. Import the layout and go straight to Training, not a match.
  2. Run the same drill for ten minutes: peek, scope, fire, wall. Note which button you miss.
  3. Fix one button at a time with the arrows or the size slider, then repeat the drill.
  4. Give a new finger count three to five days before deciding. Early discomfort is normal; pain is not.
  5. Only then take it into ranked, and keep your old layout saved as a fallback.

FAQ

Do Free Fire HUD codes expire?

Not by time. Expiry was removed in OB50 on 30 July 2025. Codes can still break after a major OB update if the internal button structure changes, which is why an old code may report invalid even though it is not "expired".

Are HUD codes different for each server?

No. Garena does not label share codes by server, and a code advertised for the India server is just one its creator used there. The same 22-character string imports on any server.

Can I use a 4-finger code on a small phone?

You can import it, but the grip cramps your hands and causes mistaps on screens under 6 inches. Start with a 2-finger layout on a small phone and move to 3 fingers on a mainstream handset.

Do I need to download an app to use a HUD code?

No. HUD sharing is a built-in game feature. Anything that asks you to install an APK or third-party tool to unlock a code is not an official share code, and third-party HUD generators are neither published nor checked by Garena.

More games to download