DEV Community: Locahl

Free hosts file editor alternatives: SwitchHosts, PowerToys, Terminal, and when to pay

Locahl — Mon, 20 Jul 2026 18:55:31 +0000

You can manage the hosts file without paying anyone. Plenty of people should.

This is the free stack, plus the one case where a one-time paid app is rational.

Free options that actually work

1. SwitchHosts

Best free GUI for most developers.

Win / Mac / Linux
Profiles and groups
Open source

Cost of free: flush DNS yourself; live with the Electron-style desktop footprint.

2. PowerToys Hosts File Editor (Windows)

Best free "just edit the file" tool on Windows if PowerToys is already installed.

Cost of free: weak multi-environment story, Windows only.

3. Terminal / text editor + sudo

Best free option for people who already script their machines.

sudo nano /etc/hosts
# then flush DNS for your OS

Or keep profile files and copy them into place.

Cost of free: no seatbelts unless you add backups and checks.

4. Built-in Notepad / TextEdit (elevated)

Works. Painful. Easy to edit a copy that is not the system file.

Use only for rare one-line changes.

5. Gas Mask

Free historically. Not a free recommendation in 2026. Unmaintained.

Paid option worth mentioning

Locahl

Not free. One-time purchase. Cross-platform.

You pay for automatic DNS flush, backups, and a more guided multi-environment UI.

Pay only if the free tools are costing you real time (stale DNS, broken hosts, no shared OS story).

Free vs paid decision

Stay free if:

you edit hosts weekly or less
you remember DNS flush
OSS or zero budget is the rule

Consider paid if:

you switch environments daily
teammates keep hitting Permission denied / stale cache
you want one tool on Windows, macOS, and Linux

Suggested free setups

Solo, mixed OS, free only

SwitchHosts + a shell alias for DNS flush.

Windows-only, rare edits

PowerToys Hosts + ipconfig /flushdns.

Power users

~/hosts-profiles/local
~/hosts-profiles/staging
./hosts-use <name>   # copies + flushes

Do not confuse "free editor" with "safe workflow"

Every free path still needs:

Backup before big edits
One active mapping per hostname
DNS flush after apply
Terminal verification before blaming the app

Those four steps matter more than the logo on the window.

Free default: SwitchHosts. If free is costing you time on flush and backups, Locahl is the paid cross-platform alternative.

PowerToys Hosts File Editor alternative (when you need more than an edit box)

Locahl — Mon, 20 Jul 2026 18:42:13 +0000

Microsoft PowerToys includes a Hosts File Editor. It is free, signed, and already on many Windows machines.

It is a good editor. It is not always a good hosts workflow.

What PowerToys Hosts does well

Opens the real Windows hosts file with the right elevation story
Simpler than hunting C:\Windows\System32\drivers\etc\hosts in Notepad
Free if you already use PowerToys
Fine for a handful of static lines

When people search for an alternative

You switch environments all day

Local shop in the morning, client staging after lunch, cutover IP at night. An editor with one big file turns into commented chaos.

You want named profiles you can toggle, not archaeology in comments.

You also use a Mac or Linux box

PowerToys is Windows-only. Your hosts process should not fork by OS if the team shares domain names.

You forget `ipconfig /flushdns`

Same bug as every other hosts tool without auto flush: file correct, browser wrong.

Alternatives on Windows

SwitchHosts

Free, open source, profiles, also runs on Mac/Linux.

Best PowerToys alternative when you need environment switching and maybe multi-OS later.

Locahl

Paid one-time. Windows, macOS, Linux. Automatic DNS flush and backups.

Best when PowerToys feels too manual and you want the apply step to include flush + safety.

Notepad as Administrator

Still works. Still easy to save the wrong copy or skip flush.

Only fine for rare edits.

Hostly / CLI hosts switchers

Interesting if you want hosts open Dev from scripts. Check that the project is maintained before you depend on it in CI.

Feature snapshot (Windows view)

Tool	Profiles	Auto flush	Multi-OS	Cost
PowerToys Hosts	Limited	No	No	Free
SwitchHosts	Yes	No	Yes	Free
Locahl	Yes	Yes	Yes	One-time
Notepad Admin	No	No	Manual	Free

Practical upgrade path

