Plan one small performance
A short browser recording benefits from a simple structure. Choose a style, begin with one chord, add a change after a few beats, build energy once, and finish deliberately. This gives the clip a beginning, contrast, and ending without requiring a long arrangement.
The best first recording is not necessarily the most complex one. A clear gesture or keyboard pattern is easier to repeat and improve than a dense sequence of changes. Fifteen seconds of intentional performance beats a minute of wandering.
A repeatable pre-recording checklist
Run the same short checklist before every take. It removes the variables that most often ruin an otherwise good performance.
- Pick one style and rehearse two or three chord changes at a steady tempo.
- If using the camera, confirm lighting, permission, and full-hand framing; if using keyboard, confirm each key produces the expected chord.
- Put the device on a stable surface so the frame does not move mid-take.
- Close heavy tabs and apps so audio and visuals stay smooth during capture.
- Decide where the ending lands before you press record.
Prepare the input before recording
If you use hand control, verify lighting, camera permission, and hand framing before you start a take. If you use keyboard mode, verify that key presses produce the expected chord changes. A tracking hiccup in the first two seconds of a take usually means the setup step was skipped, not that the performance was wrong.
Gesture Synth combines its generated music and responsive visuals for a short vertical performance. It does not need your microphone to generate the audio—the sound you hear in the recording is synthesized by the app itself.
Set up and fix hand tracking →Practice the keyboard method first →
What affects recording quality in a browser
Three factors dominate: device load, browser codec support, and motion discipline. A device busy with video calls or many tabs may drop frames or produce stuttering audio. Different browsers support different recording containers and codecs, so a file that plays perfectly in Chrome may need a conversion step elsewhere.
Motion discipline is the underrated one. Fast, constant hand movement creates visual noise and makes the music feel accidental. Slow, deliberate gestures read better on video and give the tracker an easier job at the same time.
Review the first take with a checklist
After a recording, review three things: did the first chord start cleanly, did the energy change happen where intended, and did the ending feel deliberate? If one part is weak, change only that part for the next take rather than replacing the entire plan.
Also test the downloaded file on the device where you intend to share it. Browser recording and playback support can differ across platforms, so an actual download test is more useful than assuming every format behaves the same everywhere.
Share and store the result deliberately
A downloaded clip is a file like any other: give it a name you will recognize later, keep the best one or two takes instead of every attempt, and play it once from the saved copy rather than from the in-page preview. The saved file is the ground truth for what a viewer will receive.
When you share the clip, the platform you choose may re-encode it. A short vertical video travels well, but small compression artifacts in fast-moving visuals are normal on every platform and are not a defect in your recording. If visual fidelity matters for a particular post, compare the uploaded result with your local file before making the post public.
Respect your recording environment
For camera-based performances, remember that your video preview is part of the local browser experience. Avoid including other people or sensitive material in the camera frame. If you do not want to use a camera at all, use keyboard mode for a camera-free performance.
Review the Privacy Policy if you want details about local camera processing and optional analytics choices.