Website profiles · Technology insights · Alternatives

vifm.info

No paid content found
Visit website
Profile views 3 Outbound visits 1 Normal
Vifm Full homepage screenshot

At a glance

Category
Software & Apps
Language
English
Paid-content signal
No paid content foundObserved
Registered
2014
Hosting
Hetzner Online GmbHInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Vifm?

Vifm is a terminal-based file manager with a curses interface that behaves much like Vim. According to its own site, it gives users who already know vi "complete keyboard control over your files without having to learn a new set of commands," and it borrows some ideas from the mutt mail client as well.

Who it suits

  • Vim users who want file browsing to feel like editing: the same mappings, command-line mode with ranges and abbreviations, marks, and registers.
  • People who work over SSH or inside tmux/GNU Screen, since it runs in a terminal and has built-in integration with both.
  • Users who manage large or messy directories, thanks to advanced filtering and renaming, file decorations by type or name, and a less-like preview mode with customizable viewers.

What it offers beyond basic navigation

It supports one- or two-pane views within tabs, plus table, grid, tree, and Miller-style layouts. Its less common features include directory-tree comparison, undo/redo and backgrounding of operations, FUSE filesystem support, sessions, named bookmarks, and scripting configuration per directory. It is cross-platform (GNU/Linux, BSD, Solaris, Windows, macOS) and UTF-8 aware.

The trade-off

Vifm assumes comfort with Vim conventions; if you have never used vi, the keyboard model is a learning curve rather than a shortcut. One user quoted on the site, Carlos Pita, sums up the design philosophy: "If you don't know how to do it, don't look at the docs, just think how you would do it in vi." That is a strength for the vi-familiar and a barrier for everyone else.

A practical next step: if you already use Vim daily, install Vifm and try it on one project directory for a week before replacing your current file manager; if you don't use Vim, a simpler terminal file manager will likely cost you less time. The site's cheatsheets and Q&A section are the natural starting points for learning the keybindings. See Vifm for documentation and downloads.

How do I get started with Vifm if I already know Vim?

Start by installing Vifm from your package manager, then launch it with vifm in a terminal. Since you already know Vim, you can skip most of the tutorial phase: normal mode, h/j/k/l for movement, : for the command line, and Vim-style mappings and abbreviations all carry over. The page describes Vifm as a curses file manager built to give vi users "complete keyboard control over your files without having to learn a new set of commands," which is exactly the shortcut you're looking for.

A practical first session

Run vifm --help or open the in-app :help to confirm the version and see the default key list, then try these in a scratch directory:

  • j/k to move through entries, Enter to open a directory or file, h to go up.
  • : to open the command line, where Vim-like ranges and abbreviations work.
  • yy to yank a file, p to paste, and dd to mark for deletion (Vifm routes deletions through its trash rather than deleting outright).
  • v for visual selection, then : to run a command on the selected range.
  • Tab to switch between the two panes if you keep the two-pane view.
  • :q to quit, :w isn't needed—file operations apply immediately.

Where the Vim model bends