Keep PowerToys for now if you only have 5 stable lines
When you start commenting / staging blocks every week, move to SwitchHosts or Locahl
Always backup before the first import
After every apply:

ipconfig /flushdns
ping myapp.test

If PowerToys is "just an editor," that is not an insult. Editors are useful. Managers exist for the days the editor is not enough.

If you need profile switching and automatic DNS flush beyond PowerToys, try Locahl on Windows (and Mac/Linux when you need them). SwitchHosts stays the free profile-based option.

iHosts alternative for Mac developers who need Windows or Linux too

Locahl — Mon, 20 Jul 2026 18:34:42 +0000

iHosts is a clean macOS hosts editor. If your world is only Apple hardware, it can be enough.

The search for an iHosts alternative usually means one of three things:

You need the same tool on a Windows or Linux machine
You want a different price / feature mix
You are standardizing a mixed OS team

What iHosts is good at

Native Mac UI
Visual editing of hosts entries
DNS flush support in the Mac workflow
Fine for solo Mac local development

Where it stops fitting

No help for the teammate on Windows
No Linux desktop parity
Harder to document "everyone use the same hosts app" in a mixed stack company

If your README says "install iHosts" and half the team cannot, you do not have a shared tool. You have a Mac preference.

Alternatives

SwitchHosts

Free, open source, Win / Mac / Linux. Closest free iHosts alternative when OS coverage matters.

Tradeoff: flush DNS yourself after switches.

Locahl

Paid one-time, Win / Mac / Linux. Visual environments, automatic DNS flush, backups.

Tradeoff: not free. Worth it if the team already loses time to stale DNS and broken hosts edits.

Gas Mask

Do not use as your iHosts replacement. Abandoned path.

Terminal profiles

Works on Mac and everywhere else. Same scripts for the whole team.

Tradeoff: no GUI. Higher chance of drift without discipline.

Stay on iHosts

Valid if:

every developer is on macOS
your environments are simple
you are fine maintaining Mac-only docs

Migration checklist (iHosts → cross-platform)

Export or copy current hosts content
Backup /etc/hosts
Install SwitchHosts or Locahl on each OS you care about
Recreate local / staging profiles with identical hostnames
On Mac, confirm flush still happens (auto or script)
On Windows, confirm Admin write + ipconfig /flushdns
Verify with terminal before browser

ping -c 1 api.myapp.test

Identical hostnames across machines matter more than identical apps. The app just reduces mistakes.

Pick by constraint

Constraint	Pick
Free + multi-OS	SwitchHosts
Multi-OS + auto flush	Locahl
Mac-only forever	iHosts is fine
Scriptable everywhere	Terminal profiles

If you outgrew a Mac-only hosts app, Locahl covers Windows, macOS, and Linux with automatic DNS flush. SwitchHosts is the free cross-platform option.

Best hosts file managers in 2026: SwitchHosts, Gas Mask, and the rest

Locahl — Mon, 20 Jul 2026 18:20:12 +0000

If you edit /etc/hosts more than once a week, a dedicated manager beats Notepad-as-Admin.

Here is a clear map of the usual options in 2026, including the abandoned ones people still Google.

Who this list is for

Local domains like app.test instead of localhost:3000
Staging / pre-DNS cutover tests
Focus-mode site blocking via 0.0.0.0
Teams that need the same workflow on Windows, macOS, and Linux

The short list

SwitchHosts — best free default

Open source, cross-platform, profile switching, remote lists.

Choose it when price is zero and you accept manual DNS flush.

Locahl — best polished paid default

Cross-platform desktop app. Automatic DNS flush, backups, visual multi-environment flow. One-time purchase.

Choose it when you want fewer "why is the browser still wrong?" loops.

Gas Mask — legacy Mac only

Historically popular. Not maintained for modern macOS.

Do not start a new setup on Gas Mask. If you are on it, migrate.

iHosts — Mac-native GUI

Solid if your whole team is on macOS and you want a native editor.

Skip it if you need Windows or Linux parity.

PowerToys Hosts File Editor — Windows built-in-ish

Free with PowerToys. Good for quick edits.

Not a full multi-profile manager like SwitchHosts.

Terminal + profile files — best for scripters

Copy ~/hosts-profiles/$ENV over /etc/hosts, flush, verify.

Maximum control. You own backups and mistakes.

