Installation¶
Starship can be installed on virtually any platform through multiple methods. This guide covers installation and shell configuration for all major environments.
Prerequisites¶
Nerd Fonts (Recommended)¶
Starship uses symbols that require a patched font for proper display. Install a Nerd Font for the best experience:
Popular choices:
- FiraCode Nerd Font
- JetBrainsMono Nerd Font
- Hack Nerd Font
- MesloLGS Nerd Font
Installation:
Download from nerdfonts.com and install to ~/.local/share/fonts/:
After installation, configure your terminal emulator to use the Nerd Font.
No Nerd Font?
Starship works without Nerd Fonts, but some symbols won't display correctly. You can configure text-only symbols in your configuration. See the Styling guide for alternatives.
Installation Methods¶
Package Managers¶
Starship is not in the default repositories. Use the install script or Cargo:
Install Script¶
The official install script works on Linux and macOS:
With options:
# Install to custom location
curl -sS https://starship.rs/install.sh | sh -s -- --bin-dir /usr/local/bin
# Install specific version
curl -sS https://starship.rs/install.sh | sh -s -- --version v1.16.0
# Force reinstall
curl -sS https://starship.rs/install.sh | sh -s -- --force
Cargo (Rust)¶
If you have Rust installed:
Update existing installation:
Binary Download¶
Download precompiled binaries from the GitHub releases page:
# Example for Linux x86_64
curl -LO https://github.com/starship/starship/releases/latest/download/starship-x86_64-unknown-linux-gnu.tar.gz
tar xzf starship-x86_64-unknown-linux-gnu.tar.gz
sudo mv starship /usr/local/bin/
Shell Configuration¶
After installing the binary, configure your shell to use Starship.
Bash¶
Add to the end of ~/.bashrc:
Login vs Non-Login Shells
On some systems, you may need to add this to ~/.bash_profile as well for login shells.
Zsh¶
Add to the end of ~/.zshrc:
Fish¶
Add to ~/.config/fish/config.fish:
PowerShell¶
Add to your PowerShell profile (find location with $PROFILE):
Nushell¶
Add to your Nushell config:
Then add to config.nu:
Cmd (Windows)¶
Requires Clink. Add to the Clink startup script:
Configuration File¶
Create the configuration directory and file:
Alternative locations:
Starship looks for configuration in this order:
$STARSHIP_CONFIGenvironment variable~/.config/starship.toml$XDG_CONFIG_HOME/starship.toml
Use a custom location:
Verifying Installation¶
Check the installed version:
Test the initialization:
This should output initialization code. If it does, restart your shell or source your configuration:
Updating Starship¶
Uninstalling¶
Remove the Binary¶
Clean Up Configuration¶
Remove the shell initialization line from your shell config file.
Optionally remove the configuration:
Platform-Specific Notes¶
macOS¶
- Use iTerm2 or another terminal that supports true color
- Configure the font in Terminal Preferences or iTerm2 Profiles
- The default Terminal.app has limited color support
Linux¶
- Most modern terminals support true color
- If using a tiling window manager, ensure your terminal supports Nerd Fonts
- On servers, consider using a minimal configuration without Nerd Font symbols
Windows¶
- Windows Terminal is recommended for best results
- Ensure you're using PowerShell 7+ for full feature support
- WSL works well with Starship (configure your Linux shell inside WSL)
SSH Sessions¶
Starship works over SSH, but:
- The remote server needs Starship installed
- Your local terminal needs the Nerd Font configured
- Consider a minimal configuration for slow connections