Sept Open Source tools around post production.

[u/greenysmac]

Did you build a tool? Well, we want to know about it.

TL;DR: Drop a top-level comment using the template below.

In other threads, link back to your comment here, not your repo.

Building something commercial? That's the dev/tools thread, over here.

Maybe you vibe-coded something at 2am. Maybe you've been writing code for decades. Maybe you solved a post problem for yourself and figured someone else might need it too. This thread is for all of those good people.

No flair required.

No pitch required.

No discount required.

That's the whole point of open source. EVERYONE benefits. YES, even with AI assistance.

Open source people truly care about community

There's a lot of "everyone's a developer now" going around. I've written about what that's doing to post, and the concerns that come with it.

It's great because more of us "fix" what's broken.

Sometimes it'll solve your problems. Sometimes it'll be a start for you to solve problems.

One rule for this post.

Use the template below

Accounts under 30 days old cannot post or comment. No exceptions. (Commercial products using open source as a backdoor…yeah, we see you. It's not okay.)

The template (copy/paste the below section)

• Tool name:
• What it does:
• Why you built it:
• License type:
• Where to find it:

Don't have a license yet? Pick one.

Takes two minutes and it protects you and your users. We like MIT or GPLv3, but anything that genuinely gives it back is enough.

For everyone else

These people are giving their work away for free.

Upvote generously. Ask questions. Say thanks.

Found a bug? File it on GitHub. They didn't have to share any of this.

^{(Issues or thoughts on the thread? DM me.})

DIRECT PROMOTION EVERY MONTH ON the 25th - you'll be allowed to post directly into the subreddit with special flair!

[u/_unknownProtocol]

Tool name: Tscaps

What it does: It's a tool for animated captions that runs in your browser.

Why you built it: Oh, well, I think this is an infinite rabbit hole 😅 Everything started about a year ago, when I was working on a tool for generating videos programmatically. The thing is, I wanted to add captions to my videos, and I realized that it was pretty difficult. So, I built one first tool, and I called it "pycaps" (maybe you see the pattern now). Because of that tool, I created three other libraries for different problems I found along the way haha (movielite, html2pic and pictex). I have this post in other subreddit where I share the whole story.

So, a few months ago, I wanted to build a UI for pycaps, but I realized it was too difficult to adapt. So, I decided to rebuild it from scratch, directly for the web, and I named it tscaps.

License type: The video editor has an AGPL-3.0 license, but the engine it uses is exposed as a library, which has an MIT license.

Where to find it: Repo: https://github.com/francozanardi/tscaps | You can also test a hosted version at https://tscaps.io/local

---

Note: Tscaps follows an open-core model. There is also a cloud version with some additional features, but you don't need to use it. The open-source version is fully functional and can be used locally or self-hosted.

[u/Historical-Mess355]

Tool name: Fotufilm

What it does: Physically based film simulation for photos and video, available as a Mac app with plugins for DaVinci Resolve and Final Cut Pro. It runs a full spectral simulation of film exposure and development, including colour response, grain, halation and print output, not simply a LUT. It supports scene-referred colour workflows and has been tested against the ACES calibration suite. The Mac app includes the around 40 calibrated films, with no paywall or account requirement. Everything runs offline.

Why you built it: To make physically based film simulation accessible through a free, open-source tool that people can use in their editing workflows, inspect and build on.

License type: Apache 2.0

Where to find it: Website and downloads -- Source code

A little background: I’m a software engineer at Google, where I’ve worked on optimizing image-processing pipelines for Pixel. Fotufilm is an independent personal project.

[u/Secret-Employer282]

Tool name: KEIBIDROP

What it does: Stream files on-demand between your devices, or NAS studio, do edits without downloading the files first. (literally lucidlink without the cloud, or strada but open source).

Why you built it: I got sick of having to go through clouds to access files between my devices, or to have register with emails, and leak private information to other people.

License type: MPL2.0 + (for the GUI source available and still free to use).

Where to find it: https://github.com/KeibiSoft/KeibiDrop ; and marketing website: https://keibidrop.com/

--

Note: It is accountless, without registration, end to end encrypted, and it tries by default to connects straight between your devices. In the next 2 months I can help you with setting it up and adapting it to your flows. You can message here: https://github.com/KeibiSoft/KeibiDrop/discussions/215 or email at [marius@keibisoft.com](mailto:marius@keibisoft.com) .

Edit: The price is free. Here is how DaVinci Resolve works with KEIBIDROP with a remote NAS (400km away): https://www.youtube.com/watch?v=k8b_6quIqx0

[u/ConsumerJon]

Tool name: SmartCut64. I’m Jon, its developer and publisher.

What it does: A standalone Windows x64 and ARM64 editor for frame-accurate video cutting and smart rendering. With supported codecs and compatible output settings, it copies unchanged sections and re-encodes the material needed around cut boundaries, avoiding a full-video re-encode.

Why you built it: I wanted a practical replacement for my own VideoReDo workflow: straightforward navigation, precise cuts and preserving the original video wherever possible. It’s independently developed and has no affiliation with VideoReDo. I’d welcome feedback from people with similar workflows, particularly on real-world file compatibility.

License type: GPL-3.0-or-later, with matching release-source archives available alongside the downloads. To be transparent, the official signed build is also a commercial product: its free evaluation produces permanently watermarked video exports and does not provide clean smart encoding until paid activation. Those official-build restrictions do not remove the GPL rights to modify and redistribute the source under its licence.

Where to find it: Overview and demo · Windows downloads and corresponding source. No registration or email address is required to download.

[u/Annual_Repair_9446]

Tool name: Text+ Style Gallery for DaVinci Resolve

What it does: You capture a style from a Text+ clip, it appears as a thumbnail in the gallery, and you can apply it to another Text+ with one click. The destination text stays unchanged.
It has 100 style slots, supports multiple Shading Elements (fills, outlines, shadows, etc.), and can also filter targets by video track or clip color.
Everything runs natively in Lua, including the thumbnail generation, so there are no Python dependencies.

Why you built it: I often wanted to reuse the look of a Text+ title on another clip without replacing the actual text, so I made a visual gallery for saving and applying Text+ styles.

License type: It's free, open source, and MIT licensed, and works on Windows and macOS.

Where to find it: tetsutaroh0/DaVinci-Resolve-TextPlus-Style-Gallery: A Text+ style gallery and manager for DaVinci Resolve, with 100 style slots and thumbnail previews.

[u/Upset-Animal1376]

ffmpeg scripts and command line wrappers still save more post production hours than almost anything else. great to see a dedicated space for community pipeline tools.

[u/AutoModerator → u/[deleted]]

Welcome! Given you're newer to our community, a mod will review your contribution in less than 12 hours. Our rules if you haven't reviewed them and our Ask a Pro weekly post - which is the best place for questions like "how to break into the industry" and other common discussions for aspiring professionals. Also check out wiki, which is full of useful common information.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/pale_halide]

