The Quora question "What would be the best way to record myself while I practice my tennis serve?" gets a few thousand views a year. The answers are mostly variations of "tripod, behind you, hit record." Mostly correct. There are a few specifics that matter.

This post covers the right way to film your serve solo — for AceSense analysis, for your own technique review, or both — without a partner, without a follow-tracking camera, and without overthinking it.

TL;DR

Phone on a fence clip or tripod, behind the baseline you're serving from, centred, at net-tape height (3 to 4 feet).
1080p / 60 fps if your phone supports it.
Hit a basket of 30–50 first serves, then 30–50 second serves.
Upload the video. The AceSense pipeline finds each serve, tags it as first or second by your serve location, and produces the per-serve breakdown.

The whole thing takes 25 minutes including the basket of balls.

What you need

A basket of balls. 50–100 minimum. If you only have a hopper of 30, plan to walk around picking up between sets.
Your phone. Same one you'd use for match recording.
A fence-mount clip OR a tripod. Same gear list as the $30 setup post. Fence-mount is faster.
Optional: a target. A cone in the deuce-T corner, a cone wide on ad. Not necessary, but if you're working on placement specifically, two cones turn a serve session into a structured drill.
Optional: a portable battery. For a 25-minute session your phone won't die, but if you're chaining a serve session with a hitting session, charge.

Where to put the camera

The placement spec is identical to the match-recording spec (full guide here). For serves specifically:

Behind your serving baseline, centred.

That's it. The reason this position works for serve filming:

It catches your motion in half-profile — you'd see your right side as a right-handed server. You can see your toss arm, your back-leg push, your contact point, your follow-through. All the technique-relevant body parts are visible.
It catches the bounce in the service box — both the deuce side and ad side. So you get placement data per serve.
It catches the opponent's return zone — which doesn't matter for solo serve practice, but is useful if you transition to a hitting partner mid-session.

A common mistake is filming from the side (clipped to the singles sideline fence, perpendicular to your serving direction). This gives a great profile view of your motion — but the court keypoint detector can't recover useful homography from a side-on view, and the AI report degrades to "we see your shots, but we can't tell where they bounced." If you only want technique review by eye, side-on works fine. If you want AceSense's per-serve breakdown, behind-baseline-centred is the correct answer.

How long, how many serves

A focused serve session is typically 20–30 minutes of actual hitting. Within that:

Warm-up (5 minutes, not recorded if you want to save time): Easy serves at 50–60% pace. Don't analyse these; they're not your real serve.

Block 1 — first serves (8–10 minutes, recorded): 30–50 first serves, all to the deuce side or all to the ad side, then the other side. Don't mix in second serves. The cleanest data comes from one shot type at a time. Your serve placement target should be narrow — wide deuce, T deuce, body deuce — not "anywhere in the box."

Block 2 — second serves (8–10 minutes, recorded): 30–50 second serves. Spin variety is the point at this level. Kicker, slice, flat with topspin. Mix sides.

Cool-down (3 minutes): A few easy serves to finish on a comfortable rep. Doesn't need to be recorded.

If you want to chain a serve session with practice points or a rally session afterward, the camera setup is already correct for match-style filming. Just keep the camera running through the transition.

What the AceSense report shows from a serve session

Upload the recorded video. The pipeline detects each serve, classifies it, and produces a session report that includes:

Total serve count by first vs second.
Speed estimate per serve, with the confidence band.
Placement heatmap — where each serve bounced in the box, deuce vs ad, broken down by first/second.
Stroke-quality score per serve and an aggregate.
Fault rate — how many serves missed long, wide, or in the net.
Trend chart — if you've recorded previous serve sessions, your week-over-week pattern.

The "fault rate" and "placement heatmap" are the high-leverage numbers for most amateurs. Speed is a vanity metric that you should treat as a trend, not an absolute.

Common mistakes (and the fix)

A few things we see in user-uploaded serve sessions that hurt the report:

1. Filming from inside the court

A surprising number of users mount the phone at the net post or on the singles sideline, thinking that's a "good profile shot." It's not — the court keypoint detection breaks down because the court is partially behind the camera. Fix: behind the baseline, every time.

2. Filming with auto-tracking on (Pivo, OBSBOT, etc.)

Auto-tracking cameras follow you around. Wrong for serve analysis — every time the camera pans, the court coordinates have to be re-estimated, and the homography drifts. Fix: turn off any auto-tracking. Fixed camera. Full court in frame.

3. Filming for too long

A 90-minute serve session that's actually 20 minutes of serving and 70 minutes of ball-pickup creates a huge video file with mostly empty time. The AceSense pipeline can handle it, but you're uploading a lot of irrelevant footage. Fix: stop recording during long ball-pickup phases. You can easily restart.

4. Mixing in groundstrokes

If you serve a few, then rally a few, then serve again, the report sees you serving 14 times in a 60-minute session and the speed/placement aggregates are noisy. Fix: dedicated serve session is the cleanest data. If you mix, accept that the report's serve aggregates are diluted.

5. Filming straight at yourself from the opposite baseline

Workable for technique review by eye, but the camera can't see the bounce of your serve clearly (it's coming toward the camera, not landing in the camera's field of view). Fix: stick with behind-your-own-baseline.

What to do with the resulting video

Two paths:

Path 1: AceSense analysis. Upload, get the report, read it. The serve-specific feature page is at /features/shot-detection.

Path 2: Your own eye. Watch your serves at 0.25× speed in your phone's video player. This is genuinely valuable in addition to AI analysis — the eye catches things ("I'm pulling my head down too early") that an AI report doesn't yet quantify. The Quora "watching recordings improve your skills" thread has community consensus that it works.

The two paths are complementary, not exclusive. The AceSense report tells you what's happening at a population level (your toss height is X cm above the reference distribution; your contact point is 3% later than the reference); your own eye tells you what to feel different next session. Use both.

A specific 4-week solo serve protocol

If you're committed enough to do this for a month, here's the loop we've seen work:

Week 1: Baseline session. Record. Read the report. Pick the one biggest leak (usually fault rate on second serve, or wide-vs-T balance on first).
Week 2: Same session structure, working on the leak. Record. Compare to week 1's numbers.
Week 3: Same. Compare to weeks 1 and 2.
Week 4: Compare across all four. The trend chart is what to look at, not any single session.

This is the 4-week self-coaching workflow applied to serves specifically. It works. Most amateurs don't do it because it requires showing up alone with a basket of balls four weeks in a row, which is more discipline than most have. If you do it, you'll move materially.

Related: The right camera angle and height for AI shot detection is the placement deep-dive. Why your serve speed reading might not be 130 mph is the post you need before you over-react to your speed numbers. Or /features/shot-detection for the product view.