Hostly / CLI-first tools — automation angle

Useful when you need hosts switch inside scripts or CI, especially on Windows. Check maintenance and OS support before standardizing a team on one.

Comparison table

Tool	Platforms	Cost	Maintained	Profiles	Auto DNS flush
SwitchHosts	Win / Mac / Linux	Free	Yes	Yes	No
Locahl	Win / Mac / Linux	One-time	Yes	Yes	Yes
Gas Mask	Mac	Free	No	Yes	No
iHosts	Mac	Paid	Yes	Yes	Yes
PowerToys Hosts	Windows	Free	Yes	Basic	No
Terminal profiles	All	Free	DIY	DIY	DIY

Decision tree

Need free + cross-platform? → SwitchHosts
Need auto flush + backups + cross-platform? → Locahl
Mac only + native UI? → iHosts
Windows only + already use PowerToys? → PowerToys Hosts
Live in the shell? → profile files
Still on Gas Mask? → migrate to 1, 2, or 3 this week

Features that matter more than branding

Whatever you pick, insist on:

Easy elevated write to the real hosts path
Clear active vs inactive mappings
Backup before overwrite
DNS flush in the apply path (app or script)
Terminal verification habit (ping / getent)

Fancy UI without those five still wastes your afternoon.

Looking for a SwitchHosts alternative? Here is what actually differs

Locahl — Mon, 20 Jul 2026 16:13:13 +0000

SwitchHosts is still the most common free hosts manager. It works. It is open source. It runs on Windows, macOS, and Linux.

People search for a SwitchHosts alternative when something in the daily loop gets annoying: forgotten DNS flush, Electron footprint, or wanting clearer multi-environment switching.

This is a practical comparison, not a takedown.

What SwitchHosts is great at

Free and open source
Profiles / groups you can toggle
Remote hosts lists
Cross-platform
Active enough community for a niche tool

If that covers your needs, stay. Free is a real feature.

Why people look elsewhere

1. DNS flush is still your job

Change a profile, refresh the browser, still on the old IP. Classic.

You need an OS flush every time:

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Windows (Admin)
ipconfig /flushdns

# Linux (systemd-resolved)
sudo resolvectl flush-caches

Tools that flush automatically remove a whole class of "is hosts broken?" mornings.

2. You want stronger backups

A bad paste into hosts can take down local resolution for half your stack. Automatic pre-change backups matter more than people admit until it happens once.

3. You want a lighter or more guided UI

SwitchHosts is capable. Some teams want fewer panels and a clearer "what is active right now?" signal when jumping between client projects.

Alternatives to SwitchHosts

Locahl

Paid one-time desktop app (Windows, macOS, Linux).

Same problem space: manage hosts visually, switch environments. Adds automatic DNS flush and backups.

Pick it if SwitchHosts works but the manual flush / polish gap bothers you enough to pay once.

Terminal profiles

Keep separate hosts files and copy the active one into place. Scriptable. Free.

Pick it if you already live in the shell and do not want another desktop app.

Gas Mask

Mac-only legacy option. Do not migrate to Gas Mask in 2026. Migrate away from it.

iHosts

macOS-focused GUI. Fine for Apple-only setups.

PowerToys Hosts File Editor

Windows-only editor. Good for simple edits, weaker as a full SwitchHosts replacement if you depend on many named profiles.

Hostly (and similar CLI-first tools)

Newer Windows-oriented tools that advertise SwitchHosts import plus a CLI for scripts/CI. Worth a look if automation matters more than a polished cross-platform GUI.

Feature snapshot

Need	SwitchHosts	Locahl	Terminal	PowerToys
Free	Yes	No	Yes	Yes
Win / Mac / Linux	Yes	Yes	Yes	Win only
Profiles / environments	Yes	Yes	DIY	Limited
Auto DNS flush	No	Yes	DIY	No
Auto backups	No	Yes	DIY	No
Open source	Yes	No	N/A	Yes (PowerToys)

Should you switch?

Stay on SwitchHosts if:

free / OSS is non-negotiable
you remember to flush DNS
profiles already match your workflow

Try an alternative if:

you lose time to stale DNS every week
you want safer undo after bad edits
you share a Win/Mac/Linux team and want one consistent paid tool

Migration tip

