PUBG MOBILE Still Lagging on M1 or M2 iPad? Best Graphics Settings, Repair Steps, and Bug Report Checklist
PUBG MOBILE released a July 26, 2026 patch for severe FPS drops on M1 iPad Pro models, but some players continued reporting performance problems on M1, M2, and iPad Air 5 devices. The announced fix should not be represented as an official M2 repair. This device-first guide separates low FPS from network lag, provides conservative and competitive graphics profiles, explains thermal and storage checks, organizes resource repair and reinstallation, and gives players a standardized report format when problems remain.
PUBG MOBILE released a patch on July 26, 2026, aimed at severe FPS drops on iPad Pro models using Apple's M1 chip. After the patch, some players reported improvement, while others continued describing lag on M1 devices. Players using M2 iPads and iPad Air 5 also discussed similar symptoms. Those later reports matter, but they do not expand the official patch scope by themselves. The announced July 26 target was M1 iPad Pro performance.
A useful troubleshooting process must separate device generation, rendering performance, heat, storage, resource integrity, and network response. The word lag is too broad. One player may have low frame rate, another may have high ping, and another may have smooth performance until the device becomes hot.
This guide begins with symptom classification and then provides device-specific settings, repair steps, and a report template. It is designed for players who already installed the July 26 update but still experience poor play.

