One Big Widget

Why an iOS widget cannot show a live web page

Search for how to put a website on your iPhone Home Screen and you get two different answers mixed together. One is Safari's Add to Home Screen, which gives you an icon that opens the site. The other is a widget, the panel that sits on the Home Screen and shows content without you opening anything. Most articles treat them as the same feature.

The short version: a widget cannot contain a live web page, because there is no web browser inside a widget. Apple's own documentation says what a widget can draw, how it gets new content, and how often the system lets it update. This page walks through what Apple states, with links, and says plainly where Apple publishes nothing.

A widget is a picture, not a live page. WidgetKit renders views in a separate process and cannot host a web view, so anything showing a web page in a widget is showing an image of it, refreshed on Apple's budget of roughly 40 to 70 times a day.

The two things people mean by putting a website on the Home Screen

Add to Home Screen is a Safari feature. You get an icon. Tapping it opens the page in Safari, or, if the site is set up as a web app, in its own window with the browser controls hidden. Apple's archived guide for web developers calls these icons Web Clips. Nothing from the page appears on the Home Screen. The icon is only a launcher.

A widget is a different system: a panel of content the Home Screen draws for you. Apple says widgets "elevate a small amount of timely, personally relevant information from your app, display it where people can see it at a glance." They are built with a framework called WidgetKit, and WidgetKit is where the limit lives.

A widget is a picture of a view, drawn somewhere else

Here is the part almost nobody explains. Your widget's code does not run while you look at the widget. Apple states it directly: "WidgetKit renders the views on your behalf in a separate process. As a result, your widget extension is not continually active, even if the widget is onscreen."

Apple is more specific in its page about widget buttons: "the system archives a view representation and only renders the views using these representations when applicable." Then the consequence: "the system can't run your code or update data bindings at the time it renders your widget."

That is the whole story. The app hands the system a finished description of what to draw, and the system stores it and draws it later. Nothing is running behind the widget on your Home Screen. A live web page is the opposite: it needs a process that is loading, running scripts and repainting continuously.

There is no web view a widget is allowed to use

Apple publishes a list of the SwiftUI views a widget may use. It opens with "Widgets can use many, but not all, SwiftUI views to present content." The list is text, images, buttons, toggles, labels, links, stacks, grids, shapes, gradients and a drawing canvas. No web view. Apple's page about building a widget adds that "WidgetKit ignores other views when it renders the widget's content."

The same page closes the obvious workaround. A developer would normally add a web view to a SwiftUI layout by wrapping the older WKWebView in a bridge called UIViewRepresentable. Apple: "Widgets can't use UIKit or AppKit views wrapped with UIViewRepresentable or NSViewRepresentable."

One newer wrinkle, stated honestly. Apple added a native SwiftUI WebView in iOS 26, described as giving "a complete browsing experience, including the ability to navigate between different webpages." It is not on WidgetKit's list of supported views, and Apple makes no statement either way about using it in a widget. That is an absence of a statement, not a statement, and a browsing experience is not something an archived drawing can be.

How a widget gets new content: the timeline

Instead of running continuously, a widget hands the system a schedule, which Apple calls a timeline. In Apple's words, "WidgetKit gets a timeline from your provider, and uses it to track when to update your widget." Each entry in it "has a date and time, and additional information the widget needs to display its view."

The timeline also says when to come back for a new one. Apple documents three reload policies. With atEnd, "WidgetKit requests a new timeline after the last date in the timeline's entries." With never, "WidgetKit doesn't ask for another timeline" until the app asks it to. With after, the app names a date, which is how a stock widget can finish on Friday and ask to be woken when the market opens. An app can also tell the system its data changed, or send a push notification. None of that makes a widget live. It makes it redraw.

How often a widget actually refreshes, in Apple's own numbers

A figure of 40 to 70 refreshes a day circulates in forums and blog posts, usually with no source. It is Apple's own. The page on keeping a widget up to date says "For a widget the user frequently views, a daily budget typically includes from 40 to 70 refreshes. This rate roughly translates to widget reloads every 15 to 60 minutes, but it's common for these intervals to vary due to the many factors involved."

Apple also sets a floor, saying timeline entries should be "at least about 5 minutes apart." Now note the hedging on the daily figure. "The budget allocation is dynamic and takes many factors into account," among them how often you look at the widget and whether the app is open. Each widget gets its own budget, so two copies of one widget count separately. Apple also "tunes the 24-hour window to the user's daily usage pattern," so the budget does not reset at midnight.

Some reloads do not count against the budget at all. Apple's list includes while the app is in the foreground, while it is the current Now Playing app, when you tap a button in the widget, and when the system language or text size changes. In StandBy, the refresh rate is system-defined and "doesn't count against its budget."

One number is missing from Apple's documentation. Widget extensions get killed for using too much memory, and crash logs posted by developers on Apple's own forums show a 30 MB limit, but Apple publishes no such figure, so treat it as developer reporting. Apple says only that "widgets can only access limited resources and a request may not have enough time to complete before the system halts the widget extension."

What iOS 17 changed, and what it did not