Export or copy your SwitchHosts content first. Keep a raw /etc/hosts backup. Import into the new tool. Verify with terminal resolution before you uninstall anything.

ping -c 1 myapp.test
grep -n "myapp.test" /etc/hosts

Same checks you should already run with SwitchHosts.

If automatic DNS flush and backups are the reason you are shopping, look at Locahl as a SwitchHosts alternative. Keep SwitchHosts if free and OSS matter more.

Best Gas Mask alternatives in 2026 (hosts file managers)

Locahl — Mon, 20 Jul 2026 15:57:50 +0000

Gas Mask was the default Mac hosts app for years. Profiles, a simple UI, done.

It is no longer a safe default. Maintenance stalled, and modern macOS versions are a gamble. If you still rely on it, pick a maintained alternative before the next OS upgrade breaks your workflow.

What Gas Mask did well

Profile-based hosts switching on macOS
Simple mental model: enable a set, apply
Free

What you still need from any replacement:

Edit /etc/hosts without fighting permissions every time
Switch local / staging / cutover maps cleanly
Flush DNS after apply (or you will think the app is broken)
Prefer something that still gets updates

Alternatives worth considering

1. SwitchHosts (free, cross-platform)

Open source. Windows, macOS, Linux. Profiles, remote hosts sources, tray switching.

Best if you want free and you are fine flushing DNS yourself after changes.

Gap: no automatic DNS flush. After every switch, run the OS flush command or you keep seeing the old IP in the browser.

2. Locahl (paid, cross-platform)

Desktop app for Windows, macOS, and Linux. One-time purchase.

Built around the same job as Gas Mask (visual hosts editing + environments) with automatic DNS flush and backups when you change entries.

Best if you want Gas Mask’s simplicity without the abandoned-app risk, and you work on more than one OS.

3. iHosts (macOS)

Native Mac feel. Visual editor. Fine if you only care about Apple machines and like a Mac-only UI.

Gap: not useful for a Windows/Linux teammate using the same workflow.

4. Terminal + profile files (free)

Keep ~/dev/hosts-profiles/local and staging, copy into /etc/hosts with sudo, flush DNS.

Best if you hate GUI apps and already script your machine.

Gap: easy to leave conflicting lines, no safety net unless you build backups yourself.

5. PowerToys Hosts File Editor (Windows only)

Part of Macrosoft PowerToys. Clean editor for the Windows hosts file.

Best if you are Windows-only and already run PowerToys.

Gap: not a Gas Mask replacement on Mac, and not a multi-environment manager by itself.

Quick comparison

Tool	Platforms	Price	Maintained	Auto DNS flush
Gas Mask	macOS	Free	No	No
SwitchHosts	Win / Mac / Linux	Free	Yes	No
Locahl	Win / Mac / Linux	One-time	Yes	Yes
iHosts	macOS	Paid	Yes	Yes
Terminal profiles	All	Free	You	Manual
PowerToys Hosts	Windows	Free	Yes	Manual

How to migrate off Gas Mask

Uxport or copy your active hosts content while Gas Mask still opens
Save a backup of /etc/hosts
Install the replacement
Recreate profiles: local, staging, maybe blocklist
Apply one profile, flush DNS, verify with ping / getent before trusting the browser
Uninstall Gas Mask after a week of clean use

Do not delete Gas Mask on day one if it is the only place your profiles live.

Which one should you pick?

Stay free + cross-platform → SwitchHosts
Want auto flush + backups + Win/Mac/Linux → Locahl
Mac only, native UI → iHosts
Happy in the shell → profile files + scripts
Windows only → PowerToys Hosts File Editor

Gas Mask earned its reputation. It does not earn a place on a 2026 Mac setup anymore.

If you want a maintained Gas Mask-style workflow with automatic DNS flush on Windows, macOS, and Linux, try Locahl.

Fix Permission denied when editing /etc/hosts

Locahl — Thu, 16 Jul 2026 22:38:26 +0000

You open the hosts file, change one line, hit save, and get Permission denied.

That is normal. The system hosts file is protected on purpose.

Why it happens

On macOS and Linux, /etc/hosts is owned by root.

On Windows, C:\Windows\System32\drivers\etc\hosts needs Administrator rights.

A normal editor process cannot overwrite it.

macOS / Linux fix

Edit with elevated rights:

