Bash String to Array (Split by Space, Delimiter, Newline + mapfile Examples)

Quick Cheat Sheet: Bash String to Array

Common Scenarios and One-Liners

# Space-separated string (most common)
string="apple banana orange"
read -ra arr <<< "$string"

# Comma-separated string
string="apple,banana,orange"
IFS=',' read -ra arr <<< "$string"

# Pipe-separated string
string="apple|banana|orange"
IFS='|' read -ra arr <<< "$string"

# Multiple delimiters (comma, semicolon, pipe)
string="apple,banana;orange|grape"
IFS=',;|' read -ra arr <<< "$string"

# Multiline string to array (recommended)
string=$'apple\nbanana\norange'
mapfile -t arr <<< "$string"

# Read file into array (line by line)
mapfile -t arr < file.txt

# Null-delimited input (advanced)
printf "apple\0banana\0orange" | mapfile -d '' -t arr

Space vs Delimiter vs Multiline (When to Use What)

Convert String to Array in Bash (Core Methods Explained)

Using read -ra (Best for Most Cases)

# Space-separated string
string="apple banana orange"

read -ra arr <<< "$string"

echo "${arr[@]}"

• Splits based on whitespace (default IFS)
• Fast and commonly used
• Best for simple scripts. After splitting, you can iterate over elements using a for loop in Bash.

Using IFS with Custom Delimiters

# Comma-separated string
string="apple,banana,orange"

IFS=',' read -ra arr <<< "$string"

echo "${arr[@]}"

# Pipe-separated string
string="apple|banana|orange"

IFS='|' read -ra arr <<< "$string"

• Use when input has a known delimiter
• Supports multiple delimiters. You can also validate values after splitting using string comparison in Bash.

Using mapfile / readarray (Multiline & Files)

# Multiline string
string=$'apple\nbanana\norange'

mapfile -t arr <<< "$string"

echo "${arr[@]}"

# Read from file
mapfile -t arr < file.txt

• Safest method for multiline or file input
• Avoids modifying IFS
• Handles complex input reliably

Split String by Delimiter into Array (Real Scenarios)

Comma-Separated String to Array

string="red,green,blue"

IFS=',' read -ra colors <<< "$string"

echo "${colors[@]}"

Space-Separated String to Array

string="one two three"

read -ra arr <<< "$string"

echo "${arr[@]}"

Multiple Delimiters (IFS=',;|')

string="apple,banana;orange|grape"

IFS=',;|' read -ra arr <<< "$string"

echo "${arr[@]}"

• Useful when input format is inconsistent
• Works for CSV-like or mixed delimiter data. For pattern-based extraction, see print next word after pattern match.

Convert Multiline String to Array in Bash

Using mapfile -t (Recommended)

# Multiline string
string=$'apple\nbanana\norange'

mapfile -t arr <<< "$string"

echo "${arr[@]}"

• Each line becomes one array element
• Removes trailing newline with -t
• Best choice for structured multiline input. Combine this with a while loop in Bash for conditional processing.

Using read with while loop (Alternative)

string=$'apple\nbanana\norange'

arr=()

while IFS= read -r line; do
    arr+=("$line")
done <<< "$string"

echo "${arr[@]}"

• More control over processing each line
• Useful if you need to filter or modify values while reading
• Slightly slower than mapfile

Advanced: mapfile -d Delimiter (Null / Custom Delimiter)

mapfile -d '' (Null Delimited Input)

# Null-delimited input (used in safe scripting)
printf "apple\0banana\0orange" | mapfile -d '' -t arr

echo "${arr[@]}"

• Uses null (\0) as delimiter instead of newline
• Safest way to handle filenames and special characters
• Common in combination with commands like find -print0, similar to examples in remove duplicate files using shell script.

When to Use mapfile -d vs IFS

Common Errors and Edge Cases

Why arr=($string) Breaks (Word Splitting Issue)

string="apple banana orange"
arr=($string)

echo "${arr[@]}"

• Performs word splitting + glob expansion
• Breaks if values contain spaces
• Can expand wildcards like * unexpectedly
• Unsafe for user input

# Example problem
string="apple 'red banana' orange"
arr=($string)

# Output becomes incorrect due to splitting

Avoid this method unless you fully control the input

Handling Spaces Inside Values

# Problem case
string="apple 'red banana' orange"

# Safe approach using delimiter
string="apple|red banana|orange"
IFS='|' read -ra arr <<< "$string"

echo "${arr[@]}"

• Use a delimiter that does not appear inside values
• Avoid whitespace splitting when values contain spaces. You can further filter values using remove elements from array in Bash.

Special Characters and Safe Input Handling

# Unsafe (can break with special chars)
string="file name with spaces.txt"
arr=($string)

# Safe approach using mapfile
printf "%s\n" "file name with spaces.txt" | mapfile -t arr

echo "${arr[@]}"

# Best practice for filenames (null-delimited)
find . -type f -print0 | mapfile -d '' -t files

• Use mapfile for robust handling
• Prefer null-delimited input for file operations. This is useful when parsing logs or files as shown in count occurrences of word in file.refer null-delimited input for file operations
• Avoid relying on default word splitting

Performance & Best Practice

read vs mapfile (Which is Faster?)

• read is lightweight and faster for small input
• mapfile is optimized for bulk input (files, large data)
• Performance difference is negligible for most scripts. For handling multiple tasks efficiently, see run shell scripts in parallel.Performance difference is negligible for most scripts

Avoiding IFS Side Effects in Scripts

# Bad practice (modifies global IFS)
IFS=','

# Good practice (limit scope)
IFS=',' read -ra arr <<< "$string"

# Restore IFS if modified
OLD_IFS="$IFS"
IFS=',' read -ra arr <<< "$string"
IFS="$OLD_IFS"

• Changing IFS globally can break other parts of script
• Always limit scope or restore it after use

Summary

• Use read -ra for space-separated strings (fast and simple)
• Use IFS + read for custom delimiters like comma, pipe, or semicolon
• Use mapfile -t for multiline strings or file input
• Use mapfile -d '' for null-delimited data (safe for filenames and special characters)
• Avoid arr=($string) as it can break due to word splitting and glob expansion

👉 Rule of thumb:

• Simple input → read -ra
• Structured / multiline / unknown input → mapfile

Official Documentation

• GNU Bash Reference Manual
• Bash Builtins (read, mapfile, readarray)
• Understanding IFS in Bash
• Common Bash Pitfalls
• bash(1) Manual Page