In iOS 17 widgets gained real buttons and toggles. Calling that interactivity overstates it. The mechanism is App Intents, and Apple is explicit about why the detour exists. Because of "the timeline mechanism and of rendering in a separate process, the system can't run your code or update data bindings at the time it renders your widget. This is where the App Intents framework comes into play." The button is a workaround for the limit, not a lifting of it.

So a widget button does not run code inside the widget while you look at it. It names an action the app published in advance. The system performs it and then, in Apple's words, "reloads the widget's timeline." The widget is redrawn afterwards.

What you do not get is arbitrary touch handling. No scrolling, no pinching, no typing, no tapping a link in a page. Apple notes that on a locked device, "buttons and toggles are inactive." Tapping anywhere else opens the app.

One genuine exception is time. Apple says a widget "can display time-based information that WidgetKit updates live," such as "a countdown timer that continues to count down even if your widget extension isn't running." Clocks and timers are real, but the system draws those, which is not a sign the widget is running.

So how does One Big Widget put a web page on the Home Screen

By rendering the page and showing you a picture of it. The app loads the page inside the app, where a real web view is allowed, takes an image of the part you chose, and hands that image to the widget, which draws it. An image is a supported widget view. This is the only way it can work.

What that costs you: the widget shows the page as it looked when it was last rendered, not as it looks now. It updates on the widget's schedule, inside the budget above, which in Apple's figures usually means every 15 to 60 minutes. Opening the app refreshes it. You cannot scroll it, tap a link in it, or fill in a form in it.

That makes it useful for some things and useless for others. A dashboard number, a league table, a price, a build status, a train time: worth a glance every half hour. A live chat window, a video, a map you want to pan: no, and no iOS widget can do those. Anything claiming otherwise is describing an icon that opens Safari.

Questions

Can any iOS widget show a live, scrolling web page?

No. Apple's list of views a widget may use does not include a web view, and Apple states that widgets cannot wrap UIKit or AppKit views with UIViewRepresentable, which is how a web view would otherwise be embedded. Apple also states that the system renders widgets from an archived view representation and cannot run your code at the time it draws the widget. A scrolling, interactive page needs a running process, which a widget does not have.

Is Safari's Add to Home Screen the same thing as a widget?

No. Add to Home Screen gives you an icon. Tapping it opens the page in Safari, or in its own window if the site is configured as a web app. Nothing from the page is visible on the Home Screen itself. A widget draws content on the Home Screen. Many articles about putting a website on your Home Screen are describing the icon.

How often does an iPhone widget update?

Apple documents a dynamic daily budget rather than a fixed rate, and says that for a widget someone views frequently, a daily budget typically includes from 40 to 70 refreshes, roughly every 15 to 60 minutes, with the warning that these intervals commonly vary. Apple also says a timeline's entries should be at least about 5 minutes apart. Some reloads are exempt from the budget, including while the app is open and when you tap a button in the widget.

Why does my widget look out of date?

Usually because it has not been reloaded yet. Apple says the budget takes into account how often the widget is visible, when it last reloaded, and whether the app is running, and that if a widget sits on a Home Screen page you rarely visit, WidgetKit may reduce how often it reloads that widget and then reload it when you next look at the page. Opening the app is the reliable way to force a fresh render.

Is there a memory limit on widgets?

Apple does not publish a number that I could find. Apple says only that widgets can access limited resources and that the system may halt the widget extension. Developers on Apple's own forums report a 30 MB limit from crash logs, which is consistent across many reports but is not an Apple statement, so treat it as community reporting rather than documentation.

Didn't iOS 17 make widgets interactive?

It added buttons and toggles, through App Intents. Apple's explanation for why that framework is needed is that the system cannot run your code at the moment it renders the widget. A tap runs an action the app registered in advance, and then the widget's timeline is reloaded and it is drawn again. There is still no scrolling, typing, or tapping links inside the content.

All technical claims are from Apple Developer documentation: WidgetKit overview (https://developer.apple.com/documentation/widgetkit), Keeping a widget up to date (https://developer.apple.com/documentation/widgetkit/keeping-a-widget-up-to-date), SwiftUI views supported in widgets (https://developer.apple.com/documentation/widgetkit/swiftui-views), Creating a widget extension (https://developer.apple.com/documentation/widgetkit/creating-a-widget-extension), Adding interactivity to widgets and Live Activities (https://developer.apple.com/documentation/widgetkit/adding-interactivity-to-widgets-and-live-activities), Making network requests in a widget extension (https://developer.apple.com/documentation/widgetkit/making-network-requests-in-a-widget-extension), SwiftUI WebView (https://developer.apple.com/documentation/webkit/webview-swift.struct), and Apple's archived Configuring Web Applications guide for Add to Home Screen and Web Clips (https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html). Unverified: Apple does not publish a widget extension memory limit, so the 30 MB figure is developer-reported from crash logs on Apple's forums and is labelled as such. Apple makes no statement either way about whether the iOS 26 SwiftUI WebView can be used inside a widget extension; this page reports only that it is absent from Apple's list of supported widget views. The 40 to 70 refreshes figure, often cited without a source, is confirmed to be Apple's own wording in Keeping a widget up to date.

Make a web page widget

Get One Big Widget on the App Store

More about One Big Widget ยท Contact us