sudo nano /etc/hosts

Or open your editor as root:

sudo code /etc/hosts
# or
sudo vim /etc/hosts

Safer pattern: edit a copy you own, then install it:

cp /etc/hosts ~/hosts.work
# edit ~/hosts.work
sudo cp /etc/hosts "/etc/hosts.bak.$(date +%Y%m%d-%H%M%S)"
sudo cp ~/hosts.work /etc/hosts

Then flush DNS.

Windows fix

Start Notepad as Administrator
File → Open
Go to C:\Windows\System32\drivers\etc\
Set the filter to All Files
Open hosts
Save

If Notepad was not elevated, Windows often lets you open the file and then fails on save.

PowerShell alternative:

Start-Process notepad C:\Windows\System32\drivers\etc\hosts -Verb RunAs

Then:

ipconfig /flushdns

"I can edit but nothing changes"

That is a different bug:

you saved a copy in Downloads / Desktop
the line is still commented with #
DNS cache was not flushed
another line for the same hostname wins

Verify the live file:

grep -n "myapp.test" /etc/hosts

Avoid fighting permissions every day

Keep project hosts snippets in your repo or home folder. Copy them into place with one sudo command when needed.

That keeps the protected system file boring, and your editable copy easy to version.

Quick recovery if you break hosts

You should still be able to reach the machine by IP and local loopback. Restore from your backup:

sudo cp /etc/hosts.bak.YYYYMMDD-HHMMSS /etc/hosts

If you did not make a backup, most OS installs still have a minimal localhost block you can recreate. Do that before you go hunting for network bugs.

If you switch hosts a lot, a small desktop manager helps keep profiles and DNS flush in one place: Locahl.

DNS not updating after hosts file change? Fix it in order

Locahl — Thu, 16 Jul 2026 22:32:35 +0000

You edited the hosts file. The line looks correct. The browser still opens the old site.

Do not rewrite the hosts file again yet. Walk the stack in order.

1. Confirm the file that actually loaded

macOS / Linux:

grep -n "example.com" /etc/hosts

Windows (Admin PowerShell):

Select-String -Path C:\Windows\System32\drivers\etc\hosts -Pattern "example.com"

Check for:

a # commenting the line out
a second line for the same hostname later in the file
a typo in the hostname

If the terminal cannot see the line, the browser will not either.

2. Flush the OS DNS cache

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Windows (Admin):

ipconfig /flushdns

Linux with systemd-resolved:

sudo resolvectl flush-caches

3. Ask the OS, not the browser

# macOS / Linux
ping -c 1 example.com
getent hosts example.com

Windows:

ping example.com
nslookup example.com

If the terminal shows the wrong IP, stop. Fix hosts or flush again. Do not debug the app yet.

On some systems nslookup talks to a DNS server and can ignore hosts. Prefer ping / getent for hosts checks.

4. Clear browser DNS

Browsers cache names too.

Quit the browser fully (not just the tab)
Reopen and retry
Chrome: chrome://net-internals/#dns → Clear host cache
Try a private window once, to rule out extensions

5. Watch for HTTPS and HSTS traps

Hosts can point www.client.com at staging, while the browser still forces HTTPS and an old certificate story.

Symptoms:

certificate warnings
redirects back to production
cookies scoped to the real domain behaving oddly

For local-only work, prefer .test names. For cutover tests, expect TLS quirks and test with curl too:

curl -vI https://www.client.com

6. Docker and VPN layers

If the browser is on the host but the service is in Docker, your laptop hosts file may not be what the container uses.

If a VPN or corporate DNS is active, flush again after connect/disconnect. Some agents re-inject resolvers.

Short checklist

Line present and uncommented in the real hosts file
One active mapping per hostname
OS DNS flushed
Terminal resolves the expected IP
Browser DNS cleared
Only then debug the app, proxy, or TLS

Most "hosts is broken" reports die at step 3 or 4.

If you switch hosts a lot, a small desktop manager helps keep profiles and DNS flush in one place: Locahl.

Use a custom local domain instead of localhost:3000

Locahl — Thu, 16 Jul 2026 22:28:29 +0000

http://localhost:3000 works. It also breaks a few real-world checks early:

cookies scoped to a real-looking host
absolute URLs in emails and webhooks
multi-app setups (app, api, admin)
OAuth redirect allowlists that hate bare localhost quirks

