Logitech G Hub vs Onboard Memory

Logitech G HUB profiles run two different ways depending on the hardware: through the software while it’s open, or from a chip built into the mouse or keyboard itself. If your device has onboard memory, save your working profile to it and you’ll keep your DPI stages, button mapping and most lighting effects even on a PC that has never installed G HUB. If your device doesn’t have onboard memory, every setting depends on G HUB running in the background, full stop.

The short version: onboard memory is for people who move between computers, LAN events, or dual-boot setups and don’t want to reinstall software everywhere. G HUB-only mode is for people who stay on one machine and want automatic per-game profile switching, which onboard memory can’t replicate. Most players end up using both — a baseline profile stored on the device as a fallback, with G HUB layering extra features on top when it’s running.

Quick answer

If you only need one thing to work reliably everywhere, write it to onboard memory. If you want dynamic behavior — profiles that change automatically per game, lighting that reacts to audio, macros triggered by in-game events — you need G HUB running. The table below breaks down what carries over.

What onboard memory actually stores

Onboard memory is a small flash chip inside the mouse or keyboard, separate from the main controller. When you click “save to device” (or the equivalent action) in G HUB, the software writes a compact version of your active profile to that chip: DPI stage values, polling rate on some models, button assignments, and lighting settings that don’t require live software input. The device reads from that chip every time it powers on, whether or not G HUB is installed on the host PC.

Not every Logitech device has this chip. Budget wired mice and basic keyboards often skip onboard memory entirely to hit a lower price point, which means every setting you configure in G HUB only applies while the software is running and connected. Check the device page inside G HUB — if there’s no “save to device” or profile-storage option visible, your hardware doesn’t have the chip and everything depends on the software layer.

Devices that do include onboard memory usually cap the number of profiles they can hold locally, often somewhere between one and five depending on the model’s flash size. G HUB will tell you the exact limit when you try to save a profile to the device; if you hit the ceiling you’ll need to overwrite an existing slot rather than add a new one.

One thing that trips people up: writing to onboard memory is a manual action, not automatic. If you tweak your DPI in G HUB and don’t explicitly push that change to the device, the mouse keeps running whatever was last saved to the chip, and the software’s live view can look out of sync with reality on a second PC until you resync it.

The flash chips used for onboard memory are rated for a large but finite number of write cycles, similar to any small flash storage. In practice this ceiling is high enough that normal profile-tweaking over years of ownership won’t approach it, but it’s worth knowing this is physical storage with wear characteristics, not an infinitely rewritable software setting — another reason to finalize a profile in G HUB before pushing it to the device rather than saving to onboard memory after every minor adjustment.

Some higher-end mice split onboard storage into a dedicated lighting profile slot and a separate performance profile slot, which can be saved and overwritten independently. Check whether your specific model treats these as one combined write or two separate ones — it affects how many total distinct configurations you can realistically keep active on the device at once.

Why some settings don’t transfer

Lighting effects that need constant recalculation — audio visualizers, effects synced to a game’s health bar or ammo count through Logitech’s game integration — are generated by G HUB itself, frame by frame, and streamed to the device over USB. There’s no way to compress “react to whatever happens in this specific game” into a static profile a tiny onboard chip can execute on its own, so those effects simply fall back to whatever static color or off-state was last saved when G HUB isn’t present.

Automatic profile switching works the same way. G HUB watches which process has focus and swaps the active profile behind the scenes. Onboard memory has no concept of “which window is focused” — it just plays back one fixed profile until you manually load a different one, which on most devices means using a physical profile-switch button if the hardware has one, or reconnecting to a PC with G HUB to change it in software.

Macros are a partial case. Simple macros (a fixed key sequence, no conditional logic, no delays tied to real-time input) generally do get written to onboard memory on devices that support macro storage. Macros with complex timing logic or ones that call external software functions won’t survive the trip and revert to their unmapped button behavior on a G HUB-free machine.

The practical tradeoff is worth stating plainly: onboard memory trades dynamic, context-aware behavior for portability and independence from any specific PC. If your workflow genuinely relies on the software layer — swapping between a shooter profile and a strategy-game profile automatically, or lighting that pulses with your Discord notification sound — accept that onboard memory is a fallback state, not a full replacement, and plan your PC setup around G HUB actually being installed and running most of the time.

