What is a security camera beta test?

A pre-release or early-access trial where a manufacturer lets real owners run an unfinished camera, doorbell, firmware or app at home and report faults before general release. The tester's job is to find problems in real conditions and describe them so engineers can reproduce them.

How do I measure how long a camera alert takes?

Record the real-world event and your phone's screen together, for example with BetaSuite's dual recording, while a helper walks up to the camera or presses the doorbell. The gap between the event and the notification banner on that one timeline is the delay. Repeat it several times on Wi-Fi and on mobile data, because one run proves little.

Is it OK to test a camera that can see my neighbours or the street?

Keep it on your own property as far as you can, use privacy zones to mask what you can't avoid, and check the rules where you live, especially for audio. This isn't legal advice. Check your beta agreement for what you may share, and leave other people out of the evidence you send unless the manufacturer needs them.

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.

How to beta test a security camera or video doorbell

To beta test a home security camera or video doorbell well, run the same short checks each week (a repeatable detection walk-through, a night check and an alert-delay test), tally the false alerts and back every fault with a timestamped clip. BetaSuite: Tester's Toolkit (betasuite.app) is an iPhone, iPad and Android app built for this: its dual recording captures your phone's screen and the real-world event in one video, so the clip itself shows how long the alert took, and it burns the date and time into every photo and video. The checklist below works with any tool, and there is a free 12-step protocol to import.

Updated 2 October 2026 · Written by Goodfield Studio, the maker of BetaSuite

What to test in a security camera beta

Start with set-up and the alert path, because everything else depends on them. If the camera drops off your Wi-Fi or the alerts arrive late, later results are hard to trust. Then work through the rest, and repeat anything that fails so you can say how often it happens.

Area	What you are checking	Evidence worth capturing
Set-up and mounting	Time to pair, whether it connects on your Wi-Fi (or by cable, if your model uses one), and whether the field of view matches what you expected from the preview. Does it survive a router restart or an update?	Photos of the mounting position, and a screenshot of the live view at set-up.
Detection accuracy	Whether it spots people, vehicles, pets and parcels where it should, and labels them correctly. Use the repeatable test below.	A tally sheet and screen recordings of the alert list.
False alerts	Alerts for shadows, moving branches, rain, insects, headlights, reflections and traffic outside the area you care about. How many in a day, and at what times?	A screenshot of the alert list with the times, and the clips behind the worst ones.
Night vision	Clarity and range after dark, glare from the infrared lights off a nearby wall, window or the doorbell's own housing, and any colour night mode.	A night frame with a person at your real distances, from the app, and a photo of the scene.
Notification delay	Time from the real-world event to the alert on your phone, and from tapping the alert to live video. For a video doorbell, include the button press. Use the delay test below.	A dual recording of the event and your phone's screen together.
Live view and playback	How fast live view starts from a cold app, whether clips include the lead-up, whether the time on a clip is right and how smooth playback is.	A screen recording of opening live view and of playing a clip.
Two-way audio	Clarity both ways, delay, echo and cut-outs. Test with a helper at the door or in the garden.	A short clip of a call, with the helper at the camera.
Storage and cloud	Where clips are saved (card, hub or cloud), how long they are kept, whether you can export them, and what happens when storage is full or the internet drops.	Screenshots of the storage settings, and a test export.
Battery and power	For battery or solar models: charge level over a week against the number of events, and behaviour in cold weather. For wired models, any resets or dropouts.	A dated tally of the battery percentage.
Privacy zones and sharing	Whether a privacy zone or privacy mode you set is respected in live view and in recordings, and whether people you share with see only what you allow.	Screenshots of the zone, and of what the shared user sees.
App and connectivity	Pairing, notification settings, offline behaviour, links to other smart-home apps and firmware updates.	A screen recording, plus a screenshot of any error with the time visible.

Privacy first. A camera records people who never agreed to be filmed, so keep the test on your own property as far as you can. Point it away from neighbours' windows, gardens and shared space, use privacy zones to mask what you can't avoid, and ask a helper before you film them. Rules about video, and especially audio, recording differ between countries and states, and this guide isn't legal advice, so check yours and check what your beta agreement lets you show. Keep clips of neighbours, passers-by and children out of the evidence you share unless the manufacturer specifically needs them.

A repeatable detection test

"It detected me" can't be compared from one week to the next. This test can, so you can tell whether a firmware update or a sensitivity setting helped. It is a relative test on your own property, not a lab result.

