Your PC can serve a website to the whole internet without buying hosting and without touching your router settings. Two commands do the job — one starts a web server on your PC, the other connects it to the internet through a tunnel. This page explains the complete flow and the safety rules that are not optional.
A website normally lives on a rented server that stays awake all day. But for learning, testing and showing demos, your own PC is already a perfectly good web server — it only lacks a public door. The two-command method shown in the video gives it that door. The first command runs a small web server on your PC. The second opens a tunnel from your PC to a public address on the internet. Anyone who opens that address sees your site, served live from your desk.
Illustrative flow. The exact commands and the tool are the ones shown in the video — the pattern underneath them is always this.
Before any command runs, build the thing you are about to publish. A web server serves the whole folder it is pointed at — every file in it becomes downloadable by name, including anything you forgot was in there. So create a fresh, clean folder that contains only the demo or test site: its pages, images and style files, and nothing else. No backups, no exported documents, no configuration files, no personal photos riding along. This one habit prevents most of the accidents people have with this trick.
The first command starts a small web server on your PC and points it at your clean folder. At this stage nothing is public: the site answers only on your own machine, at a local address such as localhost with a port number. Open that address in your own browser and click through every page. If the site is broken here, the tunnel in step two will faithfully publish a broken site to the world — local testing is not a formality.
The second command starts the tunnel. The tunnel tool connects outward from your PC to the tunnel service and holds that connection open. The service hands you a public URL. From that moment, anyone anywhere who opens that URL is connected through the tunnel to the little server on your desk. Note what did not happen: you did not change any router setting, ask your ISP for anything, or open any port at home. That is why this works even on connections where traditional hosting from home fails completely.
Publishing a PC is publishing an attack surface, so treat these as setup steps, not fine print. Serve only what you mean to publish. Keep whatever app you serve updated, because its bugs are now internet-facing. Protect your tunnel account like a house key — its password and token decide who can open tunnels into your machine, so use a strong password and two-factor authentication. Never expose admin panels, Remote Desktop or file shares through a tunnel. And when the demo ends, stop the tunnel. A fun demo is not production hosting, and the difference is mostly these rules.
Now test the public path the way a stranger will use it. Pick up your phone, switch Wi-Fi off so you are on mobile data, and open the public URL. Check that pages load, images appear and links work — links that secretly point back at localhost work for you and break for everyone else, and this test is how you catch them. While visitors use the site, keep the terminal visible: requests scroll past live, and you can see both happy browsing and anything strange. Only after this test should the link go to anyone else.
Your website exists only while your PC is switched on, awake and connected. The laptop lid closes, the site dies. Windows restarts for an update, the site dies. That fragility is completely fine for a demo, a class or a test — and completely wrong for anything people depend on. When you are done, stop the tunnel first and the server second, then open the public URL on your phone once more and confirm it no longer loads. The other pages in this set go deeper: how tunnels defeat CGNAT, the security checklist, why free links keep changing, and when real hosting is simply the right answer.
See the exact two commands from the video run live — the local server starting, the public URL appearing, and the site opening from another device.
Watch Full VideoNo. That is the whole point of the tunnel method. Your PC connects outward to the tunnel service, so no router changes, no static IP and no public IP at your home are needed. It also works on connections where the ISP gives you no public address of your own at all, such as the CGNAT connections that are very common in India.
The tunnel tools used for this kind of trick offer free tiers that are genuinely enough for learning and demos. Free tiers come with limits: the public address usually changes every time you restart the tunnel, and speed or connection counts can be capped. A permanent address and heavier use generally need an account plan or real hosting.
Technically it will load. You still should not. The site dies when your PC sleeps, updates or loses power, your home upload speed limits every visitor, and your broadband terms may not allow running public servers. Use this method for demos and learning. Use real hosting for anything customers depend on.