AWK in a Nutshell
AWK is a domain-specific programming language for processing text that is organized into lines and columns. Instead of writing loops to open a file and read it line by line, you declare patterns and the actions to run when a line matches. AWK handles the reading loop for you, feeding it every line of input automatically. It was created in 1977 at Bell Labs by Alfred Aho, Peter Weinberger, and Brian Kernighan, whose surname initials give the language its name.
Cricket analogy: Like a wicketkeeper who does not chase every ball but stands ready and reacts only when the ball actually comes to the stumps, AWK sits back and springs into action only on lines that match a pattern.
Why AWK Still Matters
Despite being nearly five decades old, AWK remains preinstalled on virtually every Unix and Linux system, so it is always available when you SSH into a server with nothing else set up. Its sweet spot is quick, one-off transformations of tabular text: pulling the third column out of a log, summing a numeric field, or reformatting comma-separated values. For these tasks a one-line AWK program often replaces a dozen lines of Python or a fragile chain of cut, sort, and paste. Because AWK is stream-oriented it processes files far larger than memory, reading one record at a time.
Cricket analogy: Like a reliable twelfth man who is always in the dressing room ready to field when needed, AWK is preinstalled and available on any server the moment you need it.
A First Taste
The canonical introductory example prints the first column of every line of input. AWK automatically splits each line into fields on whitespace and names them $1, $2, $3 and so on, with $0 being the entire line. You never write the read loop; the body inside the braces runs once per line. This field-splitting behaviour, combined with implicit iteration, is what makes AWK feel almost declarative for column work.
Cricket analogy: Selecting $1 from each line is like a scorer noting only the opening batsman's name from every innings sheet, ignoring the rest of the batting order.
# Print the first whitespace-separated field of every line
awk '{ print $1 }' access.log
# $0 is the whole line, $1..$NF are the fields
echo 'alice 42 engineer' | awk '{ print $1, $3 }'
# -> alice engineerThere are several AWK implementations: the original 'one true awk' (BWK awk) by Kernighan, GNU AWK (gawk) which is the most feature-rich and common on Linux, and mawk which is very fast. For portable scripts, stick to POSIX AWK features; use gawk-only extensions only when you know gawk is present.
- AWK is a data-driven language for scanning text organized into lines (records) and columns (fields).
- It was created in 1977 at Bell Labs; the name comes from Aho, Weinberger, and Kernighan.
- You declare patterns and actions; AWK supplies the line-reading loop automatically.
- Fields are auto-split on whitespace and accessed as $1, $2, ...; $0 is the whole line.
- It is preinstalled on nearly all Unix/Linux systems and processes files larger than memory as a stream.
- Common implementations include one-true-awk, gawk (GNU), and mawk.
Practice what you learned
1. What does the name AWK stand for?
2. In AWK, what does $0 refer to?
3. Which task is AWK best suited for?
4. How does AWK handle reading the input file?
5. Which of these is a real AWK implementation?
Was this page helpful?
You May Also Like
AWK Pattern-Action Syntax
Every AWK program is a sequence of pattern { action } rules. Understanding how patterns select lines and actions transform them is the core mental model of the whole language.
Fields and Records in AWK
AWK splits input into records (lines) and fields (columns). Mastering $1..$NF, the NR/NF variables, and the FS/RS/OFS/ORS separators unlocks nearly all column-oriented text work.
Your First AWK One-Liner
Walk through building practical AWK one-liners step by step: printing columns, filtering rows, summing fields, and counting lines. These small programs cover a huge share of everyday text tasks.
Running AWK Scripts
There are several ways to run AWK: inline one-liners, program files with -f, and self-executing scripts with a shebang. Knowing each lets you scale from a quick command to a maintainable tool.
Related Reading
Related Study Notes in Programming
Browse all study notesApache Spark Study Notes
Programming · 30 topics
ProgrammingApache Flink Study Notes
Programming · 30 topics
ProgrammingHadoop Study Notes
Programming · 30 topics
ProgrammingSnowflake Study Notes
Programming · 30 topics
ProgrammingApache Airflow Study Notes
Programming · 30 topics
Programmingdbt (Data Build Tool) Study Notes
Programming · 30 topics