ayoisaiah

f2: Cross-Platform Batch File and Directory Renaming

F2 is a Go command-line tool for quickly and safely batch-renaming files and directories across platforms. Its dry-run default, conflict checks, metadata-based variables and undo support suit people who need to rename large or varied collections with control.

Stars
2.5k
Forks
67
Stars, last 30 days
+6
Last commit
2 days ago
Contributors
5

Our take

Activeregular commits and releases

Health score

32/100

How it is scored
Activity
47
Community
17
Issues
21
Pull requests
43

+6 stars in the last 30 days

F2 is an actively maintained, focused renaming utility with useful safeguards, though its development is highly concentrated in one contributor.

Good fit if

  • You want a cross-platform command-line workflow for renaming files and directories in bulk.
  • Previewing changes, conflict checks, metadata-based names or undo are important to your workflow.
  • You are comfortable installing a Go command-line tool and using its documentation for advanced workflows.

Look elsewhere if

  • You need a graphical renaming interface rather than a command-line tool.
  • Your team requires development and maintenance to be spread across multiple core contributors.
  • You need an issue history that demonstrates recent issue closure; the health data reports no issues closed in the recent review period.
All health signals
Last commit2026-11-11 (2 days ago)
Commits, last 90 days14
Releases, last 12 months1 (latest nightly, 2026-11-12, pre-release)
Contributors5 (top contributor: 99% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days1
Project age6 years

Checked on 2026-11-14 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

2,461

Forks

68

Change since Nov 17, 2026: -1 stars·0 forks

Overview

F2 is a cross-platform command-line tool written in Go for batch-renaming files and directories. It helps users handle renaming jobs quickly while reviewing proposed changes and checking for conflicts before applying them.

It supports simple replacements as well as regular expressions, and can use file attributes such as image EXIF data and audio ID3 tags to build new names. The dry-run default and undo functionality make it useful when a rename needs to be checked or corrected safely.

Key Features

  • Previews changes by default with a dry run.
  • Renames files and directories using string replacements or regular expressions.
  • Uses file attributes, including EXIF data and ID3 tags, as naming variables.
  • Checks operations for conflicts and can automatically resolve detected conflicts.
  • Supports undoing a completed renaming operation.
  • Handles renaming jobs involving thousands of files, according to the project documentation.
  • Includes workflows for file pairs, CSV-based renaming and sorting.

Use Cases

  • A photographer can organize an image library using EXIF attributes such as capture details.
  • An audio collection owner can rename tracks using embedded ID3 tags.
  • A user tidying a large folder can preview and apply consistent replacements or regular-expression rules in bulk.
  • Someone managing paired files or a CSV-driven rename list can use the documented pair-renaming and CSV workflows.

What you need

Detected in the repository

  • Node.js (from package.json)
  • Go 1.27.3 or newer (from go.mod)
  • A Dockerfile, so it can run in a container
  • Automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install with Go 1.23 or later:

go install github.com/ayoisaiah/f2/v2/cmd/f2@latest

See the README and getting started guide for other installation options and usage details.

Considerations

The project is active, with regular recent commits and a release in the past year, but the measured contributor activity is heavily concentrated in one person. Teams adopting it should account for that maintenance concentration. The repository requirements data lists Go and Node.js runtimes and Docker, while the README's Go installation path specifies Go 1.23 or later. The requirements data does not indicate tests, so adopters who need a verified test suite should investigate the repository further. The project is licensed under MIT; review the license for obligations when redistributing or incorporating it.

Found this useful?

Share it with someone who would like f2.