Setup & pairing
Does a TV remote app need Wi-Fi? Wi-Fi, infrared and Bluetooth compared
7 min read
Yes. A TV remote app on iPhone works over Wi-Fi, not infrared. No iPhone model includes an infrared transmitter, so an app cannot send the infrared pulses an older non-smart TV expects. The phone and the TV have to be on the same local network, and the TV has to expose a network remote service.
Why can't an iPhone use infrared?
An iPhone cannot send infrared because it has no infrared emitter to send it with. This is a hardware fact rather than a software restriction: Apple has never shipped an infrared transmitter in any iPhone, in any generation, so there is nothing for an app to switch on. No App Store listing, no setting, and no jailbreak changes that.
The confusion is reasonable, because for a while some phones did have one. Several Android handsets shipped with infrared blasters — parts of Samsung's Galaxy S line, HTC's One series, and a long run of Xiaomi phones — and their built-in remote apps really did drive any television in the room. Those apps do not have an iPhone equivalent, and the reason is the missing component rather than a gap in the App Store.
What does Wi-Fi control actually send?
A Wi-Fi remote sends a short, structured message over the local network to a service the television is already running. It is not a signal broadcast into the room and hoped for; it is a connection opened to a specific address, in the same way a browser opens a connection to a website.
What that message looks like depends on the brand, and the differences are real rather than cosmetic.
| Platform | What the app opens | What a button press sends |
|---|---|---|
| Samsung (Tizen) | A WebSocket connection on port 8002 | A small JSON message naming a key, such as KEY_VOLUP |
| LG (webOS) | A WebSocket connection on port 3001 | An ssap:// request for volume and playback; a plain-text frame on a second socket for the arrow keys |
| Roku | A plain HTTP connection on port 8060 | An HTTP request naming the key — Roku documents the whole interface publicly |
Two things follow from that shape. The traffic is trivially small — a key press is a few dozen bytes, which is why a phone remote feels instant on any network that works at all. And because it is a direct connection rather than a broadcast, the phone has to be able to route to the TV's address, which is the single condition everything else in this article depends on.
Does it need internet, or just a network?
Remote control needs a local network, not an internet connection. A router with the broadband unplugged still passes traffic between the devices attached to it, and a phone and a TV on that router can still talk to each other perfectly. Pulling the cable from the wall does not stop a Wi-Fi remote working.
Two honest caveats sit alongside that. Downloading the app in the first place obviously needs internet. And an app may use the internet for things that are not remote control — checking a subscription, or loading ads on a free tier — so "the remote works offline" is not the same claim as "the app behaves identically offline".
The mirror image matters more in practice: internet without a shared local network is useless. A phone that has dropped onto cellular data has a perfectly good connection to the internet and no route to the television three metres away. This is a genuinely common failure in houses with weak Wi-Fi, where the phone quietly hands over to 5G and the remote stops finding anything. Checking that the Wi-Fi symbol is showing is a faster diagnosis than it deserves to be.
It also means a Wi-Fi remote is a home-network tool with a hard boundary. It cannot reach the television from the office or from a holiday. Anything promising that is routing through a server, which is a different architecture with different privacy consequences — what the Local Network permission covers goes into why local-only is the shape these apps take.
What about Bluetooth?
Bluetooth is not a route a third-party iPhone app can take, even though it is the transport several modern TV remotes use. LG's Magic Remote and Samsung's recent remotes really do pair over Bluetooth rather than infrared, so the question is a fair one — the answer is that the door is closed from both sides.
- iOS does not let apps act as Bluetooth input devices. Presenting the phone as a keyboard or remote-style peripheral is not an ability Apple exposes to third-party apps, so an app cannot imitate the remote a TV already knows how to pair with.
- TV makers do not publish the pairing. The link between a set and its own remote uses a private profile and a pairing procedure the manufacturer controls. There is no documented way for other software to join it.
- The set has to be in pairing mode anyway, which is a menu operation on the TV — precisely the thing someone without a working remote cannot do.
So Bluetooth is the transport your TV's own remote may well be using, and it is not one an app on your phone can borrow. Wi-Fi is the only route available to third-party software on iOS, which is why every general-purpose iPhone TV remote works that way.
What should I use if my TV is not a smart TV?
A television with no network connection needs infrared, and there are three ways to get infrared out of a phone-shaped setup. None of them is an app on its own, and it is better to know that before installing one.
A replacement or universal physical remote
The cheapest and most reliable answer, and the one worth trying first. A universal remote programmed with the TV's brand code costs very little, needs no network, and keeps working when the Wi-Fi does not.
A Wi-Fi-to-infrared bridge
A small box that sits in the room, joins your Wi-Fi, and fires infrared at the TV on command. Sold as an "IR blaster hub" or "universal remote hub". The phone app talks to the hub over Wi-Fi and the hub does the infrared, so you get phone control of a non-smart TV. This is the option that works with the phone you already own.
A plug-in infrared dongle
A dongle that attaches to the phone's port and emits infrared directly, paired with its manufacturer's app. Fewer of these exist than there used to be, and support tends to be tied to one app, so check what it works with before buying.
If the television does have network features and simply has not been set up — many sets sold as smart have never been through Wi-Fi setup — connecting it once is all that is required. From there the ordinary route applies, and how to use your iPhone as a TV remote covers what to expect from each brand.
Common questions
Can an iPhone control a TV without Wi-Fi?
Not on its own. Without a shared local network there is no path from the phone to the television, and the infrared route that would not need one is unavailable because iPhones have no infrared transmitter. The workable version is an infrared bridge on Wi-Fi, which still needs a network — just not an internet connection.
Does any iPhone have an IR blaster?
No iPhone model has ever included one. This is occasionally confused with older iPod and Apple TV accessories that used infrared to control Apple hardware, but those were receivers on the Apple device, not transmitters in the phone.
Will a TV remote app work on mobile data?
No. Cellular data connects the phone to the internet, not to your home network, and remote control needs the second one. A phone that has switched from Wi-Fi to 5G loses the TV even though it looks online.
Does the TV need to be connected to the internet, or just the router?
Just the router. The television has to be reachable on the same local network as the phone; whether that network can reach the internet is irrelevant to the remote commands themselves.
The short version
Wi-Fi is the only transport available to an iPhone remote app: infrared is missing from the hardware, and Bluetooth is closed to third-party apps on both the phone and the television. What that needs is a local network shared with the TV, not an internet connection.
If the TV cannot join a network, a phone app is the wrong tool and an infrared bridge or a physical universal remote is the right one. If it can, the next question is usually whether it is showing up — the checklist for a TV that will not appear covers that, and the frequently asked questions on the home page cover the rest of the setup. More of the shared groundwork is in the setup and pairing guides.