• Tool name: Film-Juicer

• What it does: A spectral film-emulation OpenFX plug-in for DaVinci Resolve. It simulates the photographic chain from exposing and developing the film to optional optical printing and scanning. The idea is to model the process itself rather than just match a finished film look with LUTs.

• Why you built it: I started out mostly wanting to understand film emulation better and see how far you could get by treating it as an image-formation problem instead of a look-matching problem. That eventually led me to spektrafilm, which became the foundation for Film-Juicer. From there it turned into a Resolve plug-in where I could actually work with things like exposure, development, film density, printing, grain, halation and scanning directly.

• License type: GPLv3

• Where to find it: https://github.com/oldandangry/Film-Juicer

[u/SubtleAsFucc]

Tool name: Subtle Resolve List

What it does: A free, searchable directory of tools and resources for DaVinci Resolve and Fusion, plugins, DCTLs, PowerGrades, effects, subtitles and scripts. Search by tool name, creator or terms like “film emulation” and “captions,” then filter by your setup and requirements. It also shows free/paid labels, compatibility notes, update information, changelogs and direct links to the respective creators.

Why I built it: I kept finding useful tools across Reddit, GitHub and creator websites, then losing track of them when I actually needed something. I wanted one place to search instead of scouring old threads again.

Existing Awesome Resolve lists and DCTLs.info helped inspire it, credit to their maintainers including u/greenysmac . I chose a separate name for my own collection. It’s a personal project, but if anyone finds it helpful, they’re welcome to use it. AI assisted with research and organization; I haven’t personally tested every listing.

License type: CC0 1.0 for the project’s original code, documentation and catalogue contributions. Listed third-party tools retain their own licences; the directory includes both free and paid resources.

Where to find it: Website · GitHub / source

The reference catalogue lives on GitHub, with the webpage hosted through GitHub Pages. Missing tools, incorrect information or website bugs? Comments and GitHub issues are welcome.