Classify the Problem Before Changing Settings
Symptom | Likely category | First check |
|---|---|---|
Camera and interface become choppy | FPS or frame pacing | Graphics load, temperature, background recording |
Enemies teleport while camera stays smooth | Network latency | Ping, Wi-Fi stability, server route |
Performance worsens after 10-20 minutes | Thermal throttling | Device temperature, case, charging state |
Stutter appears after entering a new map area | Resource or shader loading | Download completion, storage, official repair |
Game closes without warning | Memory, resource, or client crash | Free storage, restart, repair, crash context |
Touch response feels delayed at stable FPS | Input or display latency | frame-rate setting, recording, touch conditions |
Audio continues during visual stalls | Rendering stall | frame pacing, graphics profile, temperature |
Do not solve a network problem by lowering textures, and do not solve a frame-rate problem by repeatedly changing DNS settings.
Confirm the Exact Device
Open Settings, General, About and record the model name and model number. Determine whether the device is:
iPad Pro with M1.
iPad Pro with M2.
iPad Air 5 with M1.
Another iPad generation.
The M1 iPad Pro and iPad Air 5 can share the same chip while using different thermal designs, displays, memory configurations, and device profiles. A solution that works on one should be tested rather than assumed on the other.
The M2 iPad is not automatically covered by an M1-specific patch. When reporting an M2 problem, identify it accurately.
Start With a Clean Post-Patch State
Close PUBG MOBILE from the app switcher.
Check the App Store for the current client.
Launch and finish all required in-game resources.
Restart the iPad.
Keep at least several gigabytes of free storage beyond the game installation.
Disable screen recording, livestreaming, picture-in-picture video, and large downloads.
Begin the test with the device at a normal temperature.
Record the graphics page before changing anything.
Do not use a session that remained suspended from before July 26 as the first test.
Recommended Competitive Baseline
For players who prioritize stable combat, begin conservatively:
Graphics quality: Smooth or the lowest visually acceptable preset.
Frame rate: the highest option the device can maintain consistently.
Anti-aliasing: off during diagnosis, then test later.
Auto-adjust graphics: off for controlled comparison.
Shadows: off or low when available.
Death replay and highlight recording: off during testing.
Resource quality: standard before testing optional high-resolution packages.
Brightness and color style: personal visibility preference; these should not be confused with performance repair.
The highest selectable frame-rate option is not always the best everyday setting. A stable lower target can provide more predictable recoil and touch response than a target that repeatedly collapses.
M1 iPad Pro Profile
Because the July 26 patch directly addressed M1 iPad Pro drops, test the old preferred profile first. If severe drops remain, use this sequence:
Smooth graphics with the intended high frame-rate option.
Recording features disabled.
One complete Training Ground session.
Two matches on the same map.
A warm-device test after at least 15 minutes.
Higher visual quality introduced one setting at a time.
If Smooth remains unstable, lower the frame-rate target temporarily and compare frame pacing. This shows whether the device cannot sustain the target or whether a severe bug remains independent of load.
M2 iPad Pro Profile
M2 players should not assume that the July 26 M1 fix changed their client path. Begin with a clean baseline:
Smooth graphics.
Stable high frame-rate selection.
Recording off.
Anti-aliasing off for the first comparison.
Same map and route for three attempts.
Temperature and charging state recorded.
If the problem appears only at one frame-rate option, capture that difference. If all options stutter in the same place, resource or client behavior may be more relevant than raw GPU load.
iPad Air 5 Profile
iPad Air 5 uses M1 but is not the same product as M1 iPad Pro. It may have different sustained thermal behavior and display limits.
Use:
Smooth graphics.
A frame-rate option supported and stable on the device.
No heat-trapping case during diagnosis.
No charging during the first thermal comparison.
Short and long tests separated.
Do not compare an iPad Air 5 directly with a ProMotion iPad Pro without accounting for display and device differences.
Graphics Settings Ladder
Change settings in this order:
Level 1: Stability
Smooth graphics, conservative frame rate, recording off, anti-aliasing off, complete resources, cool device.
Level 2: Competitive Responsiveness
Increase frame rate while keeping Smooth graphics. Test touch response, recoil, scopes, smoke, and vehicles.
Level 3: Visual Clarity
Add anti-aliasing or a higher graphics preset one option at a time. Keep the last stable result.
Level 4: Convenience Features
Enable highlights, death replay, or recording only after ordinary matches remain stable.
This ladder prevents a player from testing five expensive features together and then guessing which one caused the drop.
Heat Management
Apple silicon iPads can deliver strong burst performance, but sustained gaming still produces heat.
Improve thermal conditions by:
Removing a thick case during testing.
Avoiding direct sunlight.
Keeping the rear surface exposed to air.
Not placing the device on fabric that traps heat.
Using a stand that does not block the chassis.
Lowering screen brightness when comfortable.
Avoiding simultaneous fast charging during the first comparison.
Taking a break after a temperature warning.
Do not use ice packs or condensation-producing cooling methods. Moisture can damage the device.
A cooling fan can change results, so record whether it was used. Compare fan and no-fan runs separately.
Storage and Download Checks
PUBG MOBILE contains large optional map, audio, event, and texture resources. Incomplete or damaged resources can create stutter during asset loading.
Check:
Available iPad storage.
Whether the tested map finished downloading.
Whether high-resolution resources are installed.
Whether an update is paused.
Whether iCloud or another application is performing heavy background work.
Free storage before reinstalling. The operating system needs room for temporary files as well as the game.
Use the Official Repair Function
A safe repair order is:
Preserve account login and recovery information.
Record the current client version and settings.
Use the game's official routine repair.
Restart and test one complete map.
Use a more comprehensive resource repair only if the first step fails.
Redownload the affected map.
Reinstall the full application only after repair fails.
Do not delete account data or recovery details. Confirm that the account is properly linked before a full reinstall.
Network Diagnosis
Use a stable Wi-Fi connection and compare another trusted network when possible.
Check:
Ping during the problem.
Packet-loss or reconnect messages.
Whether other devices are downloading.
Distance from the router.
Interference on the wireless band.
Whether a VPN or unusual route is active.
Whether the camera remains smooth while enemies update late.
Restarting the router may help a local connection issue, but it will not repair local low FPS.
Touch and Input Checks
If the image looks smooth but aiming feels delayed:
Clean and dry the screen.
Disable unnecessary accessibility gestures during testing.
Check whether a screen protector has damaged or wet areas.
Compare frame generation or display options only if the game offers them.
Disable recording overlays.
Test without charging interference.
Recreate the control layout only after backing it up.
Do not reset the entire control scheme as the first action. A layout reset can introduce a new problem unrelated to performance.
Test Scenarios That Reveal Problems
Use more than one situation:
Training Ground
Camera rotation, sustained fire, scopes, vehicles, and repeatability.
Hot Drop
High player count, rapid asset loading, sound, effects, and close combat.
Smoke Test
Multiple smoke effects can reveal rendering pressure.
Vehicle Test
Fast traversal exposes streaming and frame pacing.
Late Circle
Dense combat and longer-session heat appear together.
Record which scenario fails. The phrase every match lags is less useful than the frame rate collapses after three smoke grenades during a warm-device late circle.
Bug Report Checklist
Field | Information to provide |
|---|---|
Device | Exact model, model number, chip, storage capacity |
System | iPadOS version and free storage |
Game | Client version, region, player identifier |
Settings | Graphics, FPS, anti-aliasing, recording, resource quality |
Scenario | Map, mode, location, match time, actions |
Device state | Battery, charging, temperature, case, cooling fan |
Network | Wi-Fi type, ping, connection warnings |
Result | low FPS, stutter, crash, touch delay, audio behavior |
Frequency | Number of failures across repeated attempts |
Evidence | Video, screenshots, timestamps, repair steps tried |
If the report concerns M2 or iPad Air 5, state that clearly. Do not label it as the M1 iPad Pro bug without evidence.
What Not to Do
Do not use unauthorized configuration tools.
Do not install performance booster applications that request suspicious permissions.
Do not repeatedly reinstall before collecting evidence.
Do not test while several variables change.
Do not publish login credentials.
Do not assume every comment describes the same device.
Do not claim an official M2 fix when the notice names M1 iPad Pro.
Do not spend money expecting UC or cosmetics to improve performance.
Performance and Purchase Decisions
A device problem should be resolved independently from account purchases. UC, outfits, weapon finishes, and passes do not raise frame rate.
Players who have already decided to purchase UC can use Topuplist and the PUBG MOBILE top-up page. Verify the region, player identifier, product amount, and payment details before completing an order.
FAQ
Did the July 26 patch fix M2 iPads?
The announced patch targeted M1 iPad Pro models. M2 player reports do not prove an official M2 fix.
Why is an iPad Air 5 different from an M1 iPad Pro?
They can share the M1 chip but have different displays, thermal behavior, memory configurations, and device profiles.
What settings should I try first?
Begin with Smooth graphics, a stable frame-rate option, recording off, anti-aliasing off, and complete map resources.
Should Auto-adjust Graphics be enabled?
Disable it during controlled comparisons. Re-enable it later if it improves normal play.
Why does lag begin after the iPad becomes hot?
Sustained heat can reduce performance. Compare a cold start with a warm-device test and improve airflow.
Can low storage cause stutter?
It can affect updates, temporary files, and asset caching. Keep meaningful free space.
Should I use the repair function or reinstall?
Use official repair first. Reinstall only after update, restart, resource, and repair checks fail.
How do I separate high ping from low FPS?
Low FPS makes local camera and interface movement choppy. High ping delays server actions while local rendering may remain smooth.
What evidence is most useful?
Exact device, full settings, device temperature state, map and location, repeated frequency, and a video showing the trigger.
Where can I top up PUBG MOBILE?
Visit Topuplist and the PUBG MOBILE top-up page. Verify the player identifier and region before payment.
Final Device Rule
Identify the exact iPad, classify the symptom, create a conservative baseline, and test temperature, storage, resources, and network separately. The July 26 patch addressed M1 iPad Pro FPS drops; it should not be presented as an automatic M2 or iPad Air 5 repair.
When a problem remains, submit a standardized report instead of changing every setting at once. Repeatable evidence gives developers a better chance to isolate the device-specific cause.

