How do I become a 3D printer beta tester?

If you already own a printer, join the manufacturer's firmware beta when one is open: Bambu Lab, for example, lets owners opt in from the Bambu Handy app. For pre-release printers, watch the brand's forum, newsletter and social channels for recruitment posts, and be ready to say which printers you own, which materials you use and what you print. Read the terms first: some tester schemes are review programmes, while a beta asks for bug reports, often in a set format and under a confidentiality agreement.

What should I test first in a 3D printer beta?

Set-up, calibration and the first layer. Everything else depends on the printer laying down a good first layer, so if that is unreliable, later results are hard to trust.

How do I test 3D printer accuracy fairly?

Print the same calibration cube or test model each time, with the same filament and slicer profile, and measure each axis with calipers. Write down the error as a percentage and repeat after each firmware update or profile change. It shows change over time, not a lab result.

What should I record when a print fails?

Photograph the failed print before you remove it, with the printer's screen or app showing its state. Note the time, how far through the print it was, the filament, profile and firmware, and what the printer said. Log how often it happens, not just the one time.

Can BetaSuite record my slicer and my printer at the same time?

Only what is on your phone. If you send jobs from a phone app, dual recording puts your phone's screen and the camera into one video. It can't record a computer's screen, so for a desktop slicer use your computer's own screen recorder and take timestamped photos of the printer and the monitor.

Can I use BetaSuite for a printer 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. Captures still save to your camera roll by default, so if your photos back up 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.

3D printer beta tester guide: what to test and log

To beta test a 3D printer well, repeat the same small set of test prints each week, record the conditions every time (filament, room and enclosure temperature, firmware, slicer profile) and back every failed print 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 there is a free 12-step protocol to import.

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

How people get into 3D printer betas

Printer betas come in two kinds, and they want different testers.

Firmware betas for a printer you already own. These are the easiest way in. Bambu Lab, for example, announces public firmware betas on its community forum and lets owners opt in from the Bambu Handy app under Me > Beta Firmware Program, as its P2S public beta post describes. Its private beta recruitment posts add a sign-up form and ask testers to report bugs in a set format, keep the beta private and not leave the printer unattended on beta firmware.
Pre-release printers. Brands recruit for these through their forums, newsletters and social channels. Have ready the printers you own and how long you have printed, the materials you use (PLA, PETG, TPU, resin), what you print (functional parts, miniatures, large or multi-colour prints) and your space (enclosure, ventilation, room temperature).

Read what you are signing up for. Some "product tester" schemes are review programmes rather than betas: Creality's official product testing programme, for example, lets testers keep the product, expects an evaluation for its store and suggests applicants include a social media link. A beta asks for bug reports instead, often under a confidentiality agreement. These pages were checked on 4 October 2026, and BetaSuite isn't connected with either brand.

Getting picked is the start. Apply only if you can keep printing through the whole test period. The rest of this guide is how to do that well.

What to test in a 3D printer beta

Start with set-up, calibration and the first layer, because everything else depends on them. If the first layer isn't reliable, later results are hard to trust. Then work through the rest, and repeat anything that fails so you can say how often it happens. The table covers filament (FDM) printers, and the last row adds what changes for resin.

