QuickEditVideo

I didn’t wake up planning to build another in-browser video editor.

Honestly, I woke up annoyed.

Annoyed at upload spinners.
Annoyed at “processing…” banners that never finish.
Annoyed at perfectly capable machines being treated like dumb terminals while some server decides whether I’m allowed to trim a clip.

At some point I caught myself staring at a progress bar and thought:
Why is my laptop—this absurdly powerful slab of silicon—just… waiting?

That’s when the doubt crept in.

“Isn’t this already solved?”
“Won’t people just say ‘use Canva’?”
“Am I rebuilding a toy while the world ships AI copilots?”

Yeah. All of that.

But the frustration stuck.

The Question I Couldn’t Shake

What if the browser is the computer?

Not metaphorically. Literally.

Modern browsers can decode video.
They can render timelines.
They can scrub, composite, resize, export.
They can do shockingly real work.

So why are we still shipping gigabytes to servers just to… move a clip two seconds to the left?

I kept circling the same uncomfortable thought:

There is no reason for a server to be involved in basic video editing.

None.

No latency excuses.
No “cloud magic.”
No permissions ceremony.

If it’s editing, the machine already has everything it needs.

The “Should I Even Build This?” Moment

This was the dangerous part.

Because once you see that something can be simpler, you start asking whether the complexity was ever justified.

And then you remember the industry incentives.

Servers mean lock-in.
Accounts mean friction.
AI features mean upsells.

Meanwhile, I just wanted to trim a clip.
Fast. Offline. No drama.

So yeah, I hesitated.

Building an in-browser editor feels almost… rebellious now.
Like showing up to a sci-fi conference with a soldering iron and a grin.

But that’s also the point.

Why QuickEditVideo Is Browser-First

Here’s the core belief I shipped this update around:

Editing is not creation.

Creation is messy. Generative. Expensive.
Editing is mechanical. Precise. Human-driven.

QuickEditVideo is for editing clips, not creating them.

That distinction matters.

Yes, it means some things are capped:

• No heavy AI inference

• No server-side video generation

• No “type a prompt, get a movie” magic

That’s fine.

Unix figured this out decades ago:
Do one thing. Do it well.

Once you try to turn an editor into a studio, a renderer, an AI lab, and a monetization funnel… you lose the plot.

So I didn’t.

The Unexpected Side Effect: Speed (and Calm)

When everything runs in the browser, something funny happens.

You don’t need full SSR.
You don’t need complex backends.
You don’t need to negotiate with infrastructure.

It’s just JavaScript. Compiled. Shipped.
Straight to the edge.

Click the link.
It loads.
It works.

No “sign up to continue.”
No “we’re warming up your workspace.”

That calm? That’s intentional.

Old-Fashioned, on Purpose

I’m very aware of the era we’re in.

AI everywhere.
Agents everywhere.
“Let the model decide.”

And yet.

Here I am, building like it’s Web 2.0 again.
Fun. Geeky. Slightly stubborn.

Because tools don’t need to be bossy to be useful.
AI should be a nudge, not a manager.

And frankly?
Screw the big corps that somehow made video editing feel like a luxury good.

This stuff should be accessible.
Immediate.
A right, not a subscription tier.

The Principle That Guides Everything I Ship

This is the same rule I use everywhere:

If it doesn’t help indie devs get to $10k MRR faster, it’s noise.

Less overhead.
More momentum.
More time spent on work that actually compounds.

QuickEditVideo exists because editing friction steals focus.
And focus is the rarest resource we have.

What I Shipped (Quietly, Intentionally)

No big launch.
No hype video.

Just a lean, browser-first editor that:

• Runs entirely client-side

• Respects your machine

• Gets out of your way

That’s it.

If this resonates—awesome.
If it breaks—tell me.
If it feels useless—especially tell me.

👉 Try it, poke at it, and share what feels right (or wrong).
Your feedback literally shapes where this goes next.

I don’t like paywalls.

I don’t like subscriptions.

I don’t like signups.

I really don’t like uploading my assets to someone else’s cloud just to merge some videos.

I just want to edit a video.

The same way I type text into a textarea.

Open → do the thing → export → done.

No account.

No “start free trial”.

No “uploading your file…”.

So I built QuickEditVideo.

The original sin of modern video editors

Somewhere along the way, video editing became… heavy.

• Canva: polished, powerful — but everything uploads. Your files live there, not with you.

• CapCut: does everything, installs everything, ships everything. Bloated.

• DaVinci Resolve: incredible tool but needs installation, and slowly moving basic features behind gates.

All great products.

All solving problems I don’t have.

My problem is simple:

“I want to open a web page, manipulate some clips, and export it.”

That’s it.

My rules (non-negotiable)

Before writing a single line of code, I wrote rules instead:

• ❌ No paywall blocking editing

• ❌ No subscriptions

