Preview: These docs are available early so you can start using them now. Some pages may still be incomplete, outdated, or change as WebLibre develops.

Custom Tabs & External Links

WebLibre can sit in the middle of several Android link flows:

  • another app sends a link into WebLibre

  • a link inside WebLibre could open a native app instead

  • WebLibre is used as a lightweight browser overlay

These are related, but they are not the same setting.

Intent Gatekeeper

Before External Link Handling even runs, the Intent Gatekeeper decides whether the source app is allowed to push the link into WebLibre at all.

When a new app sends a link, WebLibre asks whether to Allow once, Always allow, or Block it. You can manage saved decisions per app from Settings > Privacy & Security > Intent Gatekeeper, and respond to blocked-link notifications without opening the browser.

For the full feature, see Intent Gatekeeper.

Links Sent To WebLibre

When another Android app sends a link to WebLibre, External Link Handling decides how that link opens.

You can set it in Settings > Browsing > External Link Handling.

The choices are:

  • Prompt — ask each time

  • Regular — always open in a regular tab

  • Private — always open in a private tab

  • Isolated — always open in an isolated tab (shown when Show Isolated Tab UI is enabled)

This is useful for links that come from messaging apps, email apps, social apps, or Android share targets.

When another app shares text or a URL into WebLibre (for example via the Android share sheet, or a PROCESS_TEXT selection action from another app), the same routing logic applies. Site assignments can still send matching URLs to their assigned container, while the separate Custom Tabs setting decides whether another app may use the lightweight overlay.

Links That Could Open Another App

Some links inside WebLibre match apps already installed on your device, such as maps, video apps, shopping apps, or social apps.

The Open Links in Apps setting controls that behavior.

Find it in Settings > Browsing > Open Links in Apps.

The choices are:

  • Always — open the matching app without asking in ordinary browsing

  • Ask before opening — show a prompt first (the default)

  • Never — stay inside WebLibre

Choose Never if you want WebLibre to stay in control. Choose Always if you usually prefer the dedicated app.

Remember a Site’s Choice

When WebLibre asks about opening an app, you can choose Remember for this site. Manage or remove saved choices under Settings > Browsing > Open Links in Apps > Remembered site rules. You can also set a site’s preference directly in its site settings: Follow default, Open in app, or Keep in browser.

By default, the page continues loading while you decide. Turn on Wait for your answer if you want it to pause until you respond. Dismissing a prompt without choosing does not save a decision.

Some sign-in flows need a link back from another app. Allow login app callbacks is on by default to support these even when Open Links in Apps is set to Never. You can turn it off in the same settings if you do not want that exception.

If a link points to an app you have not installed and has no web fallback, Offer app store fallback can offer to open the app store. It is off by default; enable it in the same browsing settings if you want that choice. It only applies when Open Links in Apps is set to Always or Ask before opening — it has nothing to offer a fallback for when set to Never.

Private and Container Rules

In private browsing, over Tor or a proxy, or inside a strict container, WebLibre asks before opening another app even if your default is Always. It does not offer to remember the answer in those contexts. Custom Tabs follow the selected mode unless another protection applies. Opening a native app can reveal your activity to that app and may link browsing identities you intended to keep separate.

Cookie-isolated containers can have their own App Links mode and remembered site rules. Configure these in the container settings if one container should keep links in WebLibre while another uses native apps. Certain sensitive links, such as cryptocurrency wallet links, always require an explicit choice and cannot be remembered, regardless of the default.

Open in App

WebLibre also exposes Open in App as a top-level item in the browser menu, and as an action in places such as:

  • context menus on links

  • the open-link sheet for shared or detected links

  • sharing or page actions when relevant

This is useful when your default preference is to stay in WebLibre, but a specific link makes more sense in its native app.

Open in Custom Tab

In current WebLibre builds, shared or externally opened links can also offer Open in custom tab.

A custom tab is a lighter browser window meant for short visits. It is useful when you want to:

  • check one page without fully moving into your main tab workflow

  • keep the visit feeling tied to the app that launched it

  • return quickly after reading or confirming something

WebLibre can also offer a private variant of that custom-tab flow where supported.

When WebLibre Is Used as a Lightweight Browser

Some Android apps can open links in WebLibre as a custom-tab style overlay instead of sending you to the full browser experience.

In practice, that usually means:

  • a simpler browser surface

  • a close button to return to the calling app

  • less context switching than opening a full browser session

This is useful for one-off reads, sign-in confirmations, or checking a page without leaving the original app for long.

If a Custom Tab is routed through Tor or a proxy when WebLibre is starting, it waits for the connection rather than silently sending the link directly. If you choose an option to open it normally instead, check whether that changes the route before continuing. See Proxy Connections.

Turn Custom Tabs Off

The Custom Tabs setting controls whether other apps may open links this way at all.

It is enabled by default. When you turn it off, links and shared URLs sent to WebLibre open as normal tabs in the main browser instead of the lightweight overlay.

Find it in Settings > Browsing > Custom Tabs.

Which Setting Matters When

Use this rule of thumb:

  • Intent Gatekeeper — controls whether another app is allowed to send a link into WebLibre at all

  • External Link Handling — a link is coming into WebLibre from another app and was already allowed in; decide which tab type to use

  • Custom Tabs — controls whether other apps may open links as a lightweight in-app tab at all

  • Open Links in Apps — a link inside WebLibre might leave the browser for another app

  • Open in App — one-time manual action for a specific link

  • Open in custom tab — one-time action for a lighter browser window

Practical Examples

"I tap a link in a messenger app and want WebLibre to ask me each time"

Use Settings > Browsing > External Link Handling > Prompt.

"I want map links to keep opening in the browser instead of the Maps app"

Use Settings > Browsing > Open Links in Apps > Never.

"I usually stay in WebLibre, but this one video should open in the video app"

Use Open in App for that specific link.

"I only need a temporary browser window and want to return quickly"

Use Open in custom tab when WebLibre offers it.

Related Pages