Mark two or three distances from the camera on the ground (near, middle and far across the area you care about) and write them down.
Ask a helper to walk across the view, and then straight towards the camera, at each distance. Do ten passes per distance at a steady walking pace.
Keep the sensitivity, zones and schedule fixed for the whole test, and write them down.
After each pass, note whether an alert came and what it said (person, vehicle, pet, parcel or just "motion"). An alert that said "motion" when you wanted "person" is a separate result, not a hit.
Do the same for a car passing on your own drive or street, for your pet if you have one, and for a parcel left at the door.
Work out the result for each distance: detection rate = passes with the right alert ÷ passes × 100.
Repeat after dark, and again after every firmware or settings change. Log the result in the same row each time.

An alert-delay test

How long an alert takes to reach you matters more than almost any other spec, and it is hard to judge by eye. This test uses dual recording, so the clip itself is the proof and there are no two clocks to line up.

Use the phone and the connection you normally have, with the camera app's notifications on. Write down whether it is on home Wi-Fi or mobile data.
Start a dual recording in BetaSuite. It records your phone's screen and the rear camera into one video, with the date and time stamped in.
Ask a helper to walk up to the camera, or press the doorbell, while you film them with the rear camera. If you can, stand where the camera and the helper are both in shot.
Scrub the video. The gap between the moment the helper reaches the camera or presses the button and the moment the notification banner appears on the screen is the alert delay. Then note how long it takes from tapping the alert to live video or the clip playing.
Repeat about ten times, at different times of day and on both Wi-Fi and mobile data. Log the two delays separately each time.
Some camera apps block screen recording of live view or clips. If yours does, keep recording to catch the notification, time the wait for live video by hand and note that the app blocked screen recording.

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 camera's event log and the cloud's, if the manufacturer collects them.
Light	Daylight, dusk, night, street lighting, infrared or colour night mode. Most detection and clarity problems depend on it.
Weather	Rain, snow, fog, wind, heat and frost. Moving branches and rain are classic sources of false alerts, and cold shortens battery life.
Scene and distance	Where the camera is mounted, its height and angle, the distance to the area you care about, and anything that has moved since last time (a new plant, a parked car).
Settings	Sensitivity, activity zones, the detection types switched on, schedule, clip length and video quality.
Network	Wi-Fi signal at the camera, the router, whether your phone was on Wi-Fi or mobile data, and any outage. A weak signal explains many late alerts.
Power	Battery percentage at the start and end of each check, or the power source for wired models.
Software	Camera firmware, app version and your phone's operating system. Note them again after every update.

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 camera.

When	Focus
Day 1	Mount and pair. Photograph the mounting position and screenshot the live view. Note the firmware, the settings and the Wi-Fi signal at the camera. Take baseline photos of the view in daylight and after dark from the same spot.
Days 2–3	Run the detection test in daylight at each distance. Run the first alert-delay tests. Check two-way audio with a helper.
Days 4–5	Run the detection and delay tests after dark. Check night vision at your real distances, and a privacy zone if you use one.
Days 6–7	Leave it on its own and check the alert list each evening. Tally every false alert and every missed event. Check storage and, for battery models, the battery level.
First rain or wind	Note the false alerts it produces in rain, wind or moving branches. Don't spray the camera to force the test.
Every week	Repeat the detection and delay tests with the same settings. After any firmware update, repeat the set-up, detection and alert checks.

A pass/fail checklist for a security camera

Agree your thresholds with the manufacturer's brief first. If it doesn't give any, write your own before you start (for example, "alerts within 10 seconds on Wi-Fi") so you aren't judging after the fact.

Pairs on the first attempt and stays online for the week, including after a router restart.
Starts live view within a few seconds, at home and away from home Wi-Fi.
Detects a person on at least your agreed share of passes at each distance in daylight.
Labels people, vehicles, pets and parcels correctly, for the labels the model offers.
Keeps false alerts under your agreed limit per day, including in rain and wind.
Gives a picture clear enough at night to tell a person from an animal at your real distances.
Delivers alerts within your agreed time, on Wi-Fi and on mobile data.
Saves clips with the lead-up and the correct time, and lets you export them.
Has clear two-way audio without a long delay or echo, if fitted.
Honours privacy zones and sharing settings in live view and in recordings.
Lasts as long as you agreed for your number of events, if it runs on a battery.
Installs a firmware update without losing your settings, zones or shared users.

