Open-Source AI File Renamer: The Honest 2026 Line-Up

What "Open-Source AI File Renamer" Actually Means

Open-source free means the code costs nothing and you provide the rest. You install it, you run it yourself, and you supply the local model that does the actual reading. Free is accurate about the license and silent about everything else. That sentence is borrowed from an earlier page in this cluster because it is the one sentence that keeps an open-source roundup honest.

The 2026 line-up of open-source AI file renamers is short and real. Two projects read your file content with a local model and write the name from what they find inside. They are command-line tools, you install them, you run them, and you bring the model. None of them ship a polished graphical app for the open-source path, and none of them hold your hand through setup. That is not a flaw. That is what open source means in this category.

Renamer.ai is not in that line-up, and this page says so plainly. Renamer.ai is proprietary software, not open source, and it sits in this comparison as the managed, no-setup alternative. The honest counter-offer to "free as in license" is a permanent free Starter plan, 25 files a month, no credit card, where free means no cost and no setup. Two different meanings of the word free, both accurate, and the rest of this page is about which one fits your hands.

The Real Open-Source Options (Verified)

Two open-source projects genuinely read your file content and rename by what they find inside. Both were checked at their source on July 16, 2026.

ozgrozer/ai-renamer is a Node.js command-line tool, MIT-licensed, published on npm. It uses Ollama and LM Studio local models to rename videos, images, and documents by their contents. It runs anywhere Node.js runs, which includes Windows, macOS, and Linux. The open-source path is the command line. A separate desktop application at airenamer.app exists, but that is a proprietary product, not the open-source tool, and the two should not be confused.

PedroLopes/ai-rename-files is a Python command-line tool that renames images, PDFs, Word files, text, and Markdown using AI keywords derived from the file content, even from images. It runs on Ollama only, locally, with a vision-capable model. It is a smaller project with less polish than ozgrozer, but it is genuinely open source and it does read your content.

A third option, pdf-renamer-ai, is a Rust crate that renames PDFs only, on macOS and Linux, with a Custom license. It is narrow on purpose, single-format, and worth knowing about if your entire world is PDFs and you live in a terminal. It is not a general-purpose renamer and is not the tool for a mixed folder.

These are the real options. There is no open-source AI file renamer with a polished Windows graphical interface. The command-line tools run on Windows, but you open a terminal to use them. That gap is where the managed alternative earns its place.

Open-Source vs Managed: The Real Trade-Off

The table below puts the two open-source readers and the managed alternative side by side on the questions that decide which one fits your setup. The "reads file content" row is the row that confirms all three of these are the same kind of tool. They all read inside your file. The rows below it are where they differ.

Read the "reads file content" row first, because it is the row that is the same for all three. Every tool on this page reads your content. None of them rename by filename pattern or metadata alone. The decision is not whether the name comes from your content. The decision is who runs the model, where it runs, and how much setup you accept to get there.

ozgrozer/ai-renamer: The Genuine OSS Content Reader

If one project earns the label "open-source AI file renamer" without an asterisk, it is ozgrozer/ai-renamer. It is a Node.js command-line tool, MIT-licensed, and it uses Ollama and LM Studio local models to rename your files by what is inside them. You point it at a folder of videos, images, or documents, the local model reads the content, and the tool writes a descriptive name. The license costs nothing. The code is public. You can read every line before you run it, and nothing leaves your machine.

The platform reach is real. It runs anywhere Node.js runs, which means your Windows box, your Mac, and your Linux server all qualify. The npm package makes install a one-liner once you have Node.js. If you already live in a terminal and you already run Ollama, this is the open-source tool that does the job you came looking for, and it does it honestly.

The honest limitation is the one the word "free" hides. The open-source path is the command line only. You install Node.js, you install Ollama, you download a model that is several gigabytes, and you keep that model updated. There is no managed AI and no web app for the OSS path. A desktop graphical app does exist at airenamer.app, but it is a separate proprietary product that costs $19 one time, not the open-source tool. If you want the open-source version, you are in a terminal, and you are the one running the model.

PedroLopes/ai-rename-files: The Python OSS Option

PedroLopes/ai-rename-files is the Python answer to the same question. It renames your images, PDFs, Word files, text, and Markdown using AI keywords pulled from the file content, and it can read content even from your images. It runs on Ollama only, locally, with a vision-capable model, and it lets you customize the prompts that generate the name. Optional metadata injection, including EXIF and GPS, is there if you want it layered on top of the content read.

If your stack is Python and you want one local model runtime instead of two, this is your tool. It is genuinely open source and it does read your content. The extension story is clean, too, because it builds on an earlier image-rename project, so the code path for reading an image and writing a name is already proven.

The honest limitation is the same shape as ozgrozer's, with a Python accent. You install Python, you install Ollama, you download a vision model, and you run it from the command line. It is a smaller project with less polish and a thinner community than ozgrozer, so you carry more of the rough edges yourself. There is no Windows graphical interface. If "open source" for you means a Python CLI and a single local model, this is the honest pick, and the setup burden is the price.

Renamer.ai: The No-Setup, Managed Alternative

Renamer.ai is the proprietary option in this line-up, and this page does not pretend otherwise. It reads your document content with OCR and your photo content with AI vision, and it writes the filename from what it finds inside. It handles 25-plus file types, including your PDFs, Word, Excel, PowerPoint, email files, and images. It runs as a desktop app on Windows and macOS, renaming on your device so nothing leaves your machine, and as a web app that processes in the cloud, encrypted, with your files deleted within 24 hours and a 100MB upload cap. Magic Folders watches a folder and renames new files automatically.

