There is a specific kind of person who pauses a video to ask, out loud, to nobody, "wait, is this 24?"
I am that person. I have lost arguments with clients about frame rates. I have lost arguments with myself about frame rates, usually at 2 AM, usually with a timeline open, usually while the same twelve-second clip plays for the ninetieth time. And after years of this, I have arrived at an uncomfortable conclusion: the frame rate matters enormously to the person making the video and almost not at all to the person watching it.
That doesn't mean it doesn't matter. It means the reason it matters is different than we tell ourselves.
The 24 vs 60 argument is really two arguments
When editors argue about 24 vs 60 fps, they're usually having two completely separate conversations and using the same words.
The first is about what the footage looks like. 24 frames per second has a slight stutter that our brains have been trained by a century of cinema to read as "movie." 60 looks smoother, more immediate, more like a window than a screen. Neither is better. They're dialects. Motion blur at 24 is baked into the shutter angle; at 60 you get crisper individual frames, which is why slow-motion footage shot at 60 or 120 feels like real movement instead of a slideshow of blurs.
The second is about what the footage is for. A talking-head tutorial at 24 looks fine. A talking-head tutorial at 60 looks like a webcam call, which is not the association most creators want. Gameplay at 30 feels sluggish; at 60 it feels like the game. Sports and action want more frames because there is more happening between them. A static shot of someone reading chat does not care.
Most frame-rate fights are one person arguing the first question and the other arguing the second. Nobody wins because nobody is in the same conversation.
Where the obsession actually comes from
Here's the part that took me too long to admit. My frame-rate vigilance is not really about quality. It's about control.
Editing is a job where the output is judged by strangers who will never know how many hours went into it, and where the one thing you can always do is make the technical details correct. Frame rate, bitrate, color space, audio levels, whether the export preset matches the platform's recommended settings — these are the parts of the job with right answers. The parts with right answers are comforting when the creative parts are terrifying.
So when the timeline is a mess and the story isn't landing and the deadline is in six hours, we go fiddle with the sequence settings. It feels like work. It is work, technically. It's just not the work that would improve the video.
I have spent entire afternoons in settings menus avoiding a decision about a cold open. I suspect I'm not alone, because the internet is full of editors who can quote H.264 bitrate tables from memory and cannot tell you why their last video underperformed.
The test that settles it for you
If you want a practical rule instead of a philosophy, here's mine. I call it the phone test, and it's aggressively unscientific.
Export the same short clip twice — once at 24 fps, once at 60 fps. Watch both on a phone, at arm's length, at the brightness you actually use, for ten seconds each. Not on your calibrated monitor. Not at 200% zoom. On the phone, like a viewer.
Most of the time you will not be able to tell which is which. That is your answer. The differences we spend hours perfecting are frequently invisible at the size and distance where the majority of the audience meets the work.
The exception is motion: fast camera moves, gameplay, sports, anything where a frame is a meaningful amount of movement. There, the difference survives the phone test. That's your signal to care, and it's a much narrower signal than most of us treat it as.
What actually does survive the phone test
Since the frame rate mostly doesn't, it's worth naming what does — because it's usually not in the settings menu at all.
- Audio. A video with clean audio and mediocre visuals reads as professional. A video with beautiful visuals and roomy, echoing audio reads as amateur. I have never once seen an audience complain about frame rate. I have seen a hundred comments about "the audio is weird."
- The first three seconds. Frame rate cannot rescue a slow opening. Nothing rescues a slow opening except cutting it.
- Pacing. Related, but distinct: whether anything is happening. I went deep on this one already in Video Pacing: the editing instinct nobody can teach you — the instinct that something feels slow is almost never solved by more frames.
- Whether the person on screen seems like they want to be there. Unmeasurable, decisive.
- Text legibility. If a viewer has to squint at your lower third, nothing else matters. Frame rate is irrelevant to a viewer who can't read the words.
All of these are creative decisions with no right answer, which is precisely why we flee from them into the settings menu where the answers are numbered.
The 24 vs 30 vs 60 cheat sheet I actually use
I keep this short on purpose. Long technical guides exist and are better than mine at the technical part.
- Talking head, tutorials, essays, vlogs: 24 or 30. Pick one and stay consistent within a project. Consistency matters more than which.
- Screen recordings, software demos: 30 or 60. Text motion at 24 can shimmer. Match your capture rate to your output rate and save yourself a conversion.
- Gameplay, sports, action: 60 fps. This is the case where the extra frames are the point.
- Slow motion: shoot high, deliver normal. 120 in, 24 out.
- Anything vertical for short-form: 30 is the safe default and nobody will ever mention it.
The whole list fits on an index card. The hours I've spent arguing about it do not.
Why this makes good merch, weirdly
Every niche has a uniform — the thing you wear to signal to the people who get it and to be invisible to the people who don't. For editors and post-production people, that signal is the joke about caring too much about something invisible. The timeline joke. The export joke. The "we'll fix it in post" joke.
The frame rate argument is the same joke with a stopwatch. It's a thing we care about passionately, correctly, and at a volume nobody outside the edit bay can hear. Which is exactly what a good shirt does: it says the quiet part to the only people who will laugh.
That's the whole point of the PixelPunch collection: inside jokes you can wear. If you work in a terminal more than you work in a timeline, the I Am Root shirt is the same joke in a different dialect — and if you're an editor waiting on an editing-specific design, that's coming. Either way, it's for the person who notices the thing nobody asked them to notice.
The honest ending
I'm not going to stop noticing frame rates. That's not how this works; the noticing is the job and the personality defect both. But I've gotten better at asking one question before I open the settings: is this the decision that changes how the video lands, or is this the decision that lets me avoid that question?
Usually it's the second one. Then I close the settings, watch the first thirty seconds on my phone, and go fix the opening.
The frame rate was fine the whole time.