Setting up a profile for onboard memory

Start in G HUB with the device you want to configure selected in the left-hand device list. Build out your DPI stages, button assignments, and any static lighting the way you normally would, and confirm it behaves correctly while G HUB is running and connected — that’s your baseline before you try to make it work standalone.

Once the profile behaves the way you want, look for the option to save or apply it to the device’s memory rather than just the software profile list. This is where the setting actually gets written to the onboard chip. Give the write process a few seconds; interrupting it by unplugging the device mid-write can corrupt the stored profile and force you to reconfigure from scratch.

Test it properly by disconnecting the mouse or keyboard, plugging it into a different machine — ideally one without G HUB installed — and checking that DPI, buttons, and static lighting match what you configured. If something doesn’t carry over, it’s one of the software-dependent features described above, not a bug in the transfer.

A common mistake is testing onboard memory on the same PC you configured it on, immediately after saving, without ever fully closing G HUB. In that scenario the software is still technically influencing behavior in the background, so the test doesn’t actually prove the profile works independently. Close G HUB completely, or better yet test on a second machine, before trusting that a profile is genuinely self-contained.

Onboard memory for LAN events and multiple PCs

If you compete or travel with your own peripherals, onboard memory removes the dependency on installing and configuring software on a machine you don’t control. Tournament organizers and internet cafes rarely allow arbitrary software installs, so a mouse that plays back your sensitivity and button layout straight from its own memory is the only realistic way to keep consistent muscle memory across venues.

The tradeoff is that you lose live adjustment. If your usual DPI feels off on an unfamiliar mousepad or a different desk height, you can’t nudge it without either carrying a laptop with G HUB or using any physical DPI-cycle button the device has, which steps through preset stages rather than letting you dial in an exact number.

For people who switch between a desktop and a laptop at home, the calculation is different — both machines are yours, so installing G HUB on both isn’t a hardship, and you get automatic profile switching on both. Onboard memory becomes more of a safety net than a primary workflow in that case.

Before a tournament or LAN, it’s worth building a dedicated “travel profile” specifically for onboard memory rather than reusing whatever your home desk profile happens to be. Strip out any macros or lighting effects you know rely on G HUB, set DPI to a single stage rather than several you’d normally cycle through with software shortcuts, and confirm the whole thing works standalone at home first — discovering a gap in venue conditions, under time pressure, is the worst time to find out a feature didn’t transfer.

Battery and wireless considerations

On wireless Logitech mice, saving a profile to onboard memory doesn’t meaningfully change battery life — the chip is read once on power-up and the device isn’t constantly rewriting it. What does affect battery life is the polling rate and lighting effects you’ve saved as the default, since a high polling rate and always-on RGB draw more power regardless of whether G HUB is running.

If you’re setting up a profile specifically for travel or onboard-memory use, it’s worth dropping to a lower polling rate and turning lighting to static or off in that particular profile, then keeping a separate higher-performance profile for desk use where the mouse is plugged in or on a charging dock. G HUB lets you maintain multiple named profiles even though only one can live in onboard memory at a time.

As a rough point of reference, dropping from 1000Hz polling with full RGB to 500Hz polling with lighting off commonly extends runtime by a noticeable margin on a wireless mouse, though the exact figure depends heavily on the specific battery capacity and sensor used — check your mouse’s own rated battery life at different polling rates in its official specifications rather than assuming a fixed percentage across models.

When this comparison doesn’t apply

None of this matters if your device doesn’t have an onboard memory chip — check the device page in G HUB first, because plenty of budget and mid-range models simply don’t include one, and the entire onboard-vs-software debate is moot for them. In that case the software running (or not) is the only variable that matters.

It also doesn’t apply cleanly to keyboards and mice used primarily for productivity rather than gaming, where the value of per-game automatic profile switching is low anyway. If you never touch a second PC and never attend a LAN, the practical benefit of onboard memory shrinks to “backup in case G HUB crashes,” which is real but minor.

