Bash focus guide

Bash User Input with read Explained

The Bash read command lets a script ask the user for input while it runs. Use it for prompts, confirmations, simple menus, safe checks and interactive admin scripts.

Bash Hub Arguments Guide Bash Cheat Sheet Operators Guide

On this page

Basic read Why use read -r? Prompt on one line Validate input Default values Confirm actions Hidden input Simple menu Arguments vs input Common mistakes

Basics

Basic Bash read example

The simplest input script asks for a value, stores it in a variable, then uses that variable.

#!/usr/bin/env bash

echo "Enter your name:"
read -r NAME

echo "Hello, $NAME"

$ ./read-name.sh

Enter your name:
Robbie
Hello, Robbie

Important

Why use read -r?

Use read -r in most scripts. The -r option prevents backslashes from being treated as escape characters.

Command	Use
`read NAME`	Works for simple input, but can treat backslashes specially.
`read -r NAME`	Safer default for most scripts.
`read -r -p "Name: " NAME`	Shows a prompt and reads input on one line.

Prompt

Prompt the user on one line

Use -p to show the prompt before reading input.

#!/usr/bin/env bash

read -r -p "Domain: " DOMAIN
echo "You entered: $DOMAIN"

$ ./domain-prompt.sh

Domain: example.com
You entered: example.com

Validation

Check that input was provided

Always check important input before using it.

#!/usr/bin/env bash

read -r -p "Domain: " DOMAIN

if [ -z "$DOMAIN" ]; then
  echo "No domain entered"
  exit 1
fi

echo "Checking $DOMAIN"
dig +short "$DOMAIN"

$ ./check-domain-input.sh

Domain: example.com
Checking example.com
93.184.216.34

This uses the -z string test. For more test operators, see Bash Operators Explained.

Defaults

Use a default value if input is blank

You can let the user press Enter to accept a default.

#!/usr/bin/env bash

read -r -p "Service [nginx]: " SERVICE
SERVICE="${SERVICE:-nginx}"

echo "Checking service: $SERVICE"
systemctl is-active "$SERVICE"

$ ./default-service.sh

Service [nginx]:
Checking service: nginx
active

The expression ${SERVICE:-nginx} means “use nginx if SERVICE is empty”.

Confirmations

Create a yes/no confirmation prompt

Confirmations are useful before running commands that change files, restart services or delete data.

#!/usr/bin/env bash

read -r -p "Continue? [y/N] " ANSWER

case "$ANSWER" in
  y|Y|yes|YES)
    echo "Continuing..."
    ;;
  *)
    echo "Cancelled."
    exit 1
    ;;
esac

$ ./confirm-action.sh

Continue? [y/N] y
Continuing...

Defaulting to “no” is safer for scripts that change things. Your script should not YOLO a delete because someone pressed Enter too quickly.

Hidden input

Read hidden input with -s

read -s hides what the user types. This is useful for passwords or tokens, though you should still avoid storing secrets carelessly.

#!/usr/bin/env bash

read -r -s -p "Password: " PASSWORD
echo
echo "Password length: ${#PASSWORD}"

$ ./password-input.sh

Password:
Password length: 12

Menus

Build a simple Bash menu

#!/usr/bin/env bash

echo "Choose an option:"
echo "1) Show hostname"
echo "2) Show disk usage"
echo "3) Quit"

read -r -p "Choice: " CHOICE

case "$CHOICE" in
  1)
    hostname
    ;;
  2)
    df -h /
    ;;
  3)
    echo "Goodbye"
    ;;
  *)
    echo "Invalid choice"
    exit 1
    ;;
esac

$ ./simple-menu.sh

Choose an option:
1) Show hostname
2) Show disk usage
3) Quit
Choice: 2
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2        80G   42G   35G  55% /

Arguments or input?

When should you use arguments instead of read?

Use arguments when...	Use read when...
The script should run unattended or from cron/systemd.	The script is interactive and a human is present.
You want repeatable commands like `./check-service.sh nginx`.	You want a guided prompt or menu.
You need automation.	You need confirmation before a risky action.

For non-interactive scripts, arguments are usually better. For guided beginner tools, read is often easier.

Downloads

Download the example scripts

Mistakes

Common Bash input mistakes

Mistake	Problem	Better
`read NAME` everywhere	Backslashes can be treated specially.	`read -r NAME`
Not checking blank input	The script may run with an empty variable.	Use `[ -z "$VALUE" ]`.
Using input prompts in automation	Scripts can hang waiting for input.	Use arguments for cron or systemd jobs.
Unsafe confirmations	Pressing Enter might accidentally continue.	Default to cancel unless the user types yes.

Keep learning Bash

Practical script

Example: safe confirmation prompt

For risky operations, ask for confirmation and only continue on a clear answer.

#!/usr/bin/env bash

read -r -p "Restart nginx now? Type yes to continue: " answer

if [ "$answer" != "yes" ]; then
  echo "Cancelled"
  exit 0
fi

echo "Restarting nginx..."
systemctl restart nginx

Example output:

$ ./restart-nginx.sh
Restart nginx now? Type yes to continue: no
Cancelled

$ ./restart-nginx.sh
Restart nginx now? Type yes to continue: yes
Restarting nginx...

Choosing input

Should you use read or script arguments?

Use	Best for
`read`	Interactive scripts, confirmations, menus and one-off prompts.
Arguments	Automation, cron jobs, repeatable scripts and commands run by other tools.
Config file	Reusable settings such as domains, paths, thresholds and email addresses.

FAQ

Frequently Asked Questions

What does read -r do in Bash?

read -r reads input without treating backslashes as escape characters, which is usually safer.

How do I prompt a user in Bash?

Use read -r -p "Prompt text: " variable to show a prompt and store the answer.

Should I use read in cron scripts?

No. Cron scripts are non-interactive, so use arguments, environment variables or config files instead.

How do I hide password input in Bash?

Use read -r -s -p "Password: " password, then print a newline after the prompt.

$ practise_next --topic bash

Practise this next

Turn the guide into practice with a related quiz, builder, cheat sheet or learning path.

[1]Open the Bash Scripting HubFollow the main Bash learning path.[2]Try the Bash Script CheckerCheck simple Bash scripts and practise safer habits.[3]Read: Bash Functions ExplainedLearn how to organise scripts with functions.[4]Open the Bash Cheat SheetReview common Bash syntax and scripting patterns.