How to beta test a drone
To beta test a drone well, fly legally and safely first, then repeat the same short flights, record the conditions every time (wind, temperature, battery, GPS) and back every fault with a timestamped photo or clip. BetaSuite: Tester's Toolkit (betasuite.app) is an iPhone, iPad and Android app built for this: it burns the date and time into every photo and video and turns your sessions into a report for the manufacturer. The checklist below works with any tool and covers consumer drones and self-flying cameras, and there is a free 12-step protocol to import.
Fly legally and safely first
Follow your local aviation rules, and never test unsafely. Drone rules differ by country and change over time, and following them is your responsibility, not the manufacturer's or this guide's. Check your national aviation authority before you fly, for example CASA in Australia or the FAA in the US (links checked 2 October 2026). Beta firmware doesn't change the rules. This guide is not legal advice.
- Know the rules where you are. That means registration or licensing, where and how high you may fly, no-fly zones and airspace, flying near people, and rules about filming. This page doesn't summarise them on purpose, because they differ and change.
- Choose a big, open site. No people, vehicles or animals nearby, and away from airports, roads, crowds and power lines.
- Keep your eyes on the aircraft. If you want video of a test, ask a helper to film, or use the drone's own footage, rather than looking down at your phone.
- Stay inside the manual's limits. Don't fly in wind, rain, cold or low light the manual says to avoid, just to force a test.
- Test small and land early. Change one thing per flight, keep each test short, and land at the first sign that something is wrong. Don't test failsafes, range limits or obstacle avoidance in any way the manufacturer's brief doesn't describe.
- Look after the batteries. Follow the manual for charging and storage, and stop using a battery that is swollen, damaged or unusually hot.
- Respect privacy. Don't film people who haven't agreed to it, or private property you have no right to film, and check the rules on filming.
- Follow the stricter rule. If your beta agreement or the manufacturer's safety instructions are stricter than the law, follow them.
What to test in a drone beta
A drone beta is mostly about what happens when something goes wrong, so be methodical and keep each test small. Start in the safest order: pre-flight checks and GPS first, then a low hover, then the features one at a time. Repeat anything that fails so you can say how often it fails. This covers consumer drones and self-flying cameras.
| Area | What you are checking | Evidence worth capturing |
|---|---|---|
| Pre-flight and set-up | Activation, firmware checks, calibration prompts, propeller and battery checks, and how clear the app's warnings are. Time taken and how many retries. | Screenshots of the pre-flight screen and photos of the aircraft before flight. |
| GPS lock and positioning | Time to a GPS lock, satellite count or signal bars, compass calibration prompts, home-point accuracy and how steadily it holds position. | A screenshot of the lock status, and a photo of the landing spot against the take-off spot. |
| Hover and handling | A stable hover, smooth control response, drift in wind, and how it behaves in each flight mode. | A clip, or a screenshot of the flight log, with the time visible. |
| Return-to-home and failsafes | Return-to-home from the app, the controller and on low battery: height, route, landing accuracy, and whether you can cancel it or take over. Only the checks the manufacturer tells you to do. | A clip of the return filmed by a helper, and the app's status log. |
| Obstacle avoidance | Whether it detects the test target, brakes or goes around it, in each direction it claims to cover, and whether it stops for things that aren't there. Only as the brief describes, with a safe target. | A clip filmed by a helper, plus the app's warnings with the time visible. |
| Tracking and follow modes | How closely it keeps its subject, how it copes with the subject turning, passing behind something or being lost, and whether it keeps a safe distance. | The drone's own footage, and a helper's clip of the subject. |
| Video and photo quality | Sharpness, exposure, colour, shake or gimbal drift, flicker or banding, dropped frames and focus hunting. Compare modes and resolutions. | A frame grab of the worst moment and a note of the mode and settings. |
| Link range and dropouts | Control and video-feed quality as distance grows (gradually, in sight and within the legal limit), interference, and what the warnings tell you. | Screenshots of the signal indicators and a note of the distance when warnings began. |
| Battery and temperature | Flight time against the claim, how accurate the battery percentage and the flight-time-left figure are, the low-battery warnings, temperature after landing and charging time. | Notes of the percentage at take-off and landing, the weather, and a photo of the battery screen. |
| App and controller | Pairing, time to connect, crashes or freezes, flight-log accuracy, settings that don't stick, and how the app behaves when a call or a notification arrives. | A screen recording, or a screenshot of any error with the time visible. |
| Firmware updates | Update time and failures, whether the aircraft, controller and app stay in step, and whether settings, the home point and saved media survive. | Before and after screenshots of the version numbers. |
| Noise and wear | Noise at a normal distance, vibration, propeller and motor wear, gimbal play and heat after several flights. | Dated notes, plus close photos of the wear points. |
Conditions to record every time
A fault you can't reproduce is just a story. Log the same details every time so engineers can line your problem up against everyone else's.
| Record | Why it matters |
|---|---|
| Date, time and time zone | Engineers can match your report to the drone's own flight logs, if the manufacturer collects them. |
| Site and airspace | A general description of where you flew: open ground or near buildings, trees or water. GPS, link and obstacle behaviour change a lot between them. Note that you checked the local rules for the site. |
| Weather | Wind speed and gusts, temperature, rain, fog, sun angle and cloud. Wind and cold change flight time, stability and the camera picture. |
| GPS and compass | Satellite count or signal level at take-off, any compass prompt, and whether the home point was set before take-off. |
| Aircraft and battery | Battery percentage at take-off and landing, battery temperature if shown, the number of charge cycles, propeller condition and anything fitted (guards, filters, accessories). |
| Flight mode and settings | Flight mode, speed limits, return-to-home height, the obstacle-avoidance setting, camera resolution and frame rate, and any custom settings. |
| Software | Aircraft, controller and app firmware versions. Note them again after every update. |
| Changes | Anything different since the last flight: a new battery, new propellers, a firmware update, a different site. |
BetaSuite adds the date and time to every photo and video for you, and can add GPS, live weather, the season and the time zone, each of which you can turn on or off in Settings.
A first-week routine
Adjust this to your brief. The point is to do the same checks in the same order, so a change in the result means something changed in the drone.
| When | Focus |
|---|---|
| Day 1 | Unbox, charge and update. Photograph the aircraft and note the firmware. Do the pre-flight checks, then a short, low hover in an open area where you may fly, with your eyes on the aircraft. |
| Days 2–3 | Short flights to check GPS lock, hover and the first return-to-home in good weather. Land with plenty of battery to spare. |
| Days 4–5 | One feature at a time: obstacle avoidance, tracking, camera modes. Build distance gradually, within the rules and in sight, to check the link. |
| Days 6–7 | A normal outing, the way you would really use it. Log every warning, dropout and error, then review the footage. |
| First windy or cold day | Only if it is within the manual's limits and still safe to fly. Note battery behaviour and stability. Don't fly outside the limits to force a test. |
| Every week | Repeat the same short flight and the same photos. After any firmware update, repeat the pre-flight, GPS, hover and return-to-home checks. |
A pass/fail checklist for a drone
Agree your thresholds with the manufacturer's brief first. If it doesn't give any, write your own before you start (for example, "lands within 2 m of the home point") so you aren't judging after the fact.
- Passes its pre-flight checks and shows no unexplained warnings.
- Gets a GPS lock and sets the home point within the time the manual gives.
- Holds a steady hover without drifting or wobbling beyond your threshold.
- Returns to home and lands at or near the home point, and lets you cancel it or take control, if the manufacturer asks you to check this.
- Detects the test obstacle and stops or goes around it, without false stops, if the brief covers it.
- Keeps tracking its subject in follow modes, or tells you clearly when it loses it.
- Records video and photos without dropped frames, flicker or gimbal faults.
- Keeps a stable control link and video feed at the distances you flew, with a clear warning if the signal weakens.
- Flight time and battery estimates match what happens, with a warning early enough to land safely.
- Battery and aircraft aren't unusually hot after landing.
- Pairs with the app and keeps its connection for the whole flight, without crashes or freezes.
- Installs a firmware update without a failure and without losing settings or saved media.
A fail isn't a verdict on the drone. It's a finding. Write it up with the conditions and a clip.
If a safety system fails in the air, land as soon as it is safe to, and tell the programme before you fly again.
How to capture evidence engineers can use
- Fly first, film second. Your eyes belong on the aircraft. Ask a helper to film, or review the drone's own footage and the app's flight log after you land.
- Film the whole event, not just the fault. From a safe place: ten seconds before, the fault itself, and ten seconds after.
- Capture the app's warnings. Warnings and signal indicators can vanish in seconds. Screenshot the flight log and the warning list straight after you land, with the time visible. If the drone's app runs on your phone, dual recording in BetaSuite can record the phone's screen and its rear camera into one video. Start it before take-off, and test it on the ground first, because some apps may block screen recording. The small camera window floats over the flight app, so drag it clear of the controls and warnings.
- Start wide, then close. First the aircraft and the site, then the detail: the propellers, the gimbal, the battery, the error on the app.
- Use a reference. A bright mat or a cone at the home point shows how close it landed. A tape measure beside a mark shows its size.
- Burn the time into the picture. A stamp that is part of the image travels with the file. File metadata is often stripped when a photo is shared or compressed. BetaSuite stamps every photo and video, with optional GPS, weather, season and time zone. A stamped clip is also easier to line up with the drone's own flight log. More on that in the timestamp camera app guide.
- Catch the intermittent faults. With Instant Capture, BetaSuite keeps a rolling buffer and saves the last 15–30 seconds when you tap, so a helper who keeps the camera on the drone can save the moment after it happens, without ending up with one long clip of the whole flight.
- Mark it as it happens. A helper can add a one-tap marker or a quick voice note with the time, or you can add one straight after landing, then write it up properly later.
- One issue per clip. Name it by what happened ("Landed short of the home point, tree line"), not "Video 14".
- Keep the drone's own footage and flight logs. Save them for each flight, named by date and time, so the manufacturer can match them to your report.
What to send the manufacturer
A good report is short at the top, specific in the middle and backed up at the bottom. See how to write a beta test report for the full structure.
| Section | What goes in it |
|---|---|
| At a glance | Aircraft model and serial number, firmware versions (aircraft, controller and app), test dates, and where you flew in general terms. Three sentences on how it went. |
| Findings, worst first | Safety issues first (loss of control, failsafe or battery problems), then anything that stops the drone working, then annoyances. For each one: what happened, what you expected, how to repeat it, how often it happens and the conditions. |
| Evidence | Time-stamped photos and clips, plus the drone's own footage and screenshots of the app's flight log, matched to each finding by name or time. |
| What worked | A short list. Engineers also need to know what not to change. |
| Data files | A CSV or JSON of your findings if they ask, so they can load it into their own tools. BetaSuite reports can ship with both. If they want the drone's own flight logs, send those from the manufacturer's app, because BetaSuite doesn't read them. |
Here is the format for one finding. The values are made up, to show the shape.
Title: Return-to-home lands about 15 m short of the home point Severity: High (it did not land where expected) Expected: Returns to the home point and lands within 2 m Actual: Descended about 15 m short, with a "GPS signal weak" warning Frequency: 2 of the last 4 returns, both near the tree line Conditions: 9 km/h wind, 18°C, 14 satellites at take-off, firmware 1.4.2, battery 38% Evidence: Helper's wide clip, then a screenshot of the warning, stamped 10:12:31
Want to see a finished report? Open the sample report (PDF). It has an At a Glance summary, findings sorted by severity and an image appendix.
Running it in BetaSuite
- Create a project for the drone, and note the model, serial number and firmware (aircraft, controller and app) in your first session.
- Import the free protocol below.
- Start a session each flight day. Capture the photos and clips the steps ask for (ask a helper for anything that has to be filmed in the air), and drop a marker whenever something happens.
- At the end of the week, generate a PDF or Word report with an At a Glance summary and findings by severity, plus JSON and CSV data files if you want them.
AI summaries are optional and opt-in. For units under NDA, Confidential Mode blocks cloud AI and cloud uploads, and warns you before you share or export anything. Everything is stored on your device, with no account.
Free BetaSuite protocol: drone field test
This is a ready-made, 12-step protocol for the first week with a consumer drone or self-flying camera. It was built with the site's own Protocol Builder, so the link below is a real import link. Its first step asks you to confirm you may fly where you are. It mixes pass/fail checks with choice, multiple-choice and rating questions, and asks for a photo or video where the evidence matters. For the general idea, see the test protocol template.
Drone field test · 12 steps · free to import and edit
- Pre-flight: on every test day, in an open area where you are allowed to fly and away from people, check the drone, propellers, battery and firmware as the manual describes, and confirm the local rules and airspace for the site. The app shows no errors. Photo: the drone and its controller, ready to fly. Screenshot: the app's pre-flight screen.
- GPS lock and calibration: the drone gets a GPS lock and completes its compass and sensor checks within the time the manual gives, with no error. Screenshot: the app showing the lock, with the satellite count or signal bars visible.
- Take-off and hover: it takes off, holds a steady hover at a low height and lands without drifting, wobbling or an error.
- Return-to-home: in an open area, trigger return-to-home the way the manual describes. It climbs to its set height, flies back and lands at or near the home point, and you can cancel it or take control at any time. Have a helper film, and keep your own eyes on the aircraft.
- Obstacle avoidance: only as the manufacturer's brief describes, in an open area, at low speed and with you ready to take over, it detects a light, soft test target and stops, brakes or goes around it. Have a helper film.
- Tracking and follow modes: how well did it follow its subject in an open, safe area?
- Video quality: in normal daylight, how good is the footage from the drone's camera? 1 = unusable, 5 = excellent. Note any shake, flicker, banding, dropped frames or focus hunting. Screenshot: the worst frame in the app.
- Link range and dropouts: increasing the distance gradually, within the legal limit and while you can still see the drone, how was the link?
- Battery and temperature: the battery percentage and flight time left match what really happened, the low-battery warning comes early enough to land safely, and the drone and battery are not unusually hot after landing. Screenshot: the battery screen after landing.
- Firmware update: updating the drone, controller and app finishes without a failure, and your settings, home point and saved footage are intact afterwards.
- Which problems did you see? Tick all that apply.
- How confident would you be flying this drone on an important shoot? 1 = not at all, 5 = completely.
Show the raw code
How to import it
- On your phone, tap Open this protocol. If BetaSuite is installed, it opens its import sheet with the code filled in. If the link opens in your browser instead, tap Copy code there (or here).
- In BetaSuite, open Test protocols, choose Import and paste the code or link.
- Edit any step to suit your unit, then run it. Your answers are saved to a session and roll up into the report. Protocols, sessions and reports are part of Advanced mode; if you're in Basic mode, Test protocols offers to switch for you.
Want to change the steps first? Open the link in the free Protocol Builder. It runs in your browser with no account, and you can generate a fresh code from your edits. Running a whole beta programme? See how to give every tester the same protocol and merge the results.
When BetaSuite is the wrong choice
BetaSuite covers everything from a single stamped photo to a full report for the manufacturer. It is the wrong tool only when:
- You need data from the drone itself. BetaSuite doesn't connect to the drone, so it can't read its flight logs, telemetry or what its camera recorded. You note what the app shows, or screenshot it, and send the manufacturer's own logs separately if they ask.
- You would be piloting and filming at once. Flying safely needs your eyes and attention on the aircraft. Use a helper, or review the drone's own footage afterwards.
- You need airspace or legal advice. BetaSuite is not a flight planner, an airspace checker or a legal tool. Use your aviation authority's own information.
- You need lab numbers. A phone can't measure flight time, wind tolerance or video quality to a standard. Use repeatable flights to compare your own runs, not to certify anything.
- You want to test an app, not hardware. BetaSuite is not a TestFlight or Google Play testing tool. See what a hardware beta testing app needs to do.
Don't need a report? If the manufacturer takes findings through its own portal or form, or you only want stamped photos and video, switch BetaSuite to Basic mode (Settings > App mode). It keeps every capture tool, including dual recording and Instant Capture, and leaves out projects, sessions and reports, so it works as a plain timestamp camera. Attach the files wherever the manufacturer asks, and switch back to Advanced at any time without losing anything.
If you run the programme rather than test in it, see the programme page. For the longer case for the app, see why BetaSuite.
Frequently asked questions
- What is a drone beta test?
- A pre-release or early-access trial where a manufacturer lets real pilots fly an unfinished drone, firmware or app and report faults before general release. The tester's job is to find problems in real conditions, safely and within the law, and describe them so engineers can reproduce them.
- Does beta firmware change the drone rules I have to follow?
- No. Beta firmware does not change aviation rules, so the usual rules for where you are still apply, and so does your beta agreement. Check your national aviation authority, for example CASA in Australia or the FAA in the US, before you fly. This page is not legal advice.
- How long should a drone beta test run?
- As long as the programme asks. As a guide, run it long enough to see calm and windy days, at least one firmware update and several battery cycles. For most testers that means several weeks of short flights rather than a few long ones.
- How do I film a drone test safely?
- Fly first and film second. Keep your eyes on the aircraft, and ask a helper to film, or review the drone's own footage and the app's flight log after you land. Don't operate your phone's camera yourself while you are piloting.
- What should I record when a drone loses its link or returns home unexpectedly?
- Land safely first. Then note the time, the place in general terms, the wind and battery level, what the app warned you about and roughly how far away the drone was. Screenshot the app's warnings and flight log, and send the manufacturer's own flight log if they ask.
- Can I use BetaSuite for a drone under NDA?
- Yes. Everything is stored on your device with no account. Confidential Mode blocks cloud AI and cloud uploads, and warns you before you share or export anything. Photos and videos also go to your camera roll by default, so if your photo library syncs to the cloud, turn Camera Roll off in Settings → Save Destinations before you turn Confidential Mode on. Check your NDA first for what you may photograph and what you may send, and by what route.
- Is BetaSuite a TestFlight alternative?
- No. BetaSuite: Tester's Toolkit is not an app-beta tool and has no connection to TestFlight or Google Play testing tracks. It is for people who beta test physical products in the field and need timestamped evidence and a report for the manufacturer.
- Is BetaSuite a subscription?
- No. It is a one-time purchase from the App Store or Google Play, with no subscription, no ads and no account. Each store sets the price.
Related guides
Start testing with timestamped evidence
BetaSuite: Tester's Toolkit burns the date and time into every photo and video, then turns your sessions, markers and findings into a PDF or Word report, on iPhone, iPad and Android. Only need a timestamp camera? Use Basic mode.
One-off purchase · No subscription · No ads · No tracking · Yours for life