How Clickplay Time Actually Works in a Production Environment
I ran into Clickplay Time by accident. We were trying to sync audio stems to video markers and someone on the engineering team had built a lightweight browser tool that let you click through frames while logging timestamps. That was years ago, and I eventually rebuilt most of the system from scratch. But Clickplay Time as a standalone concept is worth understanding because people keep reaching for it when they need frame-accurate click logging. Clickplay Time is essentially a lightweight timing utility that records the moment you click while a media timeline is running, then exports those click events as timestamped data. It is not a full NLE. It is not a scriptable automation framework. It is a click recorder with a timeline view. The typical use case is someone who needs to mark cues, transitions, or trigger points in a video or audio file without opening Premiere, DaVinci, or Logic. The interface is usually a single window with a video or audio player at the top, a timeline below it, and a list of click markers. You press space to play, click anywhere to mark a point, and export the results as CSV or JSON. That is it. The simplicity is both the selling point and the problem.
Getting It Running
Most versions of Clickplay Time are distributed as either a desktop app or a web-based tool. If you are downloading it from a GitHub repo or a third-party site, check whether it requires Node.js or Electron. The web version works in Chrome and Firefox but tends to drop frames on longer videos. The desktop build is more stable for files over ten minutes. Once installed, import your media file. Do not drag a 4K ProRes file into the web version unless you want the timeline to stutter every time you scrub. The tool is not built for high-bitrate delivery. Use a proxy or a lower-resolution export first. I learned that the hard way on a six-hour documentary edit where the entire session froze during a client review. The workaround was a quick ffmpeg transcode to H.264 at half resolution before importing into Clickplay Time.
How to Use It Properly
Start by setting your timebase. This is the part most people skip. If your footage is 29.97fps and you leave the default at 30fps, your markers will drift by roughly one frame every thirty seconds. Over a five-minute clip that is fifteen frames of error. Set the timebase to match your source media exactly. You can usually do this from the settings menu before loading anything. Play the media and click when you want a marker. Each click logs a timestamp. You can rename markers afterward, group them, or assign color codes. The export function gives you a CSV with columns for marker name, timestamp, and frame number. Some versions also support exporting as an .SRT file if you are building captions or as a .CUE sheet for audio work. Here is a practical workflow that actually works: import media, set timebase, play through once while clicking markers, clean up names, export CSV, then bring those markers into your editing software if needed. Most NLEs can import CSV marker files. Premiere and DaVinci both handle it fine. The resulting markers are not always frame-perfect because the export process rounds to the nearest millisecond, but it is close enough for most sync and cueing tasks.
Get the Full Details
Where Clickplay Time Falls Apart
It does not handle multi-track audio. If you need to click markers against separate dialogue, music, and effects stems independently, this tool will not help you. It treats the imported file as a single timeline. There is also no undo for clicked markers in most versions. If you click twice by accident during a fast sequence, you are stuck with both entries or you delete them manually one by one. The export is another weak point. Some versions only output basic CSV with timestamp and label. If you need metadata like clip name, take number, or project notes attached to each marker, you will have to manually add those columns in Excel or a text editor before importing elsewhere. It adds time, which defeats the purpose of using a lightweight tool in the first place. I also ran into a bug with files that have an alpha channel. The video plays fine but the timeline rendering breaks and markers shift by several frames. The fix was converting the file to a standard H.264 without alpha before importing. Again, ffmpeg handles this in about ten seconds with a single command line.
Alternatives Worth Considering
If Clickplay Time feels too limited for what you are doing, there are better options. For frame-accurate marker logging with export flexibility, check out SignalTap or MarkerBoard. Both are free and handle multi-format timelines properly. If you need something cloud-based that syncs across devices, Tagnote has a decent implementation though the free tier is restrictive. For pure speed when you only need to mark twenty or thirty points in a short clip, Clickplay Time is fine. It loads fast, requires no account, and gets the job done. Just do not expect it to replace an actual editing workflow or handle complex projects. It is a click logger, nothing more, and knowing that up front saves you from frustration later.
Final Notes on Clickplay Time
The tool exists in a grey area. It is useful enough that people keep finding it, but incomplete enough that everyone eventually hits a wall. The version you download matters a lot. Older builds from 2021 have known race conditions when exporting while playback is still running. Make sure you are on the latest release if one exists, or switch to an alternative before wasting an hour debugging export failures.
