head Command in Linux Made Simple

×

The head command in Linux is the fastest way to inspect a file without opening it. But when a log is 80,000 lines long and you just need the first twenty, opening it in an editor is a waste of time and, on a live server, sometimes risky. That is exactly where head earns its place in your toolkit.

Examples

head reads a file and prints the first part of it to your terminal. By default, that means the first 10 lines. Nothing more, nothing less.

Think of it like the preview pane in a file manager, except you control exactly how much you see and you can feed its output directly into other commands. On any Linux system, whether Ubuntu, Rocky Linux, RHEL, Debian, or Arch, head is part of GNU coreutils and is available out of the box. You do not need to install anything.

If you are already comfortable running basic commands in the terminal, head will feel natural within the first five minutes. It follows the same logic as most Unix tools: one job, done well, composable with everything else.

Break it down: head is the command. [OPTIONS] are the flags you add to change what it shows. [FILE...] is the file you want to read. The three dots mean you can pass multiple files at once.

If you skip the file entirely and just run head, it reads from standard input. That means you can pipe output from another command straight into it, which is where a lot of the real power comes from.

The most basic use. No flags, just the filename. You get the first 10 lines printed to your terminal immediately.

Need the first 5 lines of a config file? Pass -n followed by your number. Works with any file and any count.

Sometimes lines do not matter. If you need to check the first 50 bytes of a file (useful for magic byte verification or binary headers), use -c.

Pass more than one filename and head will label each section with a header automatically. Useful when comparing config files across environments.

When you are piping multi-file output into another command, those ==> filename <== headers will break your pipeline. Use -q to strip them out.

Combine ls -lt (sorted by modification time, long format) with head to get the most recently changed files in a directory. Handy for checking what a deployment just touched. Note: ls -l output always starts with a total N summary line, so head -n 6 returns that summary plus the top 5 files.

Want lines 15 through 25 of a file? Pipe head into tail. This is a common pattern when you know your data starts at a specific offset.

When processing data files in a script, validating the header row before doing anything else saves you from bad imports. Here is a quick check pattern you can drop into any pipeline script.

On production servers with log rotation, you often need a quick check of what is at the top of today's log versus yesterday's. Running head on both at once gives you an instant comparison.

Grab the top of a log and filter it through grep in one shot. Useful for triaging an incident when you only want error entries from the start of the file.

This is one of the most common traps. A developer runs head on a config file expecting to see the whole short file, but the file is 14 lines and they only see 10. They then assume the file is truncated or the last section is missing, and spend time troubleshooting something that is not broken.

When auditing a directory of config files or data exports, combine find with a head loop to peek at the first line of every file. Useful for format validation across a batch.

The real value of the head command in Linux is not the command itself, it is what it prevents. On a server with a 500MB log file, opening that file carelessly in an editor or running cat on it can lock up your terminal session, push huge amounts of data through a slow SSH connection, and give you nothing useful faster than head -n 20 does. For good Linux logging practice, quick non-destructive inspection is the first step before any deeper analysis.

In scripting, head -n 1 is the standard way to read a file header, validate CSV column order, or extract a shebang line without loading the whole file into memory. If you are writing automation scripts or batch processing pipelines, understanding how bash scripting and automation tools like head work together will save you from a lot of slow, fragile code. The official documentation at man7.org covers all POSIX-level details if you ever need to go deeper on compatibility.