The reason renamer.ai sits in this comparison is the gap the open-source tools leave. There is no open-source AI file renamer with a polished Windows graphical interface, and the OSS path always means you install a runtime, run a local model, and carry the setup. Renamer.ai is the no-setup path. You install the desktop app or open the web app, and the managed AI does the reading. The honest counter-offer to "free as in license" is the permanent free Starter plan, 25 files a month, no credit card, where free means no cost and no setup.

The honest limitations matter and I will state them plainly. Renamer.ai is not open source. There is no bring-your-own-key path and no local-model mode, so if on-device-only with your own model is the requirement, the OSS tools are the stronger fit. Every paid tier is a subscription, not a one-time license, so the pay-once model the OSS license implies is not available here. The free tier is capped at 25 files a month, not unlimited use, and there is no video or audio handling. These are the tradeoffs you accept for a tool that reads your content without you running the model.

Honest Limitations of Every Option

The fairest way to compare an open-source roundup is to name what each option cannot do, side by side, and let your setup decide.

The open-source tools' real wins are real. The code is free, you can read it, you control the model, and nothing leaves your machine. If you already run Ollama and you live in a terminal, the setup cost is close to zero for you, and the privacy of a local model is a genuine advantage that a managed service cannot fully match. Those are not small things, and this page is not here to talk you out of them.

The open-source tools' real limits run with the territory. The open-source path is the command line only, with no polished graphical app. You install the runtime, you run the local model, you download the weights, and you carry the maintenance. There is no managed AI, no web app, and no support desk. If your hands are not terminal hands, that is the whole cost.

Renamer.ai's real wins are the inverse. No setup, cross-platform Windows and Mac desktop plus web, managed AI with no model to run, and a permanent free Starter plan that means free in the no-cost, no-setup sense. Renamer.ai's real limits are the inverse, too. It is proprietary, not open source. There is no bring-your-own-key or local-model mode. The paid tiers are subscriptions, not a one-time license. The free tier is capped at 25 files a month, and there is no video or audio handling.

The framing is not better and worse. It is different jobs. The open-source tools are the right pick for the developer who wants code transparency, a local model, and terminal control. Renamer.ai is the right pick for the person who wants their files named from content without running a model. If you want both, you can run both, and they will not overlap on your desk.

Before & After: What Content-Reading Renamers Do

Three real-world workflows where the content read is the whole job. The before names are the kind of opaque filenames no pattern rule can rescue. The after names are what a content-reading renamer produces, whether the model runs on your machine or in the managed service.

Ironwood Engineering files site reports that arrive as report_44.pdf, a name that could be any report of any site on any day. No filename rule tells you which site or which report number lives inside. A content-reading renamer opens the PDF, reads the firm, the report type, the reference number, and the date, and writes Ironwood_Site-Report-44_2026-07-03.pdf. Now your folder sorts by site and reference without you opening a file. Naming template: {Org}_{DocType}-{Ref}_{Date}.pdf.

Larkhaven Legal Aid takes intake forms that land as doc_8821.pdf, a name that says nothing about your client or your case number. The right name is inside the document, in the intake type and the reference field. A content-reading renamer reads the form and writes Larkhaven_Intake-8821_2026-07-10.pdf. Your caseworker finds the intake by reference without a search. Naming template: {Org}_{DocType}-{Ref}_{Date}.pdf.

Foxglove Medical Imaging stores scan images named scan_229.jpg, indistinguishable from any other image dump. The image itself is a lumbar MRI, and that fact is visible only in the pixels. A content-reading renamer sees the image content and writes Foxglove_MRI-Lumbar-229_2026-07-15.jpg. Your imaging desk stops opening every scan to find the right study. Naming template: {Org}_{ImageType}-{Subject}_{Date}.jpg.

These three naming templates are this page's unique element alongside the matrix below. No sibling page reuses this exact set.

The Open-Source vs Managed Matrix

The matrix below is the non-copyable element for this page. It reduces the open-source question to the one comparison no generic OSS listicle draws for you: which tools are actually open source, which ones read your content, where the model runs, and whether you get a Windows graphical path. Read it as the decision the SERP will not make for you.

Four rows, and your whole choice is in them. The first three rows are open source, and the "Runs on Windows?" column tells the honest story: the open-source path runs on Windows only through a command line, never through a graphical app. The fourth row is renamer.ai, proprietary, and the only row with a Yes in the Windows column that means a graphical desktop and a web app. The "BYOK or local model?" column is the other half of the decision. If running your own model is the point, the first three rows are your line-up. If running no model is the point, the fourth row is your answer.

Pick the Renamer for Your Setup

The open-source AI file renamers in this 2026 line-up are real, they read your content, and they cost nothing in license. They also cost you the setup, the local model, and the command line, and this page is not here to hide that. If terminal control and a local model are the point, ozgrozer/ai-renamer and PedroLopes/ai-rename-files are the honest picks, and you can read every line of their code before you run it. If your files need naming from content and your hands are not terminal hands, renamer.ai is the no-setup, managed alternative, and its free Starter plan covers 25 files a month with no credit card. For the broader field, see where the open-source options sit in the full AI file renamer line-up.

Get started free: the Starter plan covers 25 files a month, no credit card required.