How to Edit Files on a VPS: nano vs vim — Which to Use and When

Editing configuration files directly on the server is one of the most common tasks when administering a Linux VPS — tweaking nginx, modifying /etc/hosts, editing environment variables, configuring SSH. For those just starting out, the choice between nano and vim defines the experience: nano is friendly and feels like a regular text editor; vim is minimalist, modal, and has a reputation for being intimidating.

This tutorial compares both editors in practice, shows the essential commands for each one, and helps you decide which to use based on the type of task. The target audience is the beginner sysadmin or developer who connects via SSH to a VPS and needs to edit files without panic — whether it’s tweaking a single line quickly or working efficiently on large files.

Estimated time: 15 minutes to read and test the commands on a test VPS. If you just want to know which one to install right now, jump straight to “When to use nano vs vim”.

Prerequisites

Before choosing, confirm what’s already installed. On almost every official Ubuntu image, nano comes by default; vim usually ships in the “tiny” variant (without syntax highlighting). For production, it’s always worth installing the full version of whichever editor you’ll be using to avoid surprises.

Head-to-head comparison: nano vs vim

Both editors solve the same basic problem — editing files in the terminal — but they have opposite philosophies. This table summarizes the differences that matter for the decision.

nano wins on immediate accessibility: you open, edit, save, and exit without needing to consult a manual. vim wins on productivity once you master the shortcuts — operations like “replace string X with Y in the next 50 lines” or “delete everything inside these quotes” become two-key combinations.

Installation and basic setup

Before comparing usage, make sure both are installed on your VPS so you can test them.

sudo apt update

sudo apt install -y nano vim

sudo update-alternatives --config editor

nano — essential workflow

nano uses shortcuts visible in the footer of the screen. The ^ symbol means Ctrl, and M means Alt (Meta). The most commonly used commands:

nano /etc/nginx/sites-available/default

Ctrl+O    Save (Write Out) — confirm the filename with Enter
Ctrl+X    Exit — asks whether to save unsaved changes
Ctrl+W    Search text (Where) — Alt+W to find next
Ctrl+\    Replace — prompts for old and new text
Ctrl+K    Cut entire line
Ctrl+U    Paste cut line
Ctrl+G    Full help with all shortcuts

vim — essential workflow

vim is modal: you don’t type directly into the file until you enter insert mode. This is the biggest source of confusion for beginners.

vim /etc/ssh/sshd_config

Esc         Return to normal mode (always start here when in doubt)
i           Insert — type text at the cursor position
a           Append — type text after the cursor
o           Open — create a new line below and enter insert mode
v           Visual — select text (use arrow keys to expand)
:           Command-line — enter commands (save, exit, search)

:w          Save the file (write)
:q          Quit — fails if there are unsaved changes
:wq         Save and quit (the most-used combination)
:x          Same as :wq but only writes if there are changes
:q!         Force quit, discarding changes
ZZ          Same as :wq (in normal mode, without :)

dd          Delete the entire line
dw          Delete from position to the end of the word
d$          Delete to the end of the line
yy          Copy (yank) the line
p           Paste after the cursor
u           Undo
Ctrl+R      Redo
/text       Search for "text" (n next, N previous)
:%s/a/b/g   Replace "a" with "b" throughout the file
gg          Go to the first line
G           Go to the last line
:42         Go to line 42

When to use nano vs vim

There’s no “better” — there’s better for the context. Practical criteria:

Use nano when:

• The task is editing 1-3 lines in a config file
• You’ll only touch the file once and won’t return for a while
• You’re on a server you rarely access
• You want to avoid the risk of making a mode-related mistake and corrupting the file
• You’re pasting snippets from tutorials without needing to format them

Use vim when:

• You edit files frequently (daily admin work)
• You work with large files (logs, SQL dumps, long configs)
• You need to do bulk edits (regex replacement on every line)
• You already use vim on your desktop and want consistency
• The server doesn’t have nano (some Alpine containers only ship vi/vim)

A common pattern: use nano for the first few months of VPS admin, and migrate to vim when nano starts feeling slow for repetitive operations. There’s no shame in staying with nano — many experienced people prefer it for simplicity.

Verification

To confirm your setup is ready, test both editors on a test file:

echo "line 1" > ~/test.txt
nano ~/test.txt
# Add a line, save with Ctrl+O, exit with Ctrl+X
cat ~/test.txt
# Should show 2 lines

vim ~/test.txt
# Press i, add a line, Esc, :wq, Enter
cat ~/test.txt
# Should show 3 lines

rm ~/test.txt

If both worked and you were able to save and exit each one, your VPS is ready for daily administration.

Troubleshooting

”command not found: vim”

Your VPS image may only have vi (Busybox version) or neither. Run sudo apt install vim to fix it. On RHEL-like systems (AlmaLinux, Rocky), use sudo dnf install vim-enhanced.

File is “read-only” in vim

You opened it without sudo and the file requires privileges. Without losing your work, save it with :w !sudo tee % > /dev/null — this command passes the buffer content to tee running with sudo, writing to the file. Then exit with :q!.

Nano ignores indentation when pasting code

nano auto-indents each pasted line if autoindent is active, turning indented code into a staircase. Before pasting, press Alt+I to temporarily disable auto-indent. Paste the code, then re-enable with Alt+I again.

vim shows weird characters like ^M at the end of lines

The file was saved with Windows line endings (CRLF). Convert it with :set fileformat=unix followed by :w, or run dos2unix file.txt in the terminal before opening.

Next steps

With your editor chosen and the basic commands in your head, these are the topics that typically come next in VPS administration:

1. Set up SSH key-based authentication — eliminate the login password
2. Configure the UFW firewall to close unnecessary ports
3. Automate config backups in /etc with rsync and cron
4. Use git to version critical configuration files
5. Learn tmux or screen to keep persistent SSH sessions

If you’re setting up a VPS for production and want infrastructure that delivers what it promises, a Hostini VPS ships with clean Ubuntu and Debian images (with nano and vim available), full root access, and a KVM console via the panel in case you make a configuration mistake and lose SSH.