A few things differ enough to trip up muscle memory. Movement is over files, not characters, so counts and operators behave differently (d alone doesn't delete; dd does). The page also notes influence from mutt, which shows up in how marks, registers and the command line are used. View modes are a Vifm-specific concept: the page lists table, grid, tree and miller views, plus tabs for one or two panes. Your .vimrc does not apply—Vifm reads its own vifmrc, so port your key mappings there rather than expecting them to inherit.

Configuration worth doing early

The page highlights several features that reward a little setup:

  • Mappings and command-line abbreviations in vifmrc, mirroring the mappings you already rely on.
  • Sessions to save and restore a working set of directories and tabs.
  • Named bookmarks (tags) for directories you visit constantly.
  • Directory-specific scripting, so configuration changes when you enter certain folders.
  • Preview mode with customizable viewers, which behaves like less and is handy for inspecting files without opening them.

A sensible next step: open Vifm in a project directory, create one or two mappings for actions you repeat (for example, opening a file in your editor), and save it as a session. If you want a broader reference for terminal-based workflows, the Vifm documentation and cheatsheets linked from Vifm are the most direct source, and general Vim guidance from Vim applies wherever the commands overlap.

How can I customize Vifm with my own key mappings and color schemes?

Vifm is built for this: its page describes "Vim-like user mappings," a "Vim-like command-line mode with ranges and abbreviations," and "color schemes, which can also be applied to specific sub-trees." In practice, almost all customization lives in two text files you edit yourself — vifmrc for mappings and general behavior, and theme files for colors — so the workflow is closer to configuring Vim than clicking through a settings dialog.

Key mappings

  • Where they go: your personal vifmrc (the page also mentions the "ability to script configuration for specific directories," so per-directory overrides are possible).
  • How they look: mappings follow Vim's model — a key sequence on the left, a Vifm command or action on the right. Because the command-line mode supports ranges and abbreviations, a single mapping can drive multi-file operations rather than just "open this."
  • Practical pattern: bind the operations you repeat most — toggling panes, jumping to bookmarks (tags), starting a rename with your preferred editor, or launching a preview — and leave the rest at defaults. A large mapping file you don't remember is worse than a short one you do.

Color schemes

  • Where they go: theme files, selected in vifmrc; the page notes schemes can be applied to specific sub-trees, so one directory (say, a build output folder) can look different from the rest.
  • Beyond base colors: "file decorations" can be customized by type and/or name, which is how you make, for example, executables, archives or a naming pattern stand out without changing the whole palette.

Choosing an approach

Goal What to customize Trade-off
Faster navigation Mappings for panes, tabs, marks, bookmarks Too many mappings collide with Vim habits you rely on
Clearer file overview Decorations by type/name Over-decoration makes listings noisy
Context-specific clarity Schemes for specific sub-trees More files to maintain and keep consistent
Repeatable setups Scripted configuration in vifmrc Needs version control if you use several machines

A concrete scenario: a developer who already uses Vim keeps vifmrc in a dotfiles repository, maps a key to open the current file in $EDITOR, decorates executables and archives, and assigns a muted scheme to node_modules-style trees so they recede visually.

As a next step, start from a copy of the documented sample configuration, change one mapping and one color, and confirm both behave as expected before expanding. If you want to see how other terminal tools handle configuration for comparison, GitHub hosts many dotfile repositories you can read for structure ideas.

How does Vifm compare to other terminal file managers for everyday file navigation?

Vifm is aimed at people who already think in Vim: its main advantage for everyday navigation is that movement, marks, registers and command-line editing work the way your fingers expect from vi, so you spend effort on files rather than on learning a new key set. The page describes it as a curses-interface file manager with a Vim-like environment extended with ideas from mutt, and it lists two-pane and tabbed views, table/grid/tree/miller layouts, bookmarks, a less-like preview, filtering and renaming, and per-directory configuration.

Where it fits in everyday use

  • Muscle-memory navigation: if you use vi or Vim daily, jumping, searching and repeating commands carries over directly. One quoted user, Carlos Pita, sums up the appeal as thinking "how you would do it in vi" rather than reaching for the docs.
  • Heavy, repetitive file work: multi-block selection, advanced filtering and renaming, undo/redo and background operations matter when you are moving batches of files, not just opening one.
  • Remote and long sessions: built-in integration with GNU Screen and tmux, plus remote command execution, suits people working over SSH.
  • Customisation depth: colour schemes that can apply to specific sub-trees, file decorations by type or name, and scriptable per-directory configuration reward users who invest in setup. A quoted user, Aetet, describes it as fitting "like skin" after configuration.

Trade-offs against other terminal managers

Concern Vifm's position
Learning curve Low for Vim users, steeper for others; the Vim command-line mode with ranges and abbreviations is powerful but assumes familiarity
Everyday simplicity Richer than minimal two-pane managers; features like miller view, sessions and decorations add surface area
Configuration effort High ceiling, so benefits grow with the time you put into mappings and per-directory scripts
Platform coverage Cross-platform (GNU/Linux, *BSD, Solaris, Windows, Mac OS) and UTF-8 aware

Alternatives are worth weighing by workflow rather than feature count: ranger for a Python-extensible, preview-centric layout, nnn (hosted on GitHub) for a fast, minimal, plugin-driven approach, and Midnight Commander for a conventional two-pane, menu-driven feel closer to classic file managers.

Next step: try a week of real work in Vifm with only the Vim commands you already use, then judge whether its extra views and per-directory configuration earn their setup time; if you rarely touch vi-style commands, a simpler two-pane manager will likely feel faster day to day.

Can I use Vifm on Windows or macOS, and how do I install it there?

Yes. Vifm is cross-platform: the project lists Windows, macOS, GNU/Linux, *BSD and Solaris among supported systems, and it is described as a curses-interface file manager with a Vim-like environment. On Windows and macOS that means you run it inside a terminal, not as a graphical window.

What to expect on each platform

  • Windows: The practical route is a terminal that provides a curses environment. Windows Terminal plus a POSIX-like environment (for example MSYS2 or Cygwin) is the usual setup; Vifm's own site points to its Downloads page rather than to a package manager, so check that page for the current Windows build before installing anything else. Expect Vim-style keybindings to work as documented, but shell-related features (external commands, shell-like command-line editing) depend on which shell your environment exposes.
  • macOS: Install through a package manager such as Homebrew or MacPorts, or build from source. Vifm runs in Terminal.app or iTerm2. The built-in integration with GNU Screen and tmux mentioned on the site is useful here if you want to keep a session alive across terminal windows.

Installation steps that apply to both

  1. Open the Downloads page on Vifm and pick the package or archive matching your OS.
  2. Install it with your platform's package manager where one is offered, so upgrades stay simple.
  3. Launch vifm in a terminal and confirm the two-pane view appears.
  4. Copy the sample configuration (vifmrc) into your user config directory and edit it there rather than in the system-wide file.
  5. Add your own mappings gradually; the site's cheatsheets are the quickest reference for defaults.

Choosing between the two

If you already live in a Unix-like shell, macOS is the lower-friction choice because curses and shell integration are native. On Windows, decide first whether you want a full POSIX layer (more compatible, heavier) or a lighter terminal setup (simpler, but some shell features may behave differently). Either way, the payoff is the same: complete keyboard control over files without learning a new command set, as the site puts it for vi users.

A useful next step is to read the Q&A section on the site before installing, since platform-specific quirks tend to surface there first.

How do I report a bug or ask a usage question about Vifm?

Use Vifm's own support channels: the project asks that general usage questions go to its dedicated Q&A site (registration is involved), while bugs and feature requests go through its issue tracker. The site also lists a mailing list and a wiki for discussion and reference material.

Which channel to pick

Your situation Best channel
"How do I do X in Vifm?" (configuration, mappings, commands) The Q&A site linked from the Vifm homepage's Contact/Q&A section
Reproducible bug, crash, or feature request The bug/feature tracker linked from the site's "Reporting bugs" section
Open-ended discussion, patch talk, or announcements The mailing list
Looking for prior answers or recipes The wiki and cheatsheets

Making a bug report useful

Vifm is highly configurable, so most reports hinge on your setup. Before filing, gather:

  • The Vifm version (shown in the interface and in the site's news, e.g. the v0.14.5 release note) and your OS.
  • The exact keystrokes or : command that triggered the problem.
  • Relevant lines from vifmrc, plus any directory-specific config if the issue is location-dependent.
  • Terminal and multiplexer details if the problem is visual — Vifm integrates with GNU Screen and tmux, and curses rendering issues often depend on those.
  • Whether it reproduces with a minimal config, which separates a Vifm bug from a configuration mistake.

For usage questions, state what you tried and what you expected; Vifm's command-line mode, mappings, and marks follow Vim conventions, so mentioning your Vim background helps answerers pitch the reply correctly.

If you want background first, the official documentation at Vifm covers commands, options and scripting, and the cheatsheets are a fast way to check whether your question is already answered.

Related questions

More questions →
How Vifm's Vim-like Interface Works for Managing Files

Vifm is a terminal file manager with a curses interface that deliberately reuses Vim's interaction model: if you already use vi or Vim, you can navigate and manipulate files without learning a separate command set. The official site states this directly — "If you use vi, Vifm gives you complete keyboard control over your files without having to learn a new set of commands" — and one quoted user summarizes the design philosophy as: "If you don't know how to do it, don't look at the docs, just think how you would do it in vi." The trade-off is that the interface assumes prior Vim familiarity; users without it face a steeper start than with a menu-driven file manager.

The core mechanism: modes, mappings, and a command line

Vifm is not a Vim plugin or an embedded Vim — it is a standalone file manager that borrows Vim's conventions. The site lists these Vim-derived features:

  • Vim-like user mappings — you bind keys to actions the same way you would in Vim.
  • Vim-like command-line mode with ranges and abbreviations — commands are typed on a command line, can take ranges, and support abbreviations.
  • Vim-like marks and registers — you can mark locations and store things in registers, mirroring Vim's mental model.

In practice this means the habits transfer in both directions: motions and key sequences you already have in muscle memory do file-management work, and the command line behaves like the one you already know rather than a new mini-language.

What you actually do with it

The Vim-like layer sits on top of ordinary file-manager operations. Per the site, Vifm provides:

  • Two panes within tabs, plus table, grid, tree, and Miller-column views of files.
  • Multi-block selection, advanced file filtering, and renaming.
  • Undo, redo, and backgrounding of operations, plus directory-tree comparison.
  • Named bookmarks (tags) and sessions.
  • A less-like preview mode with customizable viewers.
  • File decorations customizable by type and/or name.
  • Color schemes, which can also be applied to specific sub-trees.
  • FUSE filesystem support and trash.
  • Built-in integration with GNU Screen and tmux, and remote command execution.
  • Cross-platform support (GNU/Linux, *BSD, Solaris, Windows, Mac OS) with UTF-8 awareness.

Where the Vim model pays off: scriptable, per-directory configuration

The feature with the clearest payoff for Vim users is that configuration can be scripted for specific directories. Combined with mappings, command-line abbreviations, and decorations that can target particular sub-trees, this lets you make behavior depend on where you are — for example, a directory of logs could get its own mappings or display treatment without affecting the rest of the filesystem. The site also notes shell-like and external command-line editing, so the command line is not a closed box.

Is it a good fit for you?

Your situation What to expect
You use vi/Vim daily The mappings, command line, marks, and registers should feel familiar; the main learning is file-manager-specific operations, not a new editing model.
You know Vim only casually The Vim-like layer helps, but the breadth of features (views, sessions, filtering, decorations) still needs the documentation.
You don't use Vim You can still use it, but the "no new commands to learn" advantage doesn't apply, and a conventional file manager may be quicker to start with.
You work inside tmux or Screen Built-in integration is listed as a feature, which fits terminal-centric workflows.

Practical starting points

  1. Confirm the version and platform. The site's news entry lists Vifm v0.14.5 (20 October 2026); supported platforms are GNU/Linux, *BSD, Solaris, Windows, and Mac OS.
  2. Read the cheatsheets before the full documentation. The site offers dedicated cheatsheets alongside documentation, themes, screenshots, and a Q&A section — the cheatsheet is the fastest way to map your existing Vim habits onto file operations.
  3. Ask general usage questions on the Q&A site. The site directs general usage questions there (registration required) rather than to the bug tracker; bugs and feature requests go through the reporting channels described on the page.
  4. Start with mappings and the command line. These are the two features that most directly carry over from Vim, so customizing them first gives you the quickest sense of whether the interface suits you.

The site does not publish pricing information, so treat availability and any distribution-specific packaging as something to check at the download source rather than assume.

What Is Vifm and What Kind of Program Is It?

Vifm is a terminal file manager with a curses interface that gives you a Vim-like environment for managing files and directories. It is aimed at people who already use vi or Vim: if you know those editors, you can control your files with the same keyboard habits instead of learning a new command set. It runs on GNU/Linux, *BSD, Solaris, Windows, and Mac OS, and is UTF-8 aware.

What Vifm actually is

Vifm is not a text editor and not a graphical file manager. It is a full-screen program that runs inside your terminal, draws a two-pane (or one-pane) file view, and lets you navigate, select, copy, move, rename, and delete files using Vim-style keys and a Vim-style command line. The project describes it as a file manager "extended with some useful ideas from mutt," the terminal mail client.

The practical consequence: your existing muscle memory for motions, counts, marks, and : commands carries over. As one quoted user puts it, the working rule is "if you don't know how to do it, don't look at the docs, just think how you would do it in vi."

Core capabilities

The feature list is broad, but these are the ones that shape daily use:

  • Vim-like mappings and command-line mode, including ranges and abbreviations.
  • Marks and registers, so you can jump between locations and store file references.
  • Multiple view layouts: table, grid, tree, and Miller columns, inside tabs.
  • One or two panes per tab, with multi-block selection for operating on groups of files.
  • Undo/redo and backgrounding for file operations, plus a trash.
  • Directory tree comparison, useful for spotting differences between two trees.
  • less-like preview mode with customizable viewers, so you can inspect files without leaving the manager.
  • Advanced filtering and renaming, including bulk rename workflows.
  • Named bookmarks (tags), sessions, and color schemes that can be applied to specific sub-trees.
  • File decorations customized by file type and/or name.
  • FUSE filesystem support and remote command execution.
  • Integration with GNU Screen and tmux, and per-directory configuration scripting.
  • Remembering the cursor position in previously visited directories.

Who it suits, and who it does not

Vifm is a good fit if you spend your day in a terminal, already think in Vim motions, and want file operations to feel like editing — including scripting behavior per directory and customizing the interface heavily. Users quoted on the project site describe it as central to their workflow and highly configurable.

It is a weaker fit if you want a mouse-driven graphical file manager, prefer discoverable menus over modal keybindings, or are not willing to learn Vim conventions. The design assumes familiarity rather than teaching it.

Getting started and where to look

The project site (vifm.info) links to News, Documentation, Cheatsheets, Downloads, Themes, Screenshots, a Q&A site, a Wiki, and a Mailing List. For a first run, the cheatsheets are the fastest way to map Vim habits onto file operations; the documentation covers configuration, mappings, and scripting. General usage questions are directed to the dedicated Q&A site, which requires registration.

The current release listed on the site is Vifm v0.14.5, dated 20 October 2026. The site does not state pricing or licensing terms in the material available here, so check the Downloads page for the exact terms before relying on any assumption about cost.

What file management features does Vifm offer?

Vifm is a terminal file manager with a curses interface that gives you Vim-like control over files. If you already use vi or Vim, you can navigate and manage files with familiar keyboard commands instead of learning a new command set. Its main file-management capabilities include one- or two-pane browsing within tabs, several file views, directory comparison, undoable and background operations, advanced filtering and renaming, bookmarks, and a trash feature.

Browsing and layout

Vifm supports a one-pane or two-pane view inside tabs, so you can compare two directories side by side or work in a single pane. Tabs let you keep several locations open at once. The program also remembers your position in previously visited directories, which helps when you return to a folder you were working in.

File views

Files can be displayed in several ways:

  • Table view — a conventional column layout.
  • Grid view — files arranged in a grid.
  • Tree view — a directory tree.
  • Miller view — a multi-column view that follows the Miller columns pattern.

You can switch between these depending on whether you want a compact listing or a structural overview.

Operations and safety

Vifm supports undoing, redoing, and backgrounding operations. That means a file operation can be reversed, repeated, or run in the background while you continue browsing. It also offers directory tree comparison, which is useful for spotting differences between two folder structures. A trash feature provides a recoverable place for deleted files rather than immediate permanent removal.

Finding and naming files

Advanced file filtering and renaming capabilities help when you need to narrow a large directory down or rename many files at once. Named bookmarks (tags) let you jump to frequently used locations without typing full paths.

Vim-style interaction

The interface follows Vim conventions: user mappings, a command-line mode with ranges and abbreviations, marks and registers, and scriptable configuration for specific directories. File decorations can be customized by file type or name, and a less-like preview mode with customizable viewers lets you inspect file contents without leaving the manager.

Practical fit

Vifm is cross-platform (GNU/Linux, BSD, Solaris, Windows, macOS) and UTF-8 aware. It also integrates with GNU Screen and tmux and supports FUSE file systems, remote command execution, and multi-block selection. If your workflow already centers on Vim keybindings and the terminal, these features are designed to fit that environment; if you prefer a graphical file manager, the curses interface is the main trade-off to consider.

How Customizable Is Vifm and How Does It Integrate with the Terminal?

Vifm is highly customizable for a terminal file manager: it offers Vim-like mappings and command-line mode, color schemes that can target specific directory sub-trees, file decorations by type or name, a less-like preview mode with configurable viewers, and per-directory configuration scripting. Its terminal integration includes built-in support for GNU Screen and tmux, remote command execution, FUSE file system support, and saved sessions. These capabilities come from the project's own feature list on vifm.info (current release noted there: v0.14.5, 20 October 2026); exact option names and syntax should be checked against the documentation and cheatsheets linked from that site.

Customization: what can you actually change?

Vifm's design goal is that if you use vi, you get full keyboard control over your files "without having to learn a new set of commands." That principle carries into configuration.

Area What the project lists Practical effect
Key mappings Vim-like user mappings Rebind navigation and file operations to keys you already use in Vim
Command line Vim-like command-line mode with ranges and abbreviations Run commands with ranges and short forms, similar to Vim's : line
Marks and registers Vim-like marks and registers Jump to marked locations and store reusable values
Colors Color schemes, applicable to specific sub-trees Style the whole interface, or only chosen directories
File decorations Customizable by file type and/or name Visually distinguish files by extension or filename pattern
Preview Less-like preview mode with customizable viewers Page through file contents and choose which program renders each file type
Filtering and renaming Advanced file filtering and renaming Narrow listings and batch-rename without leaving the manager
Layout One or two panes within tabs; table/grid/tree/miller views Match the view style to the task
Configuration scope Scripting configuration for specific directories Different behavior in different parts of the file system
Bookmarks Named bookmarks (tags) Label frequently used locations instead of remembering paths

Two of these are worth calling out because they go beyond typical file-manager settings. First, color schemes applied to specific sub-trees mean a project directory can look different from your home directory without a separate config file. Second, per-directory configuration scripting means behavior can change based on where you are, not just on global settings.

Terminal integration: where Vifm meets your environment

Vifm runs in a curses interface, so it lives inside your terminal. The project lists these integration points:

  • GNU Screen and tmux: built-in integration, so Vifm works within these multiplexers rather than merely running inside them.
  • Remote command execution: run commands on remote systems from within Vifm.
  • FUSE file systems: mount and browse FUSE-based file systems.
  • Sessions: save and restore working sessions.
  • Operation control: undoing, redoing, and backgrounding file operations.
  • Directory position memory: Vifm remembers where you were in previously visited directories.
  • Multi-block selection: select multiple blocks of entries for batch actions.
  • Cross-platform: GNU/Linux, *BSD, Solaris, Windows, and Mac OS, with UTF-8 awareness.

For a concrete scenario: if you work over SSH inside tmux, keep a session with your project panes open, and need to copy files between a local directory and a FUSE-mounted remote file system, Vifm's tmux integration, FUSE support, and backgrounded operations all apply to that single workflow. The site's feature list supports each of these as a capability; it does not document the exact commands, so consult the documentation and cheatsheets before relying on specific syntax.

How to evaluate whether it fits your workflow

  1. Check your editing habits. If you already use vi or Vim daily, the mapping and command-line model will feel familiar; the project explicitly frames this as its advantage.
  2. Identify your terminal setup. If you work inside tmux or GNU Screen, the built-in integration is relevant. If you use a plain terminal, the curses interface still applies, but the multiplexer features won't.
  3. List the customizations you need. Sub-tree color schemes, name-based decorations, and per-directory scripting are the less common options; confirm they match your actual needs rather than configuring for their own sake.
  4. Read the docs before configuring. The site links Documentation, Cheatsheets, Themes, and a Q&A Wiki. The feature list names capabilities, not option syntax, so the docs are where you verify exact settings.
  5. Start with a session and a preview viewer. These are low-risk ways to test the terminal integration and preview customization before building a larger configuration.

Common sticking points

  • Assuming the feature list is a manual. It describes what Vifm can do, not how to configure it. Use the documentation and cheatsheets for syntax.
  • Expecting GUI-style settings. Configuration is Vim-like and script-based, including per-directory scripting; there is no graphical preferences panel described on the site.
  • Overlooking scope. Color schemes can apply to specific sub-trees and configuration can be scripted per directory, so a setting that seems global may be overridden where you least expect it.
  • Skipping the Q&A site. The project directs general usage questions to its dedicated Q&A site, which is a better first stop than guessing at behavior.

For general questions about the program itself, the site's own framing is the clearest summary: a curses-interface file manager providing a Vim-like environment for managing files, extended with ideas from mutt.

Where to Find Vifm Documentation, Downloads, and Support

The official Vifm site (vifm.info) is the starting point for all of these needs. Its top navigation links directly to News, Documentation, Cheatsheets, Downloads, Themes, Screenshots, Contact, Q&A, Wiki, and Mailing List. Use Documentation and Cheatsheets for reference, Downloads for the program itself, and Q&A, Wiki, or the Mailing List when you need help or want to report something.

Documentation and quick reference

  • Documentation — the main reference for Vifm's behavior and configuration.
  • Cheatsheets — condensed command and keybinding references, useful once you know the basics and want to look things up quickly.
  • Wiki — community-written material that goes beyond the official docs.

The site's own framing is helpful here: Vifm is a curses-interface file manager that provides a Vim-like environment for managing files, extended with ideas from mutt. If you already use vi, the documentation will feel familiar — as one quoted user puts it, "If you don't know how to do it, don't look at the docs, just think how you would do it in vi."

Downloads and release information

The Downloads page is the place to get Vifm. Before installing, check News for the current release; the site lists Vifm v0.14.5 dated 20 October 2026. Vifm is cross-platform (GNU/Linux, *BSD, Solaris, Windows, Mac OS) and UTF-8 aware, so confirm you are picking the build for your system.

Seeing what it looks like before you commit

Two pages help you evaluate Vifm without installing it:

  • Screenshots — the interface and pane layouts.
  • Themes — color schemes, which the feature list notes can also be applied to specific sub-trees.

These are worth a look if you are deciding whether the curses interface and Vim-style workflow suit you.

Getting help and giving feedback

The site separates channels by purpose:

Need Where to go
General usage questions Dedicated Q&A site (registration mentioned on the site)
Community knowledge, tips Wiki
Discussion, announcements Mailing List
Reporting bugs, requesting features, other contact Contact page

The site explicitly asks that general usage questions go to the Q&A site rather than other channels, so start there for "how do I…" questions and reserve bug reports and feature requests for the appropriate contact route.

A practical first pass

If you are new to Vifm, a sensible order is: read the short description on the homepage, skim Screenshots and Themes to see whether the interface fits your habits, download the current release from Downloads, then keep Cheatsheets open while you work and turn to Documentation or the Q&A site when something is unclear. Users who rely on it daily describe it as highly configurable and central to their file navigation, which is a reasonable sign that the documentation and community channels are worth learning to use early.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 2014, this domain has about 12 years of history. That suggests continuity, although ownership and purpose may have changed. The domain uses the common .info extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by inhostedns.com, indicating managed DNS hosting. MX records point to the ukraine.com.ua email service. DNSSEC is enabled, allowing validating resolvers to authenticate signed DNS data. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header identifies nginx without an exact version. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies nginx without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No viewport meta tag was detected, which may affect mobile layout behavior. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 19 characters, within a common display range.

Hosting and Email

DNSinhostedns.com
HostingHetzner Online GmbH
Emailukraine.com.ua
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Finland flagHelsinki, Uusimaa, Finland Inferred 95.217.193.151

Registration details

RDAP / WHOIS

RegistrarHosting Ukraine LLC
Registered2014-07-15
Expires2028-07-15
Domain statusactive
Nameserversns16.inhostedns.com、ns26.inhostedns.net、ns36.inhostedns.org
DNSSECsigned

DNS records

DNS

TypeNameValueTTLPriority
Avifm.info95.217.193.151900—
AAAAvifm.info2a01:4f9:4a:50aa::1900—
MXvifm.infomx15.ukraine.com.ua90015
MXvifm.infomx20.ukraine.com.ua90020
NSvifm.infons16.inhostedns.com900—
NSvifm.infons26.inhostedns.net900—
NSvifm.infons36.inhostedns.org900—
TXTvifm.infov=spf1 include:_spf.ukraine.com.ua ~all900—
DSvifm.info2253 13 2 b5c054bae6b20d82e76d2d78ffb64780e6be4d45ecf90e4633fb8592db6aa2263600—
DMARC_dmarc.vifm.infov=DMARC1;p=none;rua=mailto:[email protected];ruf=mailto:[email protected];fo=1;900—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwww.vifm.info
IssuerLet's Encrypt
Valid until2027-01-19T23:17 · Remaining when checked: 89 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
servernginx

Identified technologies

nginx

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 1 allowed · 0 disallowed
  • Allow/
  • IntervalCrawl delay 10 seconds

No sitemaps found

User reviews (0)

  • No reviews yet.