• ❌ No signups

• ❌ No cloud uploads

• ❌ No local app installs

✅ Everything runs inside the browser

✅ Your files stay on your machine

✅ Editing is always free

✅ Export in any resolution for free

✅ Anything can be done in browser should be free

Editing should be as free as typing text.

You don’t pay to open a textarea.

You don’t “subscribe” to write a paragraph.

Why should trimming, or overlaying a video feel harder than writing a tweet?

So I made the tool I wanted

Not the “best video editor”.

Not the “most features”.

Not an AI everything machine.

Just:

• Load local media

• Drag things around

• Resize, trim, move on a timeline

• Export

That’s it.

No magic.

No dark patterns.

No lock-in.

Is this a good business?

Honestly? I don’t know yet.

But I do know this:

• People are tired of gates

• People miss simple tools

• People want ownership again

If this resonates with even a small group of creators, indie hackers, teachers, devs, or parents making quick videos — that’s enough.

I didn’t build this to win a category.

I built it because I was annoyed.

And sometimes, that’s the best reason to build anything.

If you’re curious, it’s live.

If you hate it, that’s fair.

If you wish more tools worked like this — then we think the same way.

Check it out: QuickEditVideo.

We’ve shipped v0.1.16 🎉
This is a small but meaningful update focused on making the file panel and timeline feel cleaner, safer, and more intuitive.

🐛 Fixed: Long Filename Layout Issues

What Was Happening

Very long filenames could break the file panel layout, causing:

• Text spilling outside the panel

• UI elements overlapping

• Filenames becoming hard to read

• A generally messy look

What’s Fixed

The file panel now handles long names properly:

• Filenames are truncated with ellipsis

• Hover tooltips show the full name

• Spacing stays consistent

• Overall UI looks cleaner and more professional

No more layout explosions from long filenames.

✨ New: Delete Files Directly from the File Panel

Why We Added This

Before, cleaning up unused files meant awkward workarounds outside the editor. That made it easy for projects to fill up with junk.

What You Can Do Now

You can delete files right inside the file panel:

• Inline delete button per file

• Confirmation dialog to avoid accidents

• Instant project update after deletion

• Much easier to keep projects tidy

How It Works

1. Open your project

2. Find the file in the file panel

3. Click the delete icon

4. Confirm

5. File gone 👍

Simple and fast.

🔒 Smart Deletion (No Broken Timelines)

To keep your project safe, deletion comes with guardrails:

• Files in use on the timeline can’t be deleted

• Clear warnings explain what’s still referencing the file

• You’ll need to remove those elements first

• No broken clips, no missing assets

This keeps your timeline predictable and intact.

📊 New: File Metadata at a Glance

You can now quickly inspect file details from the file panel:

• Images: width & height

• Videos: duration & resolution

• Audio: duration & format

• All accessible via a small dropdown

This makes it easier to pick the right asset without opening files one by one.

🎞️ New: Video Frame Previews in Timeline Tracks

Timeline tracks now show actual video frame thumbnails instead of generic blocks:

• Visual previews embedded in clips

• Easier to tell similar clips apart

• Faster navigation in complex timelines

• Better sense of visual flow

It’s a small change that makes the timeline feel much more “editor-grade”.

⛔ New: Clip Duration Boundary on Video Tracks

Video clips on the timeline now respect the actual duration of the source file:

• Dragging the right edge of a video clip is capped

• You can’t extend a clip beyond the video’s real length

• No more confusing “empty” video regions

• Timeline behavior is more predictable and accurate

This prevents accidental over-dragging and keeps edits aligned with real media.

As always, feedback is welcome.
Thanks for using QuickEditVideo — and happy editing 🎬

We've shipped v0.1.15, bringing a critical fix to editing history and a big upgrade to how you pick and reuse colors. This release makes everyday editing smoother, faster, and far more predictable.

🐛 Fixed: History Pollution During Editing

What Went Wrong

A bug caused hundreds of history entries to be created while scrubbing or adjusting element properties (like text labels) in the sidebar.

This led to:

• Undo/redo stacks filled with meaningless micro-steps

• Sluggish performance as history grew

• Having to press Ctrl + Z dozens—or hundreds—of times

• An overall “broken” editing feel

What’s Changed

Editing behavior now matches how professional tools work.

• Live updates no longer touch history

• Only the final result is recorded

• One edit = one history entry = one undo

How It Works Now

1. While adjusting
   Changes update instantly, without creating history entries.

2. When you finish
   The final state is saved as a single, meaningful history step.

3. Undo / Redo
   Works exactly as expected—clean and predictable.

The result: faster editing, better performance, and an undo stack you can actually trust.

🎨 New & Improved Color Panel

We’ve also redesigned the color experience to reduce friction and speed up common workflows.

Clearer Icon, Faster Access