Corporate or locked-down PCs that block driver installation are the other edge case — onboard memory is often the only way to get custom DPI or remaps working at all on a machine where you can’t install G HUB, assuming IT policy allows the device to enumerate as a HID peripheral in the first place.

It’s also worth noting that a firmware update to your mouse or keyboard is applied through G HUB and can, in some cases, reset onboard memory profiles as part of the update process. If you rely heavily on a specific onboard profile, check the release notes before applying a firmware update, and be ready to reconfigure and re-save the profile afterward if the update touches onboard storage.

Troubleshooting

Symptom: DPI resets to default on a second PC. Cause: the profile was configured in G HUB but never explicitly written to onboard memory, so only the software-side profile exists. Fix: reconnect to the original PC, open G HUB, and use the save/apply-to-device action before disconnecting again.

Symptom: Lighting is static or off on a PC without G HUB, even though it looked dynamic before. Cause: the effect was a software-driven effect (audio reactive, game-integrated) that can’t be stored on the chip. Fix: set a static or breathing color as the saved profile specifically for onboard use, and accept that dynamic effects only work with G HUB running.

Symptom: Macros don’t fire on a second PC. Cause: either the device doesn’t support macro storage in onboard memory, or the macro used conditional logic that only G HUB’s software engine can execute. Fix: check the device’s spec page for macro-storage support; if it’s supported, re-save a simplified version of the macro without conditional branches.

Symptom: Onboard memory profile seems “stuck” on old settings even after changes in G HUB. Cause: changes made in the software aren’t pushed to the device automatically. Fix: repeat the save/apply-to-device step every time you want the onboard copy to match your current software profile.

Symptom: Profile write fails or the device stops responding mid-save. Cause: the device was disconnected or went to sleep during the write process. Fix: keep the device connected and awake (move the mouse periodically) throughout the save, and retry from a fresh G HUB session if it fails again.

Symptom: A device that previously worked fine with onboard memory now shows blank or default behavior after a firmware update. Cause: the update process reset onboard storage as part of applying new firmware. Fix: reconfigure your profile in G HUB and re-save it to the device; check Logitech’s release notes for that update to confirm whether this is expected behavior for your model.

Frequently asked questions

Does Logitech G HUB need to run in the background for onboard memory to work?

No. Once a profile is written to onboard memory, the mouse or keyboard plays it back from its own chip. You can close G HUB, uninstall it, or plug the device into a machine that has never seen the software, and the stored profile still runs.

Why does my RGB lighting change when I unplug my Logitech mouse from a PC without G HUB?

Some lighting effects, like ones synced to in-game events or system audio, are generated live by G HUB and can’t be baked into onboard memory. Static colors, breathing, and color cycle effects usually do transfer; reactive effects tied to software input do not.

How many profiles can I store on a Logitech device’s onboard memory?

It depends on the model and how much onboard flash it has. Entry-level mice with no onboard memory chip can’t store any profile locally. Higher-end models typically hold a handful of profiles, and G HUB’s device page tells you the exact number for your unit.

Will switching to onboard memory disable per-app profile switching?

Yes, partially. Automatic profile switching based on which game or app is in focus is a G HUB software feature. Onboard memory only stores the profile you last wrote to the chip, so you lose automatic switching until G HUB is running again.

Can I edit a profile that’s stored in onboard memory without G HUB installed?

No. Editing DPI stages, button assignments, or macros always requires G HUB (or Logitech’s older software) to write a new profile to the chip. Onboard memory is playback-only storage, not an editable in-device menu.

Sofia Lindqvist tests peripherals on a bench built around a high-speed camera rig for latency measurement and a switch-force gauge, and the onboard-memory behavior described above was checked by swapping devices between multiple PCs with and without G HUB installed. If you’re deciding which mouse to buy in the first place, our guide to how to choose a gaming mouse covers which sensor and shape questions actually matter, and mouse DPI and polling rate explained goes deeper into the settings you’ll be saving to that onboard chip. If your mouse is wireless, pair this with wired vs wireless gaming peripherals to see how battery life factors into your profile choices, and check our picks for the best wireless gaming mouse if onboard memory support is a deciding factor in your next purchase.