SDK performance
Measure it in your browser
Times MediaPipe BlazeFace inference and the Meeeetup SDK's tracking plus frontalness selection, frame by frame. Everything runs on your device — no frame and no crop is uploaded.
- Processed FPS
- —
- Detect ms
- —
- SDK ms
- —
- Tracking
- —
- Faces committed
- —
- Best score (held)
- —
- Best score (committed)
- —
- First commit
- —
- Frames
- —
- Resolution
- —
Tracking now — best frame so far
Best frames the SDK committed
On-device only. No frame, crop or metric is transmitted; the sole downloads are MediaPipe's wasm and model.
The SDK keeps one best frame per face and replaces it whenever a more frontal frame arrives. The badge is the best score it is holding (0–100); the value in brackets is the frame just processed.
These are live measurements on this device, browser and lighting. Numbers move with the environment.
Single capture
One subject, one best frame
The interactive flow a check-in kiosk uses. Of the faces that fill the guide box and clear the accuracy and quality thresholds, the biggest becomes the target. Tracking starts a 1–60 s timer: every better frame replaces the held one on the spot, and whatever is held when the timer runs out is the final capture. Every slider applies live, mid-run.
Settings
Start the camera
Realtime
—
- yaw / pitch
- —
- Confidence
- —
- Frontalness
- —
Best frame
- Frontalness
- —
- Time to commit
- —
When several faces qualify, the biggest one (brand-colored brackets) is the target. Faces failing a gate are drawn in grey, and the needle shows where the largest face is pointing.
On-device only. No frame and no crop leaves the browser.