The old palette icon has been replaced with a color pie icon, making the color tool easier to spot and recognize at a glance.

Solid Color Presets

Apply common colors instantly with built-in solid presets—no picker required. Perfect for quick edits and simple designs.

Project Color Memory

QuickEditVideo now automatically remembers every color used in your project and surfaces them in the color panel.

This helps you:

• Keep colors consistent across elements

• Reuse colors instantly

• See your project’s palette at a glance

Advanced Color Picker

Need full control? Click the ➕ button in the project colors section to open the advanced picker:

• Hue slider for base color selection

• Brightness control for lightness adjustment

• Direct hex input for precision

• Live preview as you tweak values

This layered approach—presets → project colors → advanced picker—keeps things fast for simple tasks and powerful when you need precision.

📱 Mobile Improvement: Always-Visible Close Button

On mobile devices, the sidebar now always displays a close button, making it easier to dismiss panels and return to your canvas.

This small change improves navigation flow on phones and tablets, ensuring you're never stuck with an open sidebar blocking your view.

Try it now at https://quickeditvideo.com/app/
No paywalls. No friction. Just better editing. 🎬

We’ve released v0.1.14, focused on making QuickEditVideo smoother and more reliable on mobile devices.
If you edit on your phone or tablet, this update removes several frustrating layout issues.

What’s Fixed on Mobile 📱

✅ Sidebar Displays Correctly

The sidebar could previously disappear, overlap content, or break the layout on smaller screens.
This has now been fully fixed.

• Sidebar renders consistently across screen sizes

• No more layout shifts or hidden panels

• Improved touch-friendly spacing for mobile interaction

✅ Timeline Tracks Render Properly

Timeline tracks now display correctly on mobile devices, making playback and editing more predictable and usable on smaller screens.

• Tracks no longer overlap or collapse

• Layout adapts smoothly to phones and tablets

• Editing feels consistent with desktop behavior

Known Limitation: Mobile Video Export 📝

Editing on mobile is now smooth—but there’s one important limitation to note:

Video export is not yet supported on mobile browsers.

This is due to a current limitation in @remotion/web-renderer, which does not fully support mobile environments. You can:

• Edit your video on mobile

• Save your progress

• Switch to desktop to export the final video

We’re actively monitoring upstream improvements and will enable mobile export as soon as it’s technically viable.

Why This Matters

This release is part of our ongoing effort to make QuickEditVideo truly cross-device:

• Edit anywhere

• Pick up where you left off

• Export when you’re ready

Give it a try on your phone or tablet and let us know how it feels. Your feedback directly shapes what we ship next 🚀

Hey Indie Hackers 👋

We recently rolled out a major upgrade to one of QuickEditVideo’s most used features: Text-to-Speech.

Our editor now runs on Kitten TTS Nano 0.2, a neural TTS model that delivers noticeably better voice quality without slowing things down.

Why We Made the Switch

One of our goals with QuickEditVideo is to help creators ship content faster—with fewer hurdles. Many of our users rely on TTS to generate narration for explainer videos, tutorials, or story-driven clips.

But our previous TTS setup had trade-offs: serviceable, but not always natural. We wanted speech output that could feel human enough to blend seamlessly into YouTube videos, social posts, or educational content. That’s why we jumped to Kitten TTS.

What’s Changed?

• Cleaner Audio: The new model produces more natural-sounding speech with better clarity and pronunciation.

• More Expressive Voices: The delivery feels less robotic and more human-like.

• Zero Downgrade: Processing time and performance remain basically unchanged.

• No Breakage: We swapped the engine under the hood without changing the workflow—so users don’t have to relearn anything.

About Kitten TTS Nano 0.2

It’s a compact but powerful neural TTS model from KittenML. Designed for production environments, it balances:

• High-quality voice synthesis

• Efficient runtime (good for browser-based workflows like ours)

• Robust handling of various text inputs

Basically: better quality without heavier costs.

The Impact for Creators

If you’ve tried our TTS before, you’ll immediately notice the difference—voices are smoother, clearer, and easier to listen to. If you’re new, it’s the best version yet.

No action required—every new generation is already running on Kitten TTS Nano 0.2.

What’s Next?

• Expanding the voice library (more accents, tones, and personalities).

• Giving creators control over pacing and emphasis for even more natural output.

• Exploring multi-language support as a priority.

Our north star is simple: make it possible to edit videos as easily as editing text—TTS included.

👉 Try it now: QuickEditVideo Text-to-Speech

Would love to hear your feedback on how the new voices compare—and if you’d use them for your own projects.

Hey Indie Hackers,

I’ve been building QuickEditVideo.com as a free, no-login tool for creators who need lightweight but powerful editing and AI audio features.

Over the past few weeks, I kept hearing the same feedback:
👉 “I need more natural pacing.”
👉 “I wish I could slow down / speed up the voice.”
👉 “Can I just feed in my subtitles and get a voiceover automatically?”

