{"id":462,"date":"2026-10-14T14:51:32","date_gmt":"2026-10-14T14:51:32","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2015\/12\/12\/20-xargs-commands-examples-in-linux-unix\/"},"modified":"2026-10-14T14:51:32","modified_gmt":"2026-10-14T14:51:32","slug":"20-xargs-commands-examples-in-linux-unix","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/20-xargs-commands-examples-in-linux-unix\/","title":{"rendered":"xargs in Linux: Practical Commands, Safe Patterns, and Pipeline Workflows"},"content":{"rendered":"\n

Originally published on 2015-12-12; fully revised and updated.<\/em><\/p>\n\n\n\n

\"xargs-commands\"\/<\/figure>\n\n\n\n

The xargs<\/code> command builds and runs commands from standard input. It is especially useful for DevOps and Linux engineers who need to process long lists of files, IDs, or paths in shell pipelines. In this tutorial, you\u2019ll learn how xargs<\/code> works, when to use key options, and how to avoid common mistakes with whitespace and destructive commands.<\/p>\n\n\n\n

How xargs works in a shell pipeline<\/h2>\n\n\n\n

At a high level, one command produces items, xargs<\/code> groups\/parses those items, and then executes a target command with the resulting arguments. If you run xargs<\/code> without specifying a command, it typically uses echo<\/code> as the default command.<\/p>\n\n\n\n

\nflowchart TD\n    A[Producer command emits items] --> B[Choose delimiter strategy]\n    B --> C[xargs parses input]\n    C --> D[Apply batch and replacement rules]\n    D --> E[Build target command arguments]\n    E --> F[Execute target command]\n    F --> G{More input items}\n    G -- yes --> C\n    G -- no --> H[Pipeline completes]\n<\/pre>\n\n\n\n
Quick option comparison<\/h2>\n\n\n\n
Option<\/th>What it does<\/th>Typical use<\/th>Portability note<\/th><\/tr><\/thead>
-n N<\/code><\/td>Use at most N arguments per command run<\/td>Batching large input lists<\/td>Widely available<\/td><\/tr>
-L N<\/code><\/td>Use at most N input lines per run<\/td>Line-oriented batching<\/td>Widely available<\/td><\/tr>
-0<\/code><\/td>Read NUL-delimited input<\/td>Safe filename handling with find -print0<\/code><\/td>Common on GNU\/BSD, not required by POSIX<\/td><\/tr>
-d DELIM<\/code><\/td>Use a custom delimiter<\/td>Newline-only splitting or custom records<\/td>GNU extension<\/td><\/tr>
-I REPL<\/code><\/td>Replace placeholder token in command template<\/td>Insert item in the middle of a command<\/td>Widely available<\/td><\/tr>
-P N<\/code><\/td>Run up to N processes in parallel<\/td>Parallelize independent tasks<\/td>Implementation-dependent<\/td><\/tr>
-t<\/code> \/ -p<\/code><\/td>Trace command \/ prompt before run<\/td>Safer dry-run and confirmation<\/td>Widely available<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Practical xargs command examples<\/h2>\n\n\n\n
1) Basic stdin behavior<\/h3>\n\n\n\n
This reproduces the classic interactive behavior: type input, then press Ctrl+D<\/code> to end stdin.<\/p>\n\n\n
xargs\nHi,\nWelcome to TGS.\n^D\nHi, Welcome to TGS.<\/code><\/span><\/pre>\n\n\n
2) Limit arguments per command with -n<\/h3>\n\n\n
echo<\/span> a b c d e f | xargs\n# a b c d e f<\/span>\n\necho<\/span> a b c d e f | xargs -n 3<\/span>\n# a b c<\/span>\n# d e f<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
3) Split only on newlines with -d ‘\\n’ (GNU)<\/h3>\n\n\n\n
This helps preserve spaces inside each line item.<\/p>\n\n\n
printf 'alpha\\nbeta gamma\\n'<\/span> | xargs -d '\\n'<\/span> -n 1<\/span> printf '[%s]\\n'<\/span>\n# [alpha]<\/span>\n# [beta gamma]<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
4) Safely handle filenames with spaces using -print0 and -0<\/h3>\n\n\n
find . -name \"*.c\"<\/span> -print0 | xargs -0<\/span> rm -f<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
This pattern is safer than whitespace-delimited parsing when filenames contain spaces, tabs, or newlines.<\/p>\n\n\n\n
5) Use placeholder replacement with -I<\/h3>\n\n\n
printf '%s\\n'<\/span> app.log db.log | xargs -I {} cp {} {}.bak<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
6) Legacy find cleanup patterns from the original post<\/h3>\n\n\n
find \/usr\/preserve -mtime +30<\/span> -print<\/span> | xargs rm -f\nfind \/usr\/preserve -size +1024<\/span> -print<\/span> | xargs -n 20<\/span> rm -f<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
7) Trace or confirm commands before execution<\/h3>\n\n\n
printf '%s\\n'<\/span> file1 file2 | xargs -t rm -f\nprintf '%s\\n'<\/span> file1 file2 | xargs -p rm -f<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
8) Run independent tasks in parallel<\/h3>\n\n\n
printf '%s\\n'<\/span> 1<\/span> 2<\/span> 3<\/span> 4<\/span> | xargs -n 1<\/span> -P 2<\/span> -I {} sh -c 'echo start {}; sleep 1; echo done {}'<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
xargs vs find -exec: when to choose which<\/h2>\n\n\n\n
Approach<\/th>Best for<\/th>Example<\/th>Trade-off<\/th><\/tr><\/thead>
xargs<\/code><\/td>Flexible pipelines and batching control<\/td>find . -type f -print0 | xargs -0 rm -f<\/code><\/td>Needs careful delimiter handling<\/td><\/tr>
find -exec {} +<\/code><\/td>Simple, safer in one command<\/td>find . -type f -name \"*.tmp\" -exec rm -f {} +<\/code><\/td>Less explicit control over batching style<\/td><\/tr>
find -exec {} \\;<\/code><\/td>One-file-at-a-time execution<\/td>find . -type f -exec chmod 640 {} \\;<\/code><\/td>Can be slower for large file sets<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Best practices and common pitfalls<\/h2>\n\n\n\n
  • Use find -print0 | xargs -0<\/code> when dealing with filenames from the filesystem.<\/li>
  • For destructive commands (rm<\/code>, mv<\/code>, chmod<\/code>), start with xargs -t<\/code> or replace the command with echo<\/code> first.<\/li>
  • Use -n<\/code> to control command size and avoid oversized invocations.<\/li>
  • Check your platform\u2019s man xargs<\/code> for option differences, especially -d<\/code> and -P<\/code>.<\/li>
  • When possible, prefer find -exec {} +<\/code> for straightforward file operations.<\/li><\/ul>\n\n\n\n
    Bottom line:<\/strong> xargs<\/code> is a powerful command-construction tool for shell automation. Used with safe delimiters and cautious validation, it becomes a reliable building block for DevOps workflows.<\/p>\n","protected":false},"excerpt":{"rendered":"
    This guide explains how to use xargs effectively in Linux\/Unix shells, from basic stdin handling to safe file operations and parallel execution. You\u2019ll learn practical command patterns, portability caveats, and safer alternatives.<\/p>\n","protected":false},"author":1,"featured_media":3174,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[4957],"tags":[378,632,460,1274,169,1271,1272,1273,1276,1275],"class_list":["post-462","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","tag-commands","tag-examples","tag-linux","tag-linux-xargs-command","tag-unix","tag-xargs","tag-xargs-command","tag-xargs-command-examples","tag-xargs-command-line","tag-xargs-commands-tutorials"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/462","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=462"}],"version-history":[{"count":5,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/462\/revisions"}],"predecessor-version":[{"id":79347,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/462\/revisions\/79347"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/3174"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=462"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=462"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}