Process a folder of pushup videos

Coaches can do this entirely in the browser. There is no script to install or command to type.

Open Process a folder from Single-Rep Pushup Form Analysis in desktop Chrome or Edge.
Choose a folder and allow the browser to read and write it.
Choose the pushup type (regular, dead-stop, hand-release, knee or incline) and confirm the capture FPS. Override the FPS for individual videos if needed.
Press Process videos and keep this tab open.
Find the MP4 highlight, PDF report and Markdown text beside each original. Review each row for warnings or failures.

What gets saved

For pushup.mp4, the app creates results_pushup.mp4, results_pushup.pdf and results_pushup.md. A results_pushup.json receipt records the settings, actual frame rates, analyzed range and output sizes. The MP4 is a metric highlight reel, with 30 FPS output.

Originals are not changed. Existing result files are skipped, including incomplete sets. Move old or partial results before retrying. Videos with the same base name, such as pushup.mp4 and pushup.mov, must be renamed first. Files beginning results_ or reslts_ are excluded. Subfolders are not processed.

Recording settings that matter

Capture FPS: Auto reads the encoded file rate. If the file does not say, that video fails with a message so you can enter the recorded rate. Slow motion filmed at 120 FPS is often saved at 30 FPS; enter 120 in that case so the phase times and tempo are real time. 30 FPS or higher is recommended.
Pushup type: one type applies to the whole batch and sets the standard the rep is judged against. Put different types in separate batches.
Camera: a side view with the camera near hip height and the whole body visible.
Clip: one rep, from top plank down and back to top plank. The app reports the first rep it finds; a clip with no detectable rep fails with a message instead of producing empty results. The phase markers are the automatic ones; moving them by hand is only possible in the single-video app’s Advanced mode.

Local processing and recovery

Video analysis and export happen in your browser. Static app code and model files may download from the internet. Folder permissions are granted by you in the browser, and you may need to grant them again after reopening the page.

One video runs at a time. A failure does not stop the rest. Stop batch cancels the active analysis/export; a save already in progress finishes before the queue stops. Closing the browser can leave partial results. Move these before retrying. Avoid concurrent programs writing to the same folder.

If the folder picker is unavailable, use a supported desktop browser such as Chrome or Edge, or return to the single-video app. MP4 export requires H.264 WebCodecs support; an unsupported encoder produces an error. Results are the same estimates and coaching guidance offered by the pushup app’s individual-video workflow.

For AI agents and developers: browser interface

Everything runs in the browser at https://apopt.com/pushup/automation.html. There is nothing to download or install. An AI agent or script that controls a browser (for example a browser-automation tool) can use the page’s versioned interface, window.apoptAutomation, instead of the folder picker.

Open https://apopt.com/pushup/automation.html and wait until window.apoptAutomation.version === 1.
Put one local video on the file input #automation-video; the browser reads it locally.
Start the job, poll until it finishes, then read the Markdown or download the outputs.

const api = window.apoptAutomation;
api.capabilities();   // app "pushup", options, defaults, outputs (no view option)
const id = api.start({ pushupType: "hand_release", captureFps: 60 });
api.getJob(id);       // state: running → succeeded / failed / cancelled
// After state === "succeeded":
await api.markdown(id);   // the text results
api.download(id, "mp4");  // also "pdf" and "md"
api.cancel(id);           // stops a running job

Option	Values
captureFps	"auto" or the recorded FPS, 1–2000
pushupType	regular, dead_stop, hand_release, knee or incline; default regular
model	movenet_thunder, blazepose, or yolo26n_pose to yolo26x_pose
outputFormat	vertical or person-crop; metricCycleSeconds 2–10

One job runs at a time, and only the latest job’s outputs are kept, so save every output before starting another. Unknown options and out-of-range values are rejected before processing. Video stays in the browser; an agent that reads the Markdown receives that derived text.

Example agent request: “Open the Pushup automation page, analyze pushup.mp4 as a hand-release pushup at 60 capture FPS, save the three outputs and read the Markdown.”