Stable signalUnknownHigh-risk permissions
LiveHosts icon

LiveHosts

Switch your host/IP mappings in real time without editing your hosts file

Users10KCurrent public install base
Rating3.2Store average score
Reviews43Public review volume
Manifest versionV3Extension platform version
7-day growth0Net users gained this week
7-day growth rate0%Relative weekly velocity
Preview

LiveHosts Media preview

1 assets
Trend

User growth trend

Review user movement across collected snapshots.

User Growth Over Time

10K10K10K10K10K2026年7月15日2026年7月18日2026年7月21日Latest: 10K
Rating trend

7-day rating trend

View collected rating snapshots from the latest 7-day window to assess rating stability.

7-day rating change

Start
3.23
Latest
3.23
7-day rating change
0.00
3.133.183.233.283.332026年7月15日2026年7月18日2026年7月21日Latest: 3.23
2026年7月15日2026年7月21日
Growth overview

Daily, weekly, and monthly growth

Compare 1-day, 7-day, and 30-day net growth and growth rate.

1-day growthFlat
00%
7-day growthFlat
00%
30-day growthFlat
00%
Technical snapshot

Version, languages, and crawl freshness

Review publication date, version, supported languages, and crawl timestamps.

Version2.0.0
ManifestV3
Size57.78KiB
Languages1English
Published
Store updated
Last crawled
English
Overview

Product summary

Review the store description, core capabilities, and common use cases.

LiveHosts is a Chrome extension that aims at providing a working (even if sub-obtimal) solution to a common nuisance that many web developers have to deal with every day. If you have multiple versions of your websites sharing the same host names on multiple environments, you often need to switch the assignments in your OS hosts file.

Other extensions (like the life-saving HostAdmin) can help with the cumbersomeness, but changes to the hosts file usually take an inconvenient amount of time to actually affect the browser.

Unfortunately, there is no way to make Chrome direct requests for a hostname to a specific IP without a standard redirect - you could set up a smart HTTP proxy, but it's often not possible or not convenient.

This extension settles for a sub-obtimal approach: requests to the indicated hostnames are redirected to the chosen IPs with an additional Host header. The browser's address bar reflects this behaviour showing the hostname right after the IP (e.g. http://127.0.0.1/www.example.com/). The extension also tries to take care of all requests to either the IP or the hostname in a consistent way.

Issues

After the redirect, the user is effectively in a different domain that the one they expected. They may notice some functional differences:

Reviews

Recent review snapshot

Inspect the latest comments and rating distribution.

Store average score3.2Chrome Web Store aggregate rating, including ratings without synced review text
Synced text average3.2Average computed only from synced review bodies below
Reviews with text37Synced review bodies
Total ratings / reviews43Chrome Web Store public rating/review count

Store average score: 3.2. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.

5
15
4
3
3
4
2
3
1
12
Kenny Griffin2021年5月4日
2

The concept is cool, but it doesn't work for me. Installed it on a Mac on the latest version of Chrome. I input the settings and saved them, no redirects happened.

Language en
1 helpful · 0 not helpful
klemn 022021年3月6日
5

Only one I found so far that works. Great job

Language en
Ryan Sullivan2020年12月26日
4

It did the basics of what I was wanting it to do, but I was hoping to have the ability to also put a non-default port on the end of the IP address that it could use for that host name instead. That seemed to take Chrome back to as if I didn't have the entry at all.

Language en
Rahi Dehzani2020年7月5日
5

Just to the point and functional.

Language en
Luke Wayne2020年4月14日
2

Hard to use

Language en
1 helpful · 0 not helpful
Ultra Já2020年3月3日
5

Muito boa! Recomendo!

Language pt
tague _2019年11月27日
3

It's a nice concept, but it doesn't really work perfectly. Redirects break the system, so for example if I want to test a virtual host for "foo.mysite.com" on a local server 192.168.x.x, but the main page of "foo.mysite.com" specifies a redirect to "/login", for example, the mapping won't kick in again and it'll try to send me to 192.168.x.x/login without faking the hostname being used, so the virtual host doesn't end up being used. The same also happens with HTTP-to-HTTPS redirects.

Language en
5 helpful · 0 not helpful
Ellis Benus2019年10月7日
3

I don't think this will work with WordPress on a Local Web server installation? B/c it's changing the URL to IPaddress/wp-admin the server doesn't recognize it. Is there a way to make this work with WordPress on a WAMP installation?

Language en
1 helpful · 0 not helpful
yw6622019年9月30日
3

Guy, the behavior is incorrect. First of all <IP address> is not the same origin of <Hostname>. Chrome will consider the two sites in a totally different way. The request is correctly sent, and the server should work, but the thing is at the client side: Chrome does not work this way. Secondly it wont work with HTTPS. The certificate returned by the server is for <Hostname>, not for <IP address>. Surely it is still useful some way, but what I am really looking for is sth. that works exactly the same way /etc/hosts works.

Language en
2 helpful · 0 not helpful
Payam Baharan2019年8月21日
5

firstly, sorry for poor English language I have a live site and a local copy of it on xampp that I work on it for testing. I established a virtual-host in xampp server config to work on local version, I have to add "127.0.0.1 example.com" in host file to open site with domain instead of "http://localhost/" then by commenting this line I access to live version your addon worked for me but the URL start with 127.0.0.1 not example.com is there any way to solve this problem?

Language en