Area	What you are checking	Evidence worth capturing
Set-up and calibration	Assembly time and difficulty, the self-test, automatic or manual bed levelling, and whether the calibration survives a restart, a move or an update.	Photos of each assembly stage and the calibration result on the screen or app.
First layer and adhesion	Even, well-pressed lines across the whole bed, with no gaps, scraping or lifting corners. Does it repeat across the bed and across several prints?	A close photo of the worst corner with a ruler beside it.
Dimensional accuracy	The size of a calibration cube or test model, hole sizes, and the fit of two parts that should mate. Compare against the model, not against another printer.	A photo of the part beside calipers, with the reading visible.
Print quality	Layer lines, ringing, stringing, overhangs, bridging, seams and top surfaces at the settings you really use.	Close-up photos in side light, with the profile name noted.
Filament and multi-filament handling	Loading, unloading, runout, tangles, wrong-slot errors, and clean colour or material changes, including through an AMS or other multi-filament unit if there is one.	A clip of each load or change, and a photo of any jam.
Failure detection	Whether it notices a clog, runout, a knocked-off part, spaghetti or an opened door or lid, and what it does next. Only test faults the manufacturer allows.	A clip of the alert on the printer and in the app.
Long prints and recovery	Prints of several hours, pause and resume, and any thermal error. Test power-loss recovery only if the manufacturer's brief asks for it.	Photos at the start and end with the elapsed time visible, and the finished part.
Noise and temperatures	Loudness at normal distance, how the enclosure or chamber temperature rises and levels off, and whether the room warms up noticeably.	Notes of the distance, profile and reported temperatures. A phone sound meter is fine for comparing runs.
Slicer, app and connectivity	Profile import, sending jobs by Wi-Fi, USB or card, remote monitoring, any camera feed, notifications and firmware updates.	A screen recording from the phone app, plus a screenshot of any error with the time visible.
Time-lapse and camera	If the printer or app makes a time-lapse or has a built-in camera: does it start, stay in frame and save?	The finished time-lapse, or a screenshot of the camera view.
Resin printers	Build plate levelling, vat and film handling, supports and failed-print clean-up, wash and cure steps, smell and leaks.	Photos of the vat, the plate and any leak or failed print.

Safety first. Hot ends, heated beds and moving axes can burn or trap fingers, so wait for the printer to cool and keep your hands clear while it moves. Run it somewhere ventilated, on a hard surface away from anything flammable, and follow the manufacturer's guidance on fumes and enclosures. Resin irritates skin and eyes: wear gloves and eye protection and dispose of it the way the manufacturer says. Only test thermal protection, door interlocks and other safety features exactly as the beta brief describes, never bypass them, and don't leave the printer running unattended unless the manufacturer says it is designed for that. If you smell burning or see smoke, or a cable or connector gets hot, switch it off and unplug it if you can do that safely, then contact the manufacturer.

A repeatable test-print set

"It prints better now" can't be compared from one week to the next. Printing the same small set with the same filament and settings can, so you can tell whether a firmware update or a profile change helped or hurt. It is a relative test, not a lab result.

