English

View a BASH_HISTORY file online, free

Open and read .BASH_HISTORY files online. View source, logs and text with syntax highlighting, search and line numbers, free.

Drop your .BASH_HISTORY file here

Opens your .BASH_HISTORY file right here.

Choose file
Up to 50 MB · 160+ text and code extensions
Instant. Opens in seconds
No sign-up. Just open it
100% free. No limits on use

How to open a code or text file online

Three steps, a few seconds, no software.

01

Open your .BASH_HISTORY file

Drop it on the box, choose it from your device, or paste the text straight in.

02

View it instantly

Your .BASH_HISTORY file opens neatly formatted with line numbers.

03

Search, copy or download

Search the text, jump to any line, then copy what you need or download a clean copy.

What is a .BASH_HISTORY file?

Plain text that programs, servers and people write every day.

A .BASH_HISTORY file is a system file used by the GNU Project's Bash shell to store a record of previously executed commands. It contains plain text data and is typically accessed or modified by terminal applications like Apple Terminal or GNU Bash. These files are commonly found on operating systems such as Mac OS X.

Programs that open .BASH_HISTORY files

macOS
Apple Terminal, Mac OS X, GNU Bash
Linux
Bash
.BASH_HISTORY format details
DeveloperThe GNU Project

Related viewers

Every viewer is free to use.

Frequently asked questions

Is my .BASH_HISTORY file uploaded anywhere?

No. The file is read and highlighted for you.

Why do some characters look wrong (é, ł)?

That usually means the file was saved in one encoding and opened in another. We detect UTF-8, UTF-16 and the Windows-1250/1252 code pages automatically and show which one was used.

Can it handle huge log files?

Yes, up to 50 MB. Only the lines on screen are drawn, so scrolling stays smooth. Syntax colours are switched off for files over 1.5 MB to keep things fast.

How do the log level filters work?

We find levels like ERROR, WARN, INFO and DEBUG on each line. Lines without a level, such as stack traces, stay with the entry above them, so filtering to errors keeps the full trace.

Can I edit the file?

This is a viewer. To change code, download it or copy it into your editor. Converting encodings and line endings is planned.

Was this tool helpful?

Your rating helps us decide which tools to improve next.

Be the first to rate this tool.
Found a problem?