GUI vs Terminal: When Should a Linux Beginner Use Each?

A graphical user interface, or GUI, lets you work through visible windows, buttons, menus, and pointer actions. The Ubuntu desktop and Files application are GUIs.

A terminal is a text-based interface to a shell. The shell reads commands and reports text output or errors.

Both control the same computer. The terminal is another interface, not a separate computer hidden inside Ubuntu.

Use the GUI when it makes the decision visible

For a beginner, graphical tools are often clearer for:

• Selecting a known Wi-Fi network.
• Choosing display scale and arranging monitors.
• Browsing and previewing photos.
• Dragging a file between visible folders.
• Selecting speakers or a microphone.
• Changing ordinary desktop preferences.
• Reviewing a removable drive before ejecting it.

The GUI provides visible labels and previews. Those are valuable when the task depends on identifying the correct device or seeing the result immediately.

Use the terminal when text is the useful interface

The terminal becomes especially useful for:

• Starting a web-development project.
• Checking the version of a developer tool.
• Using Git to inspect and record code changes.
• Reading detailed build output.
• Searching or transforming repeated text.
• Automating the same operation many times.
• Working on a remote server that has no desktop.

This does not mean every installation or repair should become a copied command. A graphical tool remains the better choice when it makes a risky target easier to verify.

Open Terminal and read the prompt

Open Terminal from application search.

You may see a line similar to:

Example prompt — do not typesam@computer:~$

This is the prompt. It tells you the shell is ready. Parts can identify the user, computer, and current folder.

Do not copy the prompt into a command. The dollar sign is also not part of the command in this example.

Run one read-only command

pwd means print working directory. A working directory is the folder the shell currently treats as your location.

pwd

Press Enter once.

The output may look like:

/home/sam

Your account name will differ. This path corresponds to the Home location you used in Files.

The command did not move or change anything. It asked the shell to report the current location.

What if the screen looks different?

A customized prompt can use colors, symbols, or different text. The terminal application can also have a different theme.

The teaching method remains the same:

1. Identify the prompt that was already on screen.
2. Type only the command.
3. Press Enter.
4. Read the new output.
5. Wait for the prompt to return before entering another command.

If pwd prints a folder other than Home, the terminal was opened or previously moved to another working directory. That is not automatically an error.

Choose by clarity, not status

Suppose you need to copy three photos to a visible USB drive. Files makes the source, destination, thumbnails, and eject action easy to inspect. Use it.

Suppose you need to run an Astro development server and read its port. The terminal exposes the project’s command and output directly. Use it after the relevant path teaches the command.

Common mistakes

Copying sam@computer:~$. Type only pwd.

Expecting every successful command to show a message. Some commands finish silently; later terminal lessons will teach how to verify those results.

Running a command from an unknown guide because the GUI differed. First verify the Ubuntu version, task, command meaning, and primary source.

Using a terminal to avoid learning the visible system. Keep using Files and Settings where they give safer feedback.

Assuming a command runs from every folder the same way. The current working directory can matter; pwd reveals it.

What to learn next

Next learning path: Linux Terminal Basics — Planned.

That path will explain the prompt, commands, options, output, folders, paths, and safe recovery in a deliberate order. No empty public route has been created. Until it is published, keep using the graphical tools from this path and the official command-line introduction linked below.