{"id":12315,"date":"2026-03-09T12:31:44","date_gmt":"2026-03-09T07:01:44","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=12315"},"modified":"2026-03-09T12:31:46","modified_gmt":"2026-03-09T07:01:46","slug":"head-command-in-linux","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/head-command-in-linux","title":{"rendered":"Head Command in linux | Complete User Guide with Examples 2026"},"content":{"rendered":"\n

The head command in Linux<\/strong> prints the beginning of files or input, letting you quickly preview the first lines or bytes without opening the entire file. By default, head shows the first 10 lines, supports multiple files, and works with pipes. It\u2019s essential for log inspection, data sampling, and shell scripting.<\/p>\n\n\n\n

If you regularly manage servers, debug applications, or process datasets, learning the head command in Linux is a must. This beginner friendly guide explains head\u2019s syntax, options, practical use cases, and advanced tips, crafted from 12+ years of hands on hosting and sysadmin experience at YouStable.<\/p>\n\n\n\n

\n\n\n\n

What is the head Command in Linux?<\/h2>\n\n\n\n
\"What<\/figure>\n\n\n\n

head is a standard Unix\/Linux utility (part of GNU coreutils on most distributions) that outputs the start of a file or data stream. It defaults to 10 lines but can output any number of lines or bytes you specify. It supports multiple files, works seamlessly with pipes, and is safe to use on huge files.<\/p>\n\n\n\n

\n\n\n\n

Syntax and Basic Usage<\/h2>\n\n\n\n

At its simplest, head prints the first 10 lines of each file you pass. Use options to change how many lines or bytes you see.<\/p>\n\n\n\n

head [OPTION]... [FILE]...<\/code><\/pre>\n\n\n\n
Show the First N Lines<\/h3>\n\n\n\n
Use -n (or –lines) to control line count. Positive numbers print the first N lines. A leading minus excludes the last N lines (see advanced tips below).<\/p>\n\n\n\n
# First 10 lines (default)\nhead \/var\/log\/syslog\n\n# First 20 lines\nhead -n 20 \/var\/log\/syslog\n\n# First 3 lines of two files\nhead -n 3 file1.txt file2.txt<\/code><\/pre>\n\n\n\n
Show the First N Bytes<\/h3>\n\n\n\n
Use -c (or –bytes) when you need byte precise previews, helpful for binary files or tight performance constraints.<\/p>\n\n\n\n
# First 100 bytes\nhead -c 100 image.jpg > sample.bin\n\n# First 4 KiB of a huge log\nhead -c 4096 \/var\/log\/nginx\/access.log<\/code><\/pre>\n\n\n\n
Read from Standard Input (Pipes)<\/h3>\n\n\n\n
Head works perfectly in pipelines<\/a>, making it a go to tool for sampling command output.<\/p>\n\n\n\n
# Preview the first 10 matches\ngrep \"ERROR\" \/var\/log\/app.log | head\n\n# Sample the first 15 lines of a sorted list\nsort largefile.txt | head -n 15<\/code><\/pre>\n\n\n\n
Multiple Files and Headers<\/h3>\n\n\n\n
When you pass multiple files, head prints a header before each file by default. You can quiet or force headers with -q or -v.<\/p>\n\n\n\n
# Default: headers shown\nhead -n 5 file1.txt file2.txt\n\n# Quiet: no headers\nhead -q -n 5 file1.txt file2.txt\n\n# Verbose: always show headers\nhead -v file1.txt<\/code><\/pre>\n\n\n\n
\n\n\n\n
Essential Options and Flags<\/h2>\n\n\n\n
-n, --lines=K<\/strong><\/code><\/pre>\n\n\n\n
Print the first K lines. If K has a leading minus (e.g., -n -5), head prints all but the last K lines. This is useful for trimming trailers or footers in generated files.<\/p>\n\n\n\n
# First 25 lines\nhead -n 25 report.txt\n\n# Everything except the last 3 lines (GNU head)\nhead -n -3 report.txt<\/code><\/pre>\n\n\n\n
-c, –bytes=K<\/h3>\n\n\n\n
Print the first K bytes. With a leading minus, print all but the last K bytes. This helps when dealing with binary footers or when you need a byte limited sample for tooling tests.<\/p>\n\n\n\n
# First 1 MB of a file\nhead -c 1M bigfile.dat\n\n# All but the last 512 bytes (GNU head)\nhead -c -512 archive.tar<\/code><\/pre>\n\n\n\n
-q, –quiet and -v, –verbose<\/h3>\n\n\n\n
Control whether headers are printed for multiple files. -q suppresses headers; -v forces them even for a single file. This is helpful in scripts to make outputs deterministic.<\/p>\n\n\n\n
-z, –zero-terminated<\/h3>\n\n\n\n
Treat input lines as NUL terminated instead of newline terminated (GNU extension). Use this for safety with filenames containing newlines, typically when piping from find -print0.<\/p>\n\n\n\n
# Safely sample filenames containing special characters\nfind . -type f -print0 | head -z -n 10 | tr '\\0' '\\n'<\/code><\/pre>\n\n\n\n
Help and Version<\/h3>\n\n\n\n
head --help\nhead --version<\/code><\/pre>\n\n\n\n
\n\n\n\n
Practical Use Cases for head<\/h2>\n\n\n\n
Quickly Preview Logs<\/h3>\n\n\n\n
Sampling logs helps you validate rotations, formats, and pipeline stages without loading the entire file.<\/p>\n\n\n\n
# Inspect the latest rotated syslog\nls -ltr \/var\/log | tail -n 5 | head -n 1\n\n# Verify Nginx access log structure\nhead -n 20 \/var\/log\/nginx\/access.log<\/code><\/pre>\n\n\n\n
On YouStable VPS or dedicated servers<\/a><\/strong>, this approach saves I\/O and reduces CPU usage while you troubleshoot, especially on high traffic web stacks.<\/p>\n\n\n\n
Check CSV Headers and Sample Rows<\/h3>\n\n\n\n
Data teams often need to confirm schema and encoding quickly. head gives you a reliable snapshot.<\/p>\n\n\n\n
# View header + first 10 rows\nhead -n 11 data.csv\n\n# Check if file is actually binary or malformed text\nhead -c 256 data.csv | hexdump -C<\/code><\/pre>\n\n\n\n
Combine with grep, sed, awk<\/h3>\n\n\n\n
Head is a great \u201ccircuit breaker\u201d to limit volume in pipelines so you can iterate faster.<\/p>\n\n\n\n
# First 15 error lines only\ngrep -i \"error\" app.log | head -n 15\n\n# Preview first 50 unique domains (case-insensitive)\nawk<\/a> -F, '{print tolower($3)}' access.csv | sort -u | head -n 50\n\n# Sample transformed lines to validate logic\nsed 's\/foo\/bar\/g' big.txt | head<\/code><\/pre>\n\n\n\n
Inspect Binary Files Safely<\/h3>\n\n\n\n
When working with archives or images, read a small byte range instead of opening the whole file. This is safer and faster on production hosts.<\/p>\n\n\n\n
# Peek at magic numbers or headers\nhead -c 64 file.bin | hexdump -C\n\n# Verify TAR header without expanding\nhead -c 512 backup.tar | hexdump -C<\/code><\/pre>\n\n\n\n
Script-Friendly File Sampling<\/h3>\n\n\n\n
Use head in CI\/CD or cron jobs<\/a> to provide concise, readable logs and limit noisy output.<\/p>\n\n\n\n
# In a script: log top of a build artifact list\nls -lh artifacts\/ | head -n 20 > build_summary.txt<\/code><\/pre>\n\n\n\n
\n\n\n\n
Advanced Tips for Power Users<\/h2>\n\n\n\n
Head vs Tail vs Sed<\/h3>\n\n\n\n
– head shows the beginning.<\/p>\n\n\n\n