How to Upload Wardrive Data to WiGLE from Flipper Zero (Marauder v1.14.0, 2026)

PINGEQUA Lab · Flipper Zero wardriving · 7 min read · Updated 2026-08-03

If you've been pulling the SD card out of your Flipper Zero's ESP32-C5 board to hand-upload a WigleWifi CSV at wigle.net, that workflow just got shorter. Marauder v1.14.0 lets the device send wardrive data to WiGLE directly, and this guide covers how to use it — including what to do when the upload fails.

What changed in Marauder v1.14.0

Marauder v1.14.0 shipped on 2026-07-22, and it's the first release where the firmware can push a wardrive session directly to WiGLE's servers and to WDGWars, a gamified wardriving leaderboard at wdgwars.pl, without you ever touching the SD card. The release notes specifically call out that the ESP32-C5 DevKit gained this direct-upload capability, alongside a new FindMy Live backend and a Mini v3 flasher for updating the board itself.

A follow-up release, v1.14.1, landed on 2026-08-01. It's worth knowing what it isn't: the changelog scopes it to "authoritative stable installer manifests" — flasher/installer plumbing, not new upload functionality or bug fixes to the WiGLE flow. If you're chasing an upload fix, updating to v1.14.1 alone won't necessarily get you one; see the honest note below.

Before v1.14.0, the only supported path was: collect a wardrive session to the SD card in WigleWifi CSV format, pull the card (or copy the file off it), then log into wigle.net in a browser and upload the CSV by hand. That path still works and is still useful as a fallback — more on that in the next section.

Two ways to get wardrive data into WiGLE

Both paths start the same way — you drive or walk around with GPS lock and the wardrive scan running — they only diverge at the point where the collected data actually reaches WiGLE's servers.

In practice, the SD-export route is still the more reliable one if your board is running an older Marauder build, if you're somewhere without a trustworthy Wi-Fi network to join, or if the direct upload throws an error mid-session (see the fixes below). It's also a good habit to keep as a backup even after you switch to direct upload — the CSV on the SD card is your copy of the data regardless of whether the network upload succeeds.

Step-by-step: uploading directly from the device

The general flow for the new direct-upload path looks like this. Exact menu wording can vary a little between firmware builds, so treat the menu labels below as a description of the flow rather than a literal transcript — check your own device's on-screen menu for the exact text.

• Update to Marauder v1.14.0 or newer. Direct WiGLE/WDGWars upload doesn't exist on earlier builds. If you need a refresher on the flashing process, see our Marauder firmware install guide.
• Have a WiGLE account ready. You'll need an account at wigle.net, and depending on how your firmware build authenticates, you may be asked for an API token generated from your WiGLE account page rather than your plain login — have both on hand before you start.
• Connect the device to Wi-Fi. From the device's Wi-Fi/AP configuration menu, join a 2.4 GHz network with a working internet connection. The upload step needs the board itself online, not just your phone.
• Run (or load) a wardrive session. GPS needs open sky and typically takes roughly 30 seconds to two minutes to get a cold-start fix — it won't lock indoors or under heavy cover, so start the session outdoors.
• Open the wardrive/upload menu and select the WiGLE (or WDGWars) upload option. This is the step that sends the session to WiGLE's servers directly from the board — no SD card removal, no computer.
• Wait for a confirmation. If you instead see an error or the device reboots, jump to the fixes section below.

On the compliance side, all of this only involves passively logging publicly broadcast SSID, BSSID, and GPS data as you move — you're not connecting into networks, authenticating against them, or cracking anything. WiGLE's own FAQ is explicit that this kind of passive, publicly-broadcast data is what belongs in an upload, and separately warns against bulk-importing or scraping data through unofficial tooling — stick to normal, one-session-at-a-time wardriving and you're on the right side of that line.

Fixing "upload failed" / "could not connect"

There's no single confirmed root cause yet, but a few checks clear up the most common reports:

• Confirm the network actually has internet access. A device can successfully join a Wi-Fi network and still fail to reach WiGLE's servers if that network is behind a captive portal, has client isolation, or has no real internet uplink.
• Re-enter your WiGLE credentials or API token. A typo or an expired token will produce a connection-style error that looks identical to a network problem.
• Check your firmware version. You need v1.14.0 at minimum; check the Marauder GitHub releases page for anything newer than v1.14.1 that might land a fix, since v1.14.1 itself didn't address this.
• If the device reboots mid-upload, don't assume the data is gone. Re-check the SD card — Marauder wardrive sessions are still written there, so the SD-export + wigle.net path from the table above is your fallback while the direct-upload bug gets sorted out.
• Keep the SD card itself within spec. Marauder's own FAQ requires 32 GB or smaller, formatted FAT32 — a card outside that spec can cause write/read failures that look like an upload problem but are actually storage problems.
• If it's still broken, the GitHub thread is the place to check. Issue #1409 is where the maintainer and other affected users are tracking this; it's worth a read before assuming your hardware is at fault.

FAQ

Sources & further reading (verified 2026-08-03): Marauder v1.14.0 release notes · Marauder v1.14.1 release notes · GitHub issue #1409 — WiGLE/WDGWars upload failures · Marauder official FAQ (SD card requirements) · Marauder wardrive wiki (GPS behavior) · WiGLE FAQ · WiGLE Android app releases.

For authorized security testing and education only. Test only networks and devices you own or have explicit written permission to test. You are responsible for compliance with all applicable laws and radio regulations (e.g. FCC Part 15 in the US). "Flipper Zero" and "ESP32 Marauder" are referenced for compatibility and comparison; PINGEQUA is independent and not affiliated with or endorsed by their respective owners.