Choose a small set: a first-layer test, a calibration cube (or the printer's own test model), an overhang and bridging test, and a short stringing test. Use files you can download again, and note where they came from.
Fix the variables: the same filament from the same spool (dried the same way), the same slicer profile, nozzle and bed surface, and as close as you can to the same room temperature. Change one thing at a time.
Print the set. Photograph each piece from the same angle in the same light, with a ruler beside it.
Measure the cube on each axis with calipers and compare it with the size in the slicer. Write down the numbers and the error: (measured − model) ÷ model × 100.
Score the rest by eye on a scale you wrote beforehand (for example 1 = fails, 3 = acceptable, 5 = no visible defects) and note what you see.
Repeat after every firmware update, profile change or hardware change, and log each result as a new row in the same log.

Conditions to record every time

A fault you can't reproduce is just a story. Log the same details for every print 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 printer's own logs, if the manufacturer collects them.
Filament and moisture	Brand, material, colour, spool age and whether you dried it. Damp filament causes stringing, popping and weak parts that look like printer faults.
Slicer and profile	The slicer and its version, the profile or preset, layer height, speeds, temperatures and supports. Use the same profile each time, or say what changed.
Printer state	Nozzle type and age, build plate or surface, bed and nozzle temperatures, enclosure open or closed, and any hardware changes.
Room and enclosure	Room temperature, draughts, humidity if you can measure it, and the chamber temperature the printer reports.
Software	Printer firmware, app version, slicer version and plug-ins. Note them again after every update.
Network	The Wi-Fi band, the distance to the router, and whether the job went by Wi-Fi, USB or card.
Print details	The model name, estimated and actual print time, and how far through the print it was when something failed.
Changes	Anything different since the last print: a new spool, a nozzle swap, a moved printer, a new router or a firmware 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 printer.

When	Focus
Day 1	Unbox and assemble, photographing each stage and anything that doesn't fit. Note the firmware, run the self-test and calibration, and record how long it all took.
Days 2–3	The first-layer test and the calibration cube, then repeat them on a different part of the bed. Send your first jobs from the slicer and from the app.
Days 4–5	The rest of your test-print set, then a first longer print. Test loading, unloading and (if fitted) changing filament.
Days 6–7	One or two long prints. Watch the first layers, then check on the printer regularly, and leave it unattended only if the manufacturer says it is designed for that. Log every stop, error code and failed print.
After a failure	Photograph the failed print before you remove it, with the printer screen or app showing its state. Note how far through it was and what the printer said.
Every week	Reprint the same test set. After any firmware update, repeat the first-layer, calibration and filament checks.

A pass/fail checklist for a 3D printer

Agree your thresholds with the manufacturer's brief first. If it doesn't give any, write your own before you start (for example, "calibration cube within 0.2 mm on every axis") so you aren't judging after the fact.

Completes assembly and calibration without a reset or a call to support.
Pairs with the app first time, and takes jobs from the slicer reliably.
Lays down an even first layer across the whole bed, print after print.
Prints the calibration part within the tolerance you set before you started.
Loads, unloads and changes filament without jams, tangles or wrong-slot errors.
Detects the faults the manufacturer says it detects, and pauses or alerts you.
Finishes a long print with no stall, layer shift, warping, clog or thermal error.
Resumes cleanly after a pause, or after a fault the manufacturer says it can recover from.
Keeps its noise at a level you could live with in the room where it sits.
Brings the enclosure or chamber up to temperature as the manual describes, with no thermal warnings.
Has no unexplained error codes, stops or failed prints in a week.
Installs a firmware update without losing your profiles, calibration or settings.

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

How to capture evidence engineers can use

Photograph the failed print before you touch it. Take one wide shot with the bed, the nozzle area and the printer screen or app in frame, then a close-up of the defect with a ruler beside it.
Film the first layer going down. Plenty of failures start in the first few minutes, and a short clip shows adhesion, extrusion and nozzle height better than a photo of the result.
Put the app and the printer in one clip. If you control the printer from a phone app, dual recording in BetaSuite records your phone's screen and the rear camera into a single video, so what the app says and what the printer is doing sit side by side on one timeline. BetaSuite can't record a desktop slicer's screen: use your computer's own screen recorder for that, and photograph the monitor and the printer with the stamped camera.
Use a reference. Calipers and a ruler show size, and a coin shows scale in a close-up. Keep the angle and the light the same each time.
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.
Use the right tool for time-lapse. BetaSuite is not a time-lapse tool. Use the printer's own time-lapse or a separate camera on a stand, and keep BetaSuite for the stamped photos and clips you start yourself.
Catch the intermittent faults. A print can go wrong while you're making a coffee. With Instant Capture, BetaSuite keeps a rolling buffer and saves the last 15–30 seconds when you tap, so you can work near the printer and still catch the moment.
Mark it as it happens. Add a one-tap marker or a quick voice note with the time, then write it up properly later.
One issue per photo or clip. Name it by what happened ("Layer shift at 62%, long print 3"), not "IMG 214".

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, slicer and app versions, the filament and profile, test dates and the kinds of print you ran. Three sentences on how it went.
Findings, worst first	Safety issues first (heat, smoke, smell, electrical faults, trapped fingers), then anything that stops it printing, then print-quality problems, 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.
Files and profiles	The model file (or a link to it) and your slicer profile or project file, so engineers can reproduce the print. Check your NDA for what you may send.
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:      Layer shift about two-thirds of the way through a long print
Severity:   High (the print is ruined and the printer kept going)
Expected:   Finishes the 6-hour print with no shift
Actual:     Layers shifted along X at about 62%, with no alert
Frequency:  2 of 4 long prints, both with the enclosure closed
Conditions: PETG, 22°C room, firmware 1.2.3, "Standard" profile, job sent by Wi-Fi
Evidence:   Wide photo, then a close-up with a ruler, stamped 21:47:12

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 printer, and note the model, serial number, firmware and filament in your first session.
Import the free protocol below. It opens with a free-text step for those details.
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. Everything is stored on your device, with no account.

Free BetaSuite protocol: 3D printer first-week test

This is a ready-made, 12-step protocol for the first week with a 3D printer. It was built with the site's own Protocol Builder, so the link below is a real import link. It opens with a free-text step for your set-up details, mixes pass/fail checks with a choice, a multiple-choice and a rating question, and asks for a photo, video or dual recording where the evidence matters. It is written around a filament printer, so edit the steps to suit your machine (for a resin printer, rewrite the filament step around the vat, the wash and the cure). For the general idea, see the test protocol template.

3D printer first-week test · 12 steps · free to import and edit

Open this protocol

Before you start: record the printer model and serial number, firmware, slicer and app versions, the filament brand and material (and whether it is dry), the room temperature and whether the enclosure is open or closed.Free text
Set-up and calibration: assemble and level or calibrate exactly as the manual describes. The self-test and any automatic bed levelling finish with no error and no manual rescue. Photo: the printer's own screen after calibration. If it has no screen, screenshot its app instead.Pass / FailPhoto required
First layer: print the first-layer test or a single-layer square. The lines are even and stuck down, with no gaps, blobs, scraping or lifting corners. Photo: the first layer from above, with a ruler beside it.Pass / FailPhoto required
Calibration print: print a small calibration cube or the printer's own test model. Measure each axis with calipers against the size in the slicer. It stays within the tolerance you agreed in advance, with no layer shifts or visible artefacts. Photo: the print beside the calipers.Pass / FailPhoto required
Slicer and app: send a job from the slicer or the printer's app. It arrives, starts and reports progress that matches the printer's own screen. Record the app and the printer together.Pass / FailDual recording required
Filament handling: load and unload filament and, if the printer has a multi-filament unit such as an AMS, switch between at least two spools. There is no jam, tangle, mis-feed or wrong-slot error.Pass / FailVideo required
Failure detection: following the manufacturer's steps only, trigger a fault the printer says it detects, such as filament running out or a lid or door being opened. It pauses or alerts you in the app and resumes cleanly. Keep your hands clear of the hot end, the bed and all moving parts.Pass / FailVideo required
Long print: a print of several hours finishes with no stall, layer shift, warping, clog or thermal error. Any time-lapse the printer or app makes plays back and matches the print. Photo: the finished print.Pass / FailPhoto required
How noisy was the printer at normal distance during a typical print?Options: Quiet · Noticeable but fine · Loud · Unusual noise such as grinding, clicking or rattleChoice
Firmware update: the printer or app installs an update without a failed flash, and your profiles, calibration and filament settings are still there afterwards.Pass / Fail
Which problems did you see? Tick all that apply.Options: Poor first layer or adhesion · Warping or lifting · Layer shift · Clog or under-extrusion · Filament jam or tangle · Slicer or app error · Connection dropped · Unexpected stop or error code · None of theseMultiple choice
How much would you trust this printer to finish a print correctly first time? 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-1YUY_buBH-KwO9tAXEhWRJlmzgENxdUfTQXnFtUvShyMOIHNnMUqSOpNZxD_nvxVCy17ubuwZFUbRBnlYrUcOZb77v48g_ZThN2T77hiK-nnWkLM_utVXZPpu8i046E7I8e8j2ZX5zZ__3nzKLI2X7rPotTF7bSB4G7UMUJ6J7iBRilmeaA22rrtmVHYq67HeixgJFJ6tadL1quqFty6LcZHnm6SHbb_IsRJp4h-wbGpwnOLsZQkQf9-BJOq8gHum65-gUGUCrIJDXaMDOY08-52TGE3rKIRgtyac1OE3wQD5oZ0Oe4gza4Eg2Qu_TAqtgxLiE-jX_dzpSPJIHHUEHUP78m-VF79wIkcaJPMbZE9wu5gVkpXGBn-gAbiILzgPfInWX5dlrimKe0lsSje49Ru3sHjAEGnuzxDP0QCa9ty4hoPcoozkDhrTLiHZGA4qC9LqncAdvjgSBzCC4B0vV9gw4Rzdi1BJ6WuMabQ8waKvDEU46HsE6IO_dApV1l9iegpzpDn44uuj2t-j_KoA7WQjSE1nAgRtyU8wdfDcwbkcMHG5Zlq9_w9FF0DGknmgbImHC5XdMIjB4Jr9f9ln7xNxKtxO5GBSEoO3B0Ho7_DijpwUAoy0FQE9AD5wa8yPO8h6UO9n8Wu4Bp5BDb1wfUl44MSbOg9FD5EvpvCUfnhQ_PGYIg3cjYO8eaA2K4GdDHnoKWhHoyDV9-4jJUtKlMoQwojG3oIGce-IUXuKc6k6Ev4PvCRO3COUR8L0Oy_YcaCIfAA_IoKYoQf-DQNvlOonhDr6LLKrz8tr6LDpDHq1cNIcHT6T4PVQPfPcRthXvox5i4FQfdNCJsj7SgDKGl2S5AMI3LkkmGTwR5x4C8RW8c_2C7WPOLzHBaUqFoPf6gbiDbBMhBfM0Ob6evDt4CiwWjCxteaTwsxy-g788WgwTk0Pd2k10h6TwhamrdRzRKhbTHozDxUNmmy6v7oJW5aCHJ7FYFgjjbKIW14Wz1RHCzE3lQuDr71_nEE46yiP0FE9JaBEMITf35CBMzplF9ovVWAfvcMwhImsjh1EHMXAnnYeTd_YggnFxUXoqA7VhJimKJBcPGpwx7sT8v1gMd3X2Ca3kz-CsOecQvT4cuH0w4Gzik_ICs0vHNS53Z63qWqufrU16m1c5G52yVM6xgNKjiSyp1OUJ50CJbmiIW8skXZl7aZWnMI8UQBpCa8538AeiiRf61KTlgQe3NIIdiLgx_A_bYmKhMTC6B958YjYxRH90_N8iXFz57AYI9EAeDRzd7MPqpBSuKgkRjclvxZLDCT1bTM4HwWFltB_RrO2Ar-0Zoh7Z0qZAT_DkwqcJRrynAJNhdHuU95cj6ymvnxlWykytj7I8-707gXU6nOGET9TA3LIuZaR0iMkM1OwZDYR4nrREs6x9tXh1OmNhnhRG2n8sX3YhNCaReVmWAOKeM2u0IQWDwXDMUyWpV5N3gzas6Ftj5MdX7gSKbNCLx4eojUlQ0nIKndCr1Lm_HbU8crze0BhAabXME0Sv4I1m9NKLGDlXc75gMzJVT242y_Lo52SlOtwYweXovBBCOu8pHc3LAcFtfAUlfAXWRcY1saGBr0C6cTIUifd7m2c_zhS4wGWsmrwbp5hGss95_FmHzMETvaH3PCve0znbZ3Xdlbt6KwV2hKJGtREoi1JIqoty21O9rZvsQ36D05dB6uOD1GWMxxDY4rM8kzhxq_gmZ3DFvNsq1ZZdK1q5KRjzrcDNUIgC26JUTdlWdf8U889xSPt0vDZFPxS7dhBDVWxFXW0rgU1Xia6u-2ZX9O12-wyvLwPgzw6Anw57We9wi8NGNLuqFHWx2wgkdorNtuqKrlOE7TNr-P8dLn8JFjWjWUJpe7jC09ZYKNx0YltVUtSbXSX6uh1ET9u-LcpNPRTdcxV_FgPsL0H1oBXdCLffVE3VKVHsykLUZaNEj20vhl3ddIOsNhu1ewbRl-H4Xw3Hnw7_sNtg1w0kirbpRI1tK7DuURR92VZK0VC09BT-z27w_nS3o2pTFsOWRN91pah3Qy12payEUqqrsC6bonnmdv-hoX5NcTm1vz06LflHQTddRtTsz7MmHtj-5KKWhOz7_Ry5WErfSrPK8uyvdg4883BCdGX3wWur1jZoeb-e4x5jNMSj8Fp6v1V9OfSi22Ev6k0vRbfb9aJpyy0Rbbt298LJ_tc_RF42fp13d2oYaqkEdv1G1D1VYifLQRRbHLAvG0n9s1ni3_ikWTdPTv2xjv7AnnI7MTFk6kj8ocAfUYt2bkYu7vOjuvgXrlVVs1XkBb3nL6bl5esh8w7HpLvk6o-__KzdSTLkQM7axWlBeTdNtJCJ3k8kI_GA6CZ-Z5mvpVOUmGhp9a1wy6O2qqhttmJbUCPqZlsK7LadKHtU27IqVFN2LyX03_v2uzaGeWUPzZUUWGIpFZWi7NtO1IPsBO7kICopm52qm6ZCmX14--Hth38CA1ppP8AXAAA=

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 printer itself. BetaSuite doesn't connect to the printer, so it can't read its logs, temperatures or print history. You note what the screen or app shows, or record it.
You want a time-lapse or unattended monitoring. A phone isn't a print camera. BetaSuite records the moments you start or save, so use the printer's own camera or time-lapse, or a fixed camera, to keep an eye on a long print, and leave it unattended only if the manufacturer says it is designed for that.
You want to record a desktop slicer. BetaSuite records your phone's screen, not your computer's. Use your computer's screen recorder and photograph the monitor.
You need lab numbers. Material strength, exact dimensional accuracy and certification testing need proper equipment, not a phone and a pair of calipers.
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

How do I become a 3D printer beta tester?: If you already own a printer, join the manufacturer's firmware beta when one is open: Bambu Lab, for example, lets owners opt in from the Bambu Handy app. For pre-release printers, watch the brand's forum, newsletter and social channels for recruitment posts, and be ready to say which printers you own, which materials you use and what you print. Read the terms first: some tester schemes are review programmes, while a beta asks for bug reports, often in a set format and under a confidentiality agreement.
What should I test first in a 3D printer beta?: Set-up, calibration and the first layer. Everything else depends on the printer laying down a good first layer, so if that is unreliable, later results are hard to trust.
How do I test 3D printer accuracy fairly?: Print the same calibration cube or test model each time, with the same filament and slicer profile, and measure each axis with calipers. Write down the error as a percentage and repeat after each firmware update or profile change. It shows change over time, not a lab result.
What should I record when a print fails?: Photograph the failed print before you remove it, with the printer's screen or app showing its state. Note the time, how far through the print it was, the filament, profile and firmware, and what the printer said. Log how often it happens, not just the one time.
Can BetaSuite record my slicer and my printer at the same time?: Only what is on your phone. If you send jobs from a phone app, dual recording puts your phone's screen and the camera into one video. It can't record a computer's screen, so for a desktop slicer use your computer's own screen recorder and take timestamped photos of the printer and the monitor.
Can I use BetaSuite for a printer 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. Captures still save to your camera roll by default, so if your photos back up 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.

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 →