A local hostname like myapp.test is often cleaner.

1. Add the hostname

In /etc/hosts (macOS/Linux) or C:\Windows\System32\drivers\etc\hosts (Windows):

127.0.0.1   myapp.test
127.0.0.1   api.myapp.test

Prefer .test. It is reserved for testing. Avoid inventing fake .com names you might later need for real DNS.

Flush DNS after saving.

2. Point your app at it

Many stacks already bind 0.0.0.0 or 127.0.0.1. You only change the URL you open:

http://myapp.test:3000

If the framework reads HOST / APP_URL:

APP_URL=http://myapp.test:3000

Keep the port unless you put a reverse proxy in front.

3. Optional: drop the port with a proxy

Caddy example:

myapp.test {
  reverse_proxy localhost:3000
}

Then open http://myapp.test. Same idea with nginx or Traefik.

4. HTTPS locally

Some features need secure cookies or HTTPS redirects.

Options:

Caddy or mkcert for a local cert on myapp.test
Your framework's built-in HTTPS in development

Do not fight browser warnings with a public domain pointed at 127.0.0.1 unless you control that name.

5. Frontend and API on sibling hosts

127.0.0.1   app.myapp.test
127.0.0.1   api.myapp.test

Frontend on :3000, API on :4000. CORS and cookie domains become closer to production:

Domain=.myapp.test

That is often the whole reason to stop using plain localhost.

Checklist when it "does not work"

Hosts line exists and is not commented
DNS cache flushed
App is listening on the port you typed
You opened myapp.test, not localhost
Proxy config matches the hostname if you use one

Terminal check:

ping -c 1 myapp.test
# should show 127.0.0.1

When to skip this

Throwaway demos and single-file experiments are fine on localhost.

Reach for a custom local domain when cookies, redirects, or multiple services start fighting you. One hosts line usually ends the fight.

If you switch hosts a lot, a small desktop manager helps keep profiles and DNS flush in one place: Locahl.

How to block websites with the hosts file

Locahl — Thu, 16 Jul 2026 22:14:24 +0000

You can block a domain on your machine without installing another browser extension.

Point the hostname at a dead address in the hosts file. The OS resolves it locally and the site never loads.

This is blunt. It works for distraction sites, telemetry hosts you do not need, and quick local tests.

The pattern

0.0.0.0   www.example.com
0.0.0.0   example.com

0.0.0.0 is the usual choice. Some people use 127.0.0.1. Both stop the real site from loading. 0.0.0.0 avoids sending traffic to a local server you might already run.

Block both apex and www if the site uses both.

macOS and Linux

Edit hosts:

sudo nano /etc/hosts

Add your lines, save, then flush DNS:

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux (systemd-resolved)
sudo resolvectl flush-caches

Windows

Open Notepad as Administrator, open:

C:\Windows\System32\drivers\etc\hosts

Add the same style of lines, save, then:

ipconfig /flushdns

Verify

ping -c 1 www.example.com

You should see 0.0.0.0 or a failed route, not the real public IP.

Browser still loading the site? Quit it fully and reopen. Chrome also has its own DNS cache under chrome://net-internals/#dns.

What this does not block

Apps that hardcode IPs
Sites reached through a VPN or proxy that ignores your hosts file
HTTPS hosts you only blocked under the wrong name (example.com vs www vs a CDN host)
Mobile apps on another device (hosts is local to that machine)

For team-wide or network-wide blocking you need DNS or firewall rules, not a laptop hosts file.

Keep it tidy

Group blocks under a comment:

# focus mode
0.0.0.0   www.reddit.com
0.0.0.0   reddit.com
0.0.0.0   www.youtube.com
0.0.0.0   youtube.com

When you need the site again, comment the lines or delete them and flush DNS.

Safety note

Do not block domains your OS or package manager needs unless you know what you are doing. A bad block looks like "the internet is broken" until you remember last night's edit.

Start with one domain, verify, then add more.

If you switch hosts a lot, a small desktop manager helps keep profiles and DNS flush in one place: Locahl.

Where is the hosts file on Mac, Windows, and Linux?

Locahl — Thu, 16 Jul 2026 22:01:29 +0000

You need to open the hosts file. You already know why. You just cannot remember the path.

