Gbets app download — what actually installs on which device

Is there a Gbets app, and where do you get it

Yes. There are two builds: an Android app at version 1.0.0, 5.23 MB, requiring Android 7.0 or higher, distributed through the Google Play Store and as a direct APK from the Gbets website; and an iOS app at version 1.5, released 24 August 2023, 7.2 MB, requiring iOS 13.0 on iPhone, iPadOS 13.0 on iPad, iOS 13.0 on iPod touch or visionOS 1.0 on Apple Vision, distributed through the Apple App Store with a link from the Gbets site. There is no separately documented Huawei AppGallery build — on a Huawei phone without Google Mobile Services you are installing the same Android APK by hand. Treat the file size with some caution: four different review sites publish four different Android figures (5.23 MB, 8.5 MB, 14.17 MB and "around 3 MB"), and none of them is the operator's own number, so use the size as a rough sanity check on your download rather than a signature.

Requirements by platform

Both rows are compiled from third-party review sites, not from an operator specification sheet. Where two sources gave different numbers, the disagreement is printed in the last column rather than hidden — the Android minimum OS and the Android file size are the two cells you should not treat as settled. RAM requirements are not published by any source, so there is no RAM row here.

Data checked: 2026-09-02

How to install the Gbets APK on Android

Sideloading has one real cost: you take over the job the store normally does of checking the publisher. That means the download URL and the developer name are the two things you verify, not the icon.

1. Open the Gbets website in Chrome on the phone itself and use the download link there — the APK is only trustworthy from the operator's own domain.
2. Check your Android version first: Settings → About phone → Android version. The app is listed as needing Android 7.0 or higher.
3. Free up space for a small download: the published size is 5.23 MB, though other sites report figures between about 3 MB and 14.17 MB.
4. Allow the browser to install packages: Settings → Apps → Chrome → Install unknown apps → turn on "Allow from this source".
5. Tap the downloaded file in the notification shade, or open Files → Downloads and tap the .apk.
6. Read the permission prompts before accepting. Gbets does not publish a permission list, so decline anything unrelated to betting — contacts, SMS, call logs and microphone have no role in placing a bet.
7. Turn "Install unknown apps" back off for Chrome once the install finishes.
8. Open the app and confirm it loads a Gbets login screen. A Play Store app also called "GBets" (package com.nettle.vale.game.wtn, developer GOODBOOKS LIMITED, 1.98 MB) is a symbol-matching puzzle game and is not the bookmaker.
9. Re-download from the same page when you want to update: an APK installed outside the Play Store does not receive automatic updates.

APK versions and permissions in detail →

Installing on iPhone and iPad

1. Open the App Store and search for Gbets, or follow the App Store link published on the Gbets site.
2. Check the listing shows version 1.5, dated 24 August 2023, and a 7.2 MB download before you tap Get.
3. Confirm your device runs iOS 13.0 or newer (iPadOS 13.0 on iPad, visionOS 1.0 on Apple Vision) — one source puts the floor at iOS 14, so on iOS 13 expect the possibility that the listing refuses to install.
4. Tap Get and authorise with Face ID, Touch ID or your Apple ID password.
5. Sign in with your existing Gbets account details — installing the app does not create an account.
6. Use Safari instead if the App Store listing is unavailable in your region: open the Gbets site, tap Share, then "Add to Home Screen" for a full-screen shortcut.
7. Note the difference: a Home Screen shortcut is the website in a frame. It gets no App Store update cycle and no native push notification channel.

Installing on a Huawei device

This matters more in South Africa than in most markets: Huawei handsets shipped without Google Mobile Services are common on the second-hand market, and for those users the direct APK is the only route, not a shortcut.

1. Check whether your Huawei has the Google Play Store installed. If it does, install exactly as any other Android phone and skip the rest.
2. Search AppGallery for Gbets if you have no Play Store. No AppGallery listing for the Gbets betting app is documented in any source we could verify, so expect the search to return nothing relevant.
3. Open the Gbets website in the browser on the device and use the direct APK download instead.
4. Allow external installs: Settings → Security → More settings → Install apps from external sources, then enable it for your browser.
5. Install the APK and confirm the device is on Android 7.0 or higher — HarmonyOS builds report an underlying Android version in Settings → About phone.
6. Avoid APK mirror sites surfaced by Petal Search. A mirrored APK is repackaged by a third party and its signature is no longer the operator's.
7. Re-check the Gbets site manually for updates, since neither AppGallery nor Play Store will push them to you.

Data-free access: what is and is not confirmed

No zero-rated or data-free version of the Gbets app is documented in any source we were able to verify. If you see that claim elsewhere, ask which network it applies to and on which domain, because that is how the arrangement actually works: the operator pays a South African network — MTN, Vodacom, Telkom or Cell C — to stop billing data for traffic to specific hostnames. It is a per-domain commercial deal, not a setting inside an app.

Two practical consequences follow. First, a data-free arrangement usually covers the betting site only, and stops at anything loaded from elsewhere — live video streams, embedded provider game clients, chat widgets and ad networks all sit on other domains and are billed normally. Second, data-free access never covers the download itself: pulling a 5.23 MB Android APK or a 7.2 MB iOS package comes off your bundle either way.

Do not read the app's small size as a substitute for data-free. A 5.23 MB install is cheap once; live odds refreshing every few seconds over a session is what consumes the bundle. If your data is tight, the browser on a Home Screen shortcut behaves no worse than the app, and you can cap it with your phone's data saver.

App versus mobile browser

Depositing and withdrawing inside the app

The app uses the same cashier as the website, in ZAR, with the same South African banking rails behind it — Capitec, FNB, Standard Bank, Absa and Nedbank. The method list, minimums, clearing times and any fees are set out on the payments page rather than repeated here, because those numbers change independently of the app version. If a deposit clears but the balance does not refresh in the app, close and reopen it before contacting support — the cashier and the app balance are separate calls.

Account-level problems are not app problems: for a locked account or a failed sign-in see login, and for the FICA and verification documents that gate a first withdrawal see registration and KYC.

Payment methods, limits and clearing times →

Common problems and what actually fixes them

The app installs but will not open. Check the OS floor first. Android is listed at 7.0 or higher, and one source narrows the supported band to Android 5.0–13, which means very new Android builds are also outside what has been tested. On iPhone the floor is iOS 13.0 by two sources and iOS 14 by a third. If your OS is below the floor, no amount of reinstalling helps — use the browser instead. If the OS is fine, clear the app's cache (Settings → Apps → Gbets → Storage → Clear cache), which resets a corrupted local session without deleting the install.

The app never updates. This is expected behaviour for a sideloaded APK. A package installed from a file, not from Google Play, has no update channel: you have to visit the Gbets site again and install the newer APK over the old one. Installing over the top keeps your data; uninstalling first does not lose your account, only the local session. If you want automatic updates, install the Play Store build instead and remove the sideloaded copy first, since the two signatures may conflict.

Login fails in the app but works in the browser. That pattern usually points at a stale cached session or a saved password that no longer matches, not at a blocked account. Clear the cache, retype the password manually rather than autofilling, and check your phone's date and time are set to automatic — a clock that is out by minutes breaks one-time-password and token validation. If the failure repeats across both app and browser, it is an account issue, and the login page covers lockouts and resets. Before you install anything from a link sent to you in a chat group, read legit or scam: repackaged betting APKs circulated on Telegram and WhatsApp are the most common way South African bettors lose account credentials.