## How can I use numbers with leading zeros in a loop, e.g. 01, 02?

As always, there are different ways to solve the problem, each with its own advantages and disadvantages.

Bash version 4 allows zero-padding and ranges in its BraceExpansion:

```   1 # Bash 4 / zsh
2 for i in {01..10}; do
3     ...
```

All of the other solutions on this page will assume Bash earlier than 4.0, or a non-Bash shell.

If there are not many numbers, BraceExpansion can be used:

```   1 # Bash / ksh / zsh
2 for i in 0{1,2,3,4,5,6,7,8,9} 10
3 do
4     echo "\$i"
5 done
```

In Bash 3, you can use ranges inside brace expansion (but not zero-padding). Thus, the same thing can be accomplished more concisely like this:

```   1 # Bash 3
2 for i in 0{1..9} 10
3 do
4     echo "\$i"
5 done
```

Another example, for output of 0000 to 0034:

```   1 # Bash 3
2 for i in {000{0..9},00{10..34}}
3 do
4     echo "\$i"
5 done
6
7 # using the outer brace instead of just adding them one next to the other
8 # allows to use the expansion, for instance, like this:
```

This gets tedious for large sequences, but there are other ways, too. If you have the printf command (which is a Bash builtin, and is also POSIX standard), it can be used to format a number:

```   1 # Bash / ksh93 / zsh
2 for ((i = 1; i <= 10; i++)); do
3     i=\$(printf %02d "\$i")
4     ...
5 done
```

Also, unlike the C library printf, since printf will implicitly loop if given more arguments than format specifiers, you can simplify this enormously:

```   1 # Bash 3
2 printf '%03d\n' {1..300}
```

If you don't know in advance what the starting and ending values are:

```   1 # Bash 3
2 # start and end are variables containing integers
3 eval "printf '%03d\n' {\$start..\$end}"
```

The eval is required in Bash because for each command it performs an initial pass of evaluation, going through each word to process brace expansions prior to any other evaluation step. The traditional Csh implementation, which all other applicable shells follow, insert the brace expansion pass sometime between the processing of other expansions and pathname expansion, thus parameter expansion has already been performed by the time words are scanned for brace expansion. There are various pros and cons to Bash's implementation, this being probably the most frequently cited drawback. Given how messy that eval solution is, please give serious thought to using a for or while loop with shell arithmetic instead.

The ksh93 method for specifying field width for sequence expansion is to add a (limited) printf format string to the syntax, which is used to format each expanded word. This is somewhat more powerful, but unfortunately incompatible with bash, and ksh does not understand Bash's field padding scheme:

```   1 #ksh93
2 echo {0..10..2%02d}
```

ksh93 also has a variable attribute that specifies a field with to pad with leading zeros whenever the variable is referenced. The concept is similar to other attributes supported by Bash such as case modification. Note that ksh never interprets octal literals.

```   1 # ksh93 / mksh / zsh
2 \$ typeset -Z3 i=4
3 \$ echo \$i
4 004
```

If the command seq(1) is available (it's part of GNU sh-utils/coreutils), you can use it as follows:

```   1 seq -w 1 10
```

or, for arbitrary numbers of leading zeros (here: 3):

```   1 seq -f "%03g" 1 10
```

Combining printf with seq(1), you can do things like this:

```   1 # POSIX shell, GNU utilities
2 printf "%03d\n" \$(seq 300)
```

(That may be helpful if you are not using Bash, but you have seq(1), and your version of seq(1) lacks printf-style format specifiers. That's a pretty odd set of restrictions, but I suppose it's theoretically possible. Since seq is a nonstandard external tool, it's good to keep your options open.)

Be warned however that using seq might be considered bad style; it's even mentioned in Don't Ever Do These.

Some BSD-derived systems have jot(1) instead of seq(1). In accordance with the glorious tradition of Unix, it has a completely incompatible syntax:

```   1 # POSIX shell, OpenBSD et al.
2 printf "%02d\n" \$(jot 10 1)
3
4 # Bourne shell, OpenBSD (at least)
5 jot -w %02d 10 1
```

Finally, the following example works with any BourneShell derived shell (which also has expr and sed) to zero-pad each line to three bytes:

```   1 # Bourne
2 i=0
3 while test \$i -le 10
4 do
5     echo "00\$i"
6     i=`expr \$i + 1`
7 done |
8     sed 's/.*\(...\)\$/\1/g'
```

In this example, the number of '.' inside the parentheses in the sed command determines how many total bytes from the echo command (at the end of each line) will be kept and printed.

But if you're going to rely on an external Unix command, you might as well just do the whole thing in awk in the first place:

```   1 # Bourne
2 # count variable contains an integer
3 awk -v count="\$count" 'BEGIN {for (i=1;i<=count;i++) {printf("%03d\n",i)} }'
4
5 # Bourne, with Solaris's decrepit and useless awk:
6 awk "BEGIN {for (i=1;i<=\$count;i++) {printf(\"%03d\\n\",i)} }"
```

Now, since the number one reason this question is asked is for downloading images in bulk, you can use the examples above with xargs(1) and wget(1) to fetch files:

```   1 almost any example above | xargs -i% wget \$LOCATION/%
```

The xargs -i% will read a line of input at a time, and replace the % at the end of the command with the input.

Or, a simpler example using a for loop:

```   1 # Bash 3
2 for i in {1..100}; do
3    wget "\$prefix\$(printf %03d \$i).jpg"
4    sleep 5
5 done
```

Or, avoiding the subshells (requires bash 3.1):

```   1 # Bash 3.1
2 for i in {1..100}; do
3    printf -v n %03d \$i
4    wget "\$prefix\$n.jpg"
5    sleep 5
6 done
```