Here it is for each OS, plus how to open it without fighting permissions.

Paths

OS	Path
macOS	`/etc/hosts`
Linux	`/etc/hosts`
Windows	`C:\Windows\System32\drivers\etc\hosts`

On Unix systems /etc/hosts is often a symlink into the real file. Edit the path above. Do not hunt for a second copy in your home folder.

Open it on macOS

Terminal:

sudo nano /etc/hosts

Or open it in your editor with elevated rights:

sudo code /etc/hosts
# or
sudo vim /etc/hosts

Save, then flush DNS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Finder will not let you edit /etc casually. Use the terminal or an editor launched with sudo.

Open it on Windows

Open Notepad as Administrator
File → Open
Go to C:\Windows\System32\drivers\etc\
Change the file type filter to All Files
Open hosts

Without admin rights Windows will open the file but refuse to save.

Then flush DNS:

ipconfig /flushdns

Open it on Linux

sudo nano /etc/hosts
# or
sudo vim /etc/hosts

Flush depends on the stack. Common options:

sudo resolvectl flush-caches
# or
sudo systemd-resolve --flush-caches

What a normal line looks like

127.0.0.1   localhost
127.0.0.1   myapp.test
# 203.0.113.10  staging.example.com

Rules that save time:

IP first, hostname second
Spaces or tabs both work
# comments out the rest of the line
One hostname per line is easier to read than a long list

Quick check after editing

# macOS / Linux
ping -c 1 myapp.test
# or
getent hosts myapp.test

Windows:

ping myapp.test

If the IP in the reply is wrong, the hosts line did not apply yet. Flush DNS and try again before changing the app.

Common mistakes

Editing a copy in Downloads instead of the system file
Saving without admin rights (Windows especially)
Leaving a # in front of the line you meant to enable
Forgetting the DNS flush
Using a real public TLD like .com for local names when .test would avoid surprises

Bookmark the path for your OS. You will need it again.

If you switch hosts a lot, a small desktop manager helps keep profiles and DNS flush in one place: Locahl.

How to switch local and staging domains with the hosts file

Locahl — Thu, 16 Jul 2026 21:53:52 +0000

You want shop.test on localhost during the day, then the real client domain pointed at staging, then maybe the same domain pointed at a new server before DNS moves.

You do not need dnsmasq for that. You need a clean way to switch mappings without leaving three conflicting lines in /etc/hosts.

Why one big hosts file fails

After a few months it often looks like this:

127.0.0.1   shop.test
127.0.0.1   api.shop.test
# 203.0.113.10  www.client.com
10.0.0.5    www.client.com
127.0.0.1   www.client.com

Same hostname, several intentions. The browser will not tell you which line won. It just resolves something.

Comments help for a day. They do not help when you are tired and switching contexts.

Use profiles instead of comments

Keep separate files. Only one is active at a time for a given hostname.

Example layout:

~/dev/hosts-profiles/
  local
  staging
  cutover

local

127.0.0.1   shop.test
127.0.0.1   api.shop.test
127.0.0.1   admin.shop.test

staging

203.0.113.40   www.client.com
203.0.113.40   api.client.com

cutover (pre-DNS migration test)

198.51.100.20   www.client.com
198.51.100.20   api.client.com

Apply a profile

macOS / Linux:

PROFILE=staging
sudo cp /etc/hosts "/etc/hosts.bak.$(date +%Y%m%d-%H%M%S)"
sudo cp ~/dev/hosts-profiles/$PROFILE /etc/hosts

Then flush DNS for your OS.

Windows: same idea. Keep profile files, back up the live hosts file, copy the profile over:

C:\Windows\System32\drivers\etc\hosts

Then:

ipconfig /flushdns

Small bash helper

#!/usr/bin/env bash
set -euo pipefail
PROFILE="${1:?usage: hosts-use <profile>}"
SRC="$HOME/dev/hosts-profiles/$PROFILE"
[[ -f "$SRC" ]] || { echo "missing $SRC"; exit 1; }

sudo cp /etc/hosts "/etc/hosts.bak.$(date +%Y%m%d-%H%M%S)"
sudo cp "$SRC" /etc/hosts

# macOS. Swap this block on Windows/Linux.
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
echo "Active hosts profile: $PROFILE"

Usage:

./hosts-use local
./hosts-use staging

Optional: base file + project overlay

If you want personal localhost names plus project-specific domains:

~/dev/hosts-profiles/
  _base
  project-shop-local
  project-shop-staging

Apply with:

cat ~/dev/hosts-profiles/_base \
    ~/dev/hosts-profiles/project-shop-staging \
  | sudo tee /etc/hosts >/dev/null

Keep _base small. Put production hostnames only in the project overlay so they are easy to turn off.

Pre-DNS cutover checklist

This is one of the best uses of hosts:

Put the production hostnames on the new server IP in a cutover profile
Apply the profile and flush DNS
Test login, cookies, HTTPS, redirects, anything that depends on the Host header
Switch back when you are done

Write the rollback next to the migration checklist. You will want it on cutover night.

Docker caveat

Hosts on your laptop affect the browser on your laptop.

Processes inside containers usually use Docker DNS, not your host /etc/hosts.

Browser to shop.test on the host: host hosts file
Container to another container: Compose service names or extra_hosts

Do not debug the wrong layer.

After every switch

# What does the OS resolve?
getent hosts www.client.com
# macOS alternative:
# dscacheutil -q host -a name www.client.com

# What is in the file?
grep -n "www.client.com" /etc/hosts

If the terminal IP is wrong, fix hosts first. Do not dig into the app yet.

When hosts profiles stop being enough

Move to dnsmasq, CoreDNS, or company DNS when you need:

lots of wildcards
many services added every week
one shared dynamic map for a whole team

Until then, separate profile files beat a single commented hosts file.

Start with three files

local for your .test domains
staging for client staging IPs
cutover left empty until migration week

Switch the whole file, flush DNS, verify in the terminal. That is the whole method.

DEV Community: Locahl

Free hosts file editor alternatives: SwitchHosts, PowerToys, Terminal, and when to pay

Free options that actually work

1. SwitchHosts

2. PowerToys Hosts File Editor (Windows)

3. Terminal / text editor + sudo

4. Built-in Notepad / TextEdit (elevated)

5. Gas Mask

Paid option worth mentioning

Locahl

Free vs paid decision

Suggested free setups

Do not confuse "free editor" with "safe workflow"

PowerToys Hosts File Editor alternative (when you need more than an edit box)

What PowerToys Hosts does well

When people search for an alternative

You switch environments all day

You also use a Mac or Linux box

You forget ipconfig /flushdns

Alternatives on Windows

SwitchHosts

Locahl

Notepad as Administrator

Hostly / CLI hosts switchers

Feature snapshot (Windows view)

Practical upgrade path

iHosts alternative for Mac developers who need Windows or Linux too

What iHosts is good at

Where it stops fitting

Alternatives

SwitchHosts

Locahl

Gas Mask

Terminal profiles

Stay on iHosts

Migration checklist (iHosts → cross-platform)

Pick by constraint

Best hosts file managers in 2026: SwitchHosts, Gas Mask, and the rest

Who this list is for

The short list

SwitchHosts — best free default

Locahl — best polished paid default

Gas Mask — legacy Mac only

iHosts — Mac-native GUI

PowerToys Hosts File Editor — Windows built-in-ish

Terminal + profile files — best for scripters

Hostly / CLI-first tools — automation angle

Comparison table

Decision tree

Features that matter more than branding

Related reads

Looking for a SwitchHosts alternative? Here is what actually differs

What SwitchHosts is great at

Why people look elsewhere

1. DNS flush is still your job

2. You want stronger backups

3. You want a lighter or more guided UI

Alternatives to SwitchHosts

Locahl

Terminal profiles

Gas Mask

iHosts

PowerToys Hosts File Editor

Hostly (and similar CLI-first tools)

Feature snapshot

Should you switch?

Migration tip

Best Gas Mask alternatives in 2026 (hosts file managers)

What Gas Mask did well

Alternatives worth considering

1. SwitchHosts (free, cross-platform)

2. Locahl (paid, cross-platform)

3. iHosts (macOS)

4. Terminal + profile files (free)

5. PowerToys Hosts File Editor (Windows only)

Quick comparison

How to migrate off Gas Mask

Which one should you pick?

Fix Permission denied when editing /etc/hosts

Why it happens

You forget `ipconfig /flushdns`