So, I rolled up my sleeves and shipped four major TTS upgrades that I think you’ll love:

🎯 1. Pause Markup for Perfect Timing

Insert [pause] anywhere in your text to add natural breaks. Great for suspense, emphasis, or just making your voiceovers sound less robotic.

Example:
Welcome to our presentation. [pause] Today we’ll cover three topics.

🔄 2. Smoother Transitions Between Pauses

I rebuilt the audio stitching pipeline. Now pauses flow naturally with intelligent fade-ins, breath simulation, and context-aware timing. No more jarring cuts.

⚡ 3. Adjustable Speech Speed

Control pacing with settings from 0.5x (slow, detailed lectures) to 1.5x (fast, energetic intros). The AI adapts intonation and clarity so it never sounds distorted.

🎬 4. Brand New: SRT-to-Speech Tool

Upload your .srt subtitle file → get a natural AI-generated voiceover that matches timing perfectly. You can export individual clips or one combined audio file.

This is huge for creators with existing video content—turn subtitles into podcasts, accessibility audio, or alternate voiceovers instantly.

Why This Matters for Builders

• Educators → Turn lessons + subtitles into study audio

• YouTubers/Podcasters → Faster workflows, pro-level pacing

• Accessibility advocates → Make visual content audio-friendly

• Indie hackers → Repurpose content into new formats with zero extra cost

🛡️ Bonus: Privacy First

Everything runs in your browser. No uploads. No accounts. Unlimited.

💡 Try it out:

• Blog post with full details

• Try the enhanced Text-to-Speech tool with pause and speed controls

• Convert SRT subtitles to speech with our new dedicated tool

• Read our complete SRT conversion guide for detailed tips and best practices

Would love to hear from you—what’s the next killer feature you’d want in a free browser-based TTS tool?

Last week I stumbled on a Reddit post where someone was asking for a simple online tool to turn subtitle .srt files into speech. I couldn’t believe there is no a good solution out there, so… I built one.

Day 1

I hacked together a minimal prototype by porting KittenTTS into a browser runtime. That gave me basic text-to-speech working in the browser — no servers, no uploads, fully private.

Day 2

I added subtitle support. You can now drop in an .srt file and generate audio that perfectly aligns with your captions.

A few extras I snuck in along the way:

• 🎶 Queueing – feed in longer subtitle files, no problem.

• ⏱ Auto-fit – voice automatically fits within each subtitle’s duration.

• ⚡ Manual speed control – adjust playback speed per subtitle line.

• 📦 Output options – download as individual clips in a ZIP, or merge into one MP3 that matches your SRT timings.

Right now it’s:

• ✅ Free & unlimited

• ✅ Runs entirely in your browser (private, no uploads)

• ✅ No paywall, no login required

• ✅ English only (for now)

👉 Try it here: https://quickeditvideo.com/srt-tts/

Would love feedback from anyone who works with subtitles, captions, or accessibility tools. What features would you want next?

Hey Indie Hackers,

I just shipped a new feature for QuickEditVideo.com: in-browser text-to-speech powered by a small but surprisingly capable open model called KittenTTS (15M parameters):

👉 You can try it right now here: QuickEditVideo.com/tts

🔧 Background

When building QuickEditVideo, I often needed quick narration or voiceovers for clips. Most TTS solutions I tried were:

• Cloud-only (expensive + slow)

• Proprietary (black box models)

• Or simply too heavy to run in-browser

So I decided to integrate a lightweight, functional, open TTS model directly into the browser.

✨ What’s new in this release

On top of making KittenTTS run locally, I’ve added some quality-of-life features:

• WASM → Turn original Python implementation into JS+WASM, making it fully functional in the browser.

• Queueing → Handle multiple text tasks smoothly without blocking main UI thread.

• Task history → Reuse and manage your generated audio.

• Performance improvements → Optimized for faster inference in-browser.

• Text auto-chunking → Splits and sanitizes long text into chunks automatically.

The result: you can paste text, hit generate, and get a voiceover within seconds, no server round trips.

🌟 Why this matters

• Runs in your browser — no API keys, no logins, no data sent to servers.

• Small model, big usability — 15M parameters sounds tiny compared to giants, but it’s fast and good enough for many voiceover needs.

• Open & hackable — I want indie devs and creators to actually see how things work, not just consume from a black box.

🔮 Next steps

• More voice presets and styles

• Export audio directly into QuickEditVideo’s video timeline

• Potential premium voices for those who need studio-level polish

👉 You can try it right now here: QuickEditVideo.com/tts

I’d love feedback from IH:

• Would you use in-browser TTS for quick prototyping / voiceovers?

• What’s more important to you — speed, voice quality, or cost?

Thanks for reading, and I hope some of you try it out!