A fail isn't a verdict on the camera. It's a finding. Write it up with the conditions and a clip.

Know where the footage goes. Before you start, check what the camera records, whether audio is on by default and where clips are stored and sent. Tell the people you live with and anyone who visits. The same goes for a robot vacuum with a camera. If the unit is under NDA, check what you may show.

How to capture evidence engineers can use

Film the whole event, not just the fault. Ten seconds before, the fault itself, and ten seconds after.
Put the alert and the event in one clip. Dual recording in BetaSuite records your phone's screen and the rear camera into a single video, so the moment someone reaches the door and the moment the notification arrives sit on one timeline. The gap between them is your alert delay.
Screenshot the alert list and each clip's details. The labels and times the app shows are part of the evidence.
Use a repeatable subject. The same helper, the same path, the same pace and the same marks on the ground, so a change in the result means something changed in the camera.
Photograph the scene as well as the screen. What the camera should have seen and what the app showed can differ.
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. More on that in the timestamp camera app guide.
Catch the odd moments. When you are beside the camera or doorbell and something misbehaves, Instant Capture in BetaSuite keeps a rolling buffer and saves the last 15–30 seconds when you tap. Without a tool like that, start recording before each test you run.
Mark it as it happens. Add a one-tap marker or a quick voice note with the time, then write it up properly later.
Keep other people out of it. Crop or leave out clips that show neighbours, passers-by or children before you share anything, unless the manufacturer asks for them.
One issue per clip. Name it by what happened ("Late alert, front door, dusk"), not "Video 14".

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	Model and serial number, firmware and app versions, mounting position, power and network set-up, and your settings. Three sentences on how it went.
Findings, worst first	Privacy or security issues first (a zone that is ignored, footage visible to the wrong person), then anything that stops alerts or recording, 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 matched to each finding by name or time, with other people left out where you can.
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.

Here is the format for one finding. The values are made up, to show the shape.

Title:      Person alert arrives about 40 seconds after the visitor
Severity:   High (the delay defeats the point of the alert)
Expected:   Notification within a few seconds
Actual:     Banner appeared about 40 seconds after the visitor reached the door
Frequency:  6 of 10 tests, all with the phone on mobile data
Conditions: Dusk, 9°C, one bar of Wi-Fi at the camera, firmware 4.2.1
Evidence:   Dual recording stamped 18:31:12, screen and scene in one clip

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 camera, and note the model, serial number and firmware in your first session.
Import the free protocol below.
Start a session each time you test. Capture the photos and clips the steps ask for, 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; on a supported iPhone or iPad, on-device Apple Intelligence can still write summaries. Everything is stored on your device, with no account.

Free BetaSuite protocol: security camera and doorbell test

This is a ready-made, 12-step protocol for the first week with a security camera or video doorbell. It was built with the site's own Protocol Builder, so the link below is a real import link. It mixes pass/fail checks with choice, multiple-choice and rating questions, and asks for a photo or a screen-and-camera recording where the evidence matters, and for a screenshot of what the app shows. The alert-delay step is built around dual recording. For the general idea, see the test protocol template.

Security camera and doorbell test · 12 steps · free to import and edit

Open this protocol

Set-up: mount the camera or doorbell and pair it with its app. It connects on the first attempt, and live view works from your phone on both home Wi-Fi and mobile data. Photo: the camera in place, showing where it is mounted.Pass / FailPhoto required
Person detection in daylight: a helper walks across the view ten times at your middle distance. How many passes gave a correct person alert?Options: 9 or 10 · 7 or 8 · 4 to 6 · 3 or fewerChoice
Vehicles, pets and parcels: a passing car, your pet (if you have one) and a delivered parcel are each labelled correctly, for every label your model offers. Screenshot: the app's alert list showing each one.Pass / Fail
What caused false alerts this week? Tick all that apply.Options: Shadows or moving branches · Rain or snow · Insects at night · Headlights or reflections · Traffic or people outside my area · A pet I wanted ignored · None of theseMultiple choice
Night vision: after dark, the picture is clear enough to tell a person from an animal and describe their clothing at your real distances, without glare from the infrared lights washing out the scene. Screenshot: the night view in the app.Pass / Fail
Alert delay: a helper walks up to the camera or presses the doorbell while you record the event and your phone's screen together. How long until the alert appeared?Options: Under 5 seconds · 5 to 15 seconds · 15 to 30 seconds · Over 30 seconds, or no alertChoiceDual recording required
Live view and clips: tapping the alert opens live video or the clip within a few seconds, the clip includes the lead-up to the event, and the time on it is correct. Record your phone's screen while you tap an alert through to its clip.Pass / FailDual recording required
Two-way audio: if fitted, you can hear a visitor clearly and they can hear you, without a long delay, echo or cut-outs.Pass / Fail
Privacy zones and sharing: a privacy zone you set is respected in live view and in recorded clips, and a person you share the camera with sees only what you allow.Pass / Fail
Storage: clips are saved where you set (card, hub or cloud), play back, can be exported, and old clips are removed as the settings say. A short Wi-Fi drop does not lose an event.Pass / Fail
Battery: for a battery or solar model, how did the battery last?Options: Not a battery model · As long as the maker says for my number of events · Noticeably shorter · Much shorterChoice
How confident would you be relying on this camera to alert you to something that matters? 1 = not at all, 5 = completely.Rating (1–5)

Steps marked required show the tester a Start capture button for that photo, video or dual recording, and the capture is attached to the step's result. Answers roll up into the report: pass rates, ratings and every result grouped by question. A step that asks for a screenshot has no capture button: take it with your phone's own buttons, then import it from your photo library afterwards.

Show the raw code

BSPROTO1:H4sIAAAAAAAAE-VXXa_jthH9KwO9JAHEC8nWp4FgkRQIukCbBrnb5qHYhyE5sohLkypJ23WD_e_FUPb92I_moQXSTd4sSiTPnDlzZvxzgctS7IpvKeH90SQqyuLBOF3siiX45JW3sSiLU7Gry2cru7__XDg8ULEr7kkdg0kXUHiggIBOg_Y-SLIWEsVUlIXh86TcdvU0oGjbahBNNyghm64XdTd2QzfIZhyHoiwCnYrdpixiooUvKu4pieOyg4M_ugRppttNPjxdxLcuaAKYBGeTZjApAi7LHbxOoLxzpFIE7_L-yYSYAFOiw5LKvNeaE8HJ0BnOPjxEmII_wMUfAyyzd8Q7pU8zzP5A8JMR35m87eClsQQaE97BD7NPfvccoXGwWFRUQpz92bg9nGcKxCBNXAMifVeUxQ8UonegKZFKxjveqfFizX5OO0CYyS4U4Iz2IQKq4GPM92TEiRwkc6AImFbMB6M1wzIxoVN0B3_0Zzigu8CCMVKEPZ4IEJQPgVSCZb0eLYX0qiiLv9FslKVYwkLMYyY3KLKRwfAZHIvCUF45ogRfmokfYOajvaOv8jYETcxtoNsRgIGAUM1gkVNH-gbDXkqYfAA6Ubisb6_heE0W_DRRiHdwrwKRi7NPK9e4LF_EFTtYE9Mj1_kS74gJ_mnGBAqPkTRMaCOtG5hFE-FM9PAK3hj1AMiq5Y9xWeyFt37PSYCTica7HeCUKIDG8FDm2xej0pFTGkFZwgDk_HE_Q_KQsjBv5GZFoQN05oCrYDVFFYwkPsgEUNanmYHf0hgI7WMSY5mF7Y8J9pY5zAcyBOOmgExwlkuEM8Z8DH_K76MiRx_y5q5x0ZnVdmWSA_4mU6nJ4uUD7R2XHNmLIlwCZVHx6mNBnmcuDBZEIOWDzm_pRC7l0J9K64sIMSOD5PeUZgqrXK13ezi6ZOyKLYPCZSEOlUX6p8eS5QOVNUvcQcJl4diftviFXLzVtybPiDN-a5bMqHGAMNEZIinvdCyfXhun7FFfQ7OEWjzFn2NZzYMfuQDZJdbSvir6Dn5cg_9YuE8MJVyyMjLeNIebgNjDGAcn5c3ZizNeAI_a-B2YCSaTEulcgaDQwczqwyzU5MOqRnu5Abw8fXPxxyct4Up0znYJpOZMkDom4Y8pZm8K5oTqAv_yjlYviDMG4_bZC569zEgiZQICxYVUIs3asi8yZdxVEnTNWnl1imuh5FNmVvgzmWVPj0Ts4fYC53mtES5Xf2aU98kH3NNuPTKbTMQT6avj3qB9qTDoEuajzGFaf9RflWzSF5CoHsrMkiSgfy4-ZHoZm7f62bmBDp5PxlUXkVIybh8h4uUOvmH7CenaI3TwC2hPEZxPYD37jlulw6C_5R4ULrtsewhyfWRk0Vu8Gl8Jsz-DNqvObt9YjNmquVSUd5PRXFpnf7RZbRxDIHvJPuBWl7tSmfxVaVl6HqI_0Oo72fcO-YL4Cmr4OqNmL7S2hBa-BuUPi6VE7Ixvy-IfR4rcrtaBYAn-sKQ8Evz2O_ZtSMIYv0Nji7JQuHAn4EU-lr-hS7ErhrbdatnUYui3rWio6YWUQyVo6BqlFcp-6It35TP-_s-mgWuo3PMt_WH2RvGU6Jdb5ouRE1tXRVn0_IunuIaV1RVlseWVic4UWDArI3KQpLHSQjZ6Es3QtWJsulrIBjUqHLdyrF8y8tsbSD7Uz8rNpsEJu6kSA3ZSNPV2ELLbjGJst22nqqqf5PCSm_9itLmCOBxtMh9L7P2M2p8jp_DgTxyCDOjUTPyf4Ec0LluV8-eiLF67mCsW0zpZsDcR6utM4nmameyqZ979JuA0GZXnB_KLJR5XotEEhwtnBHkQyXl8DWd0uZPsnQ-keSTLBT4x25Ge6YqorlFWYmrbXjSy3Ypx245imPpREyJhLV9y97ub7T4lu6aqp7YbayF71Yum07UYx7oVVUNVPdRNN_XjS-o-kynxF83rr05TgPY2_RVl0TL4-vlKnZe21bOlv5woPFspOUR37aysyKduoI9o1zHQuP0T4apuJ41SbKu6Fk3fKyGnbSO2umm3_UbJzfge4b-vefc_9dePMzp2bbtBaoTWUyOaaWzEsOk3gmRdd5Jkpfr3-uyvN1N_sgxR6WFolVBbWYlmkFJIOXWipy11alLV2Kv3ZoXPYjr_VLy46XpsqoGHoU40WynFOGxQ6FZPw6jaYWj1y3g_yzn_U-H3Vd-3Y78R2LVSNANuBaq6E53qx3Gqhr6V7w1C_4N_DL_oiN_z0P-4LZ_IzTiuqr6yccAHCkxFzFAOF3DHg6TAbTnHHXOfTkYRSntZ2aJQlMWfj2p-fHzs3cOGZIv1RmwnVYtGDbVA6lvR1EMlq2rot-PmJRW_3j-fRw4DsiLap_Idql6qWopx1INoNgrF0MhKSNr2OPb1VitZvHv77u27fwPCUCWCeBUAAA==

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 camera itself. BetaSuite doesn't connect to the camera, so it can't read its event log, detection scores or firmware state. You note what the app shows, or record the screen.
You need lab numbers. A phone can't give you a certified detection rate or a precise delay. The tests above compare your own runs; they don't certify anything.
You want to watch the camera for days. BetaSuite records the moments you start or save. For a long-term picture, use the camera app's own alert history and screenshot it.
The camera app blocks screen recording. Some camera and doorbell apps stop screen capture of live view or clips. BetaSuite still captures the real-world half and the notification; for the blocked screen, film it with a second phone instead.
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 security camera beta test?: A pre-release or early-access trial where a manufacturer lets real owners run an unfinished camera, doorbell, firmware or app at home and report faults before general release. The tester's job is to find problems in real conditions and describe them so engineers can reproduce them.
How do I measure how long a camera alert takes?: Record the real-world event and your phone's screen together, for example with BetaSuite's dual recording, while a helper walks up to the camera or presses the doorbell. The gap between the event and the notification banner on that one timeline is the delay. Repeat it several times on Wi-Fi and on mobile data, because one run proves little.
Is it OK to test a camera that can see my neighbours or the street?: Keep it on your own property as far as you can, use privacy zones to mask what you can't avoid, and check the rules where you live, especially for audio. This isn't legal advice. Check your beta agreement for what you may share, and leave other people out of the evidence you send unless the manufacturer needs them.
Can I use BetaSuite for a camera 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. 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.

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

No account needed. The price is set in each store.

See everything else BetaSuite does →