A terminal is a text-based window where you type commands to tell your computer what to do, instead of pointing and clicking. You type a short instruction, press enter, and the computer carries it out and prints the result as text. Developers, system administrators, and power users lean on the terminal because it is fast, precise, and easy to repeat. It can look intimidating at first, all black background and blinking cursor, but it is just another way to give your computer instructions. Here is what a terminal does, how it relates to the shell, and the few commands worth learning first.
How a terminal works
When you open a terminal, you see a prompt waiting for input. You type a command such as one that lists the files in the current folder, press enter, and the response appears as text right below. There are no buttons or menus; the entire conversation is words. That directness is the point. A single typed command can do something that would take many clicks in a graphical app, and you can run it again instantly.
Because everything is text, you can also chain commands together, save them in a file to run later, and copy them between machines. This is why so much developer tooling, from version control to deployment, assumes you are comfortable in a terminal. If you are setting up a coding workflow, our guide to how to use VS Code shows an editor with a built-in terminal so you do not have to switch windows.
Terminal vs shell
People use the words terminal and shell loosely, but they are distinct. The terminal is the window and the text interface. The shell is the program running inside it that actually reads your command, figures out what you meant, and runs it. The terminal shows the conversation; the shell holds it up.
| Part |
Role |
Analogy |
| Terminal |
The window that displays text and takes input |
The phone handset |
| Shell |
The program that interprets and runs commands |
The person on the line who understands you |
| Command |
The instruction you type |
What you say |
You can run different shells inside the same terminal, which is why the two are separate ideas. For most beginners the difference rarely matters, but knowing it helps when a tutorial mentions one or the other.
A few commands worth knowing
You do not need to memorize a manual. A small core of commands handles most day-to-day work.
- Show where you are, which prints your current folder so you never feel lost.
- List files, to see what is in the current folder.
- Change folder, to move into another directory.
- Make a folder, to create a new directory for a project.
- Clear the screen, to tidy up when the output gets noisy.
Learn those five, and you can navigate confidently. Everything else you can look up when you need it.
What to skip
- Memorizing every flag. Commands have many options; learn them as specific needs arise rather than upfront.
- Fearing the black screen. A typed command is no more dangerous than a menu click, as long as you read before you run.
- Copy-pasting commands you do not understand. Know roughly what a command does before running it, especially anything that deletes.
- Switching tools constantly. Pick one terminal, get comfortable, then explore alternatives later.
FAQ
Is the terminal the same as the command prompt?
They are close. Command Prompt is the name of one classic terminal program on Windows; terminal is the general word for any such text window across operating systems.
Do I need to use the terminal to code?
Not for everything, but many tools assume it. Learning a handful of commands removes a lot of friction from common developer tasks.
Is the terminal dangerous?
Only if you run commands you do not understand. Read before you press enter, and be especially careful with anything that removes files.
What is the difference between a terminal and a shell?
The terminal is the window you type into; the shell is the program inside it that interprets and runs your commands.
Where to go next
Set up a friendly coding home with How to Use VS Code in 2026, version your work with How to Use Git and GitHub in 2026, and start from zero with How to Start Coding in 2026.