Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is PWAsForFirefox?
PWAsForFirefox is a tool that lets you install, manage, and run Progressive Web Apps in Mozilla Firefox. Firefox supports many PWA-related web APIs but does not offer a built-in way to install a site as a standalone app; this project fills that gap by creating a modified Firefox runtime so websites can run in their own window, with their own start menu entry and taskbar icon, and without tabs or an address bar. It provides both a command-line tool and a browser extension for installing and managing apps and their profiles.
How it works in practice
You install the browser extension, follow the in-browser setup instructions, and the extension handles creating and patching the native runtime and profile. Installed PWAs live in an isolated Firefox installation and profile, and you can install essentially any website as an app. Because the runtime is Firefox-based, installed apps retain support for Firefox extensions and built-in browser features.
Who it suits
- Firefox users who want app-like web tools without switching to another browser for that purpose.
- People who prefer separate windows and profiles for work, communication, or media sites instead of a crowded tab bar.
- Users comfortable with an extension plus a native component rather than a purely click-to-install browser feature.
Trade-offs to weigh
The setup is more involved than installing a PWA in a browser that supports it natively, since it relies on a modified runtime and profile that must be installed and kept patched. That isolation is also the main benefit: apps stay separate from your main Firefox session. If you want the simplest possible path, a browser with native PWA installation will be easier; if you want to stay in Firefox, this is the practical route.
For a concrete example, someone who uses a web-based chat or project tool all day could install it as a PWA so it opens in its own window with a taskbar icon, while keeping their normal browsing tabs untouched. Start by checking the project's installation and user guide pages, then install the extension and set up one app to see whether the workflow fits.
How do I install PWAsForFirefox on my system?
PWAsForFirefox installs in two parts: a native runtime/program on your computer, and a Firefox browser extension that drives it. The website's installation page is the authoritative sequence; the short version is below.
Basic installation flow
- Install the native program. Use the project's installer for your platform (Linux packages, Windows installer, or macOS package, depending on what the installation page lists). This creates an isolated Firefox installation and profile(s) used specifically for PWAs.
- Install the browser extension. Add the PWAsForFirefox extension to your main Firefox browser, then follow the in-browser setup instructions it presents. The extension is what lets you install, manage, and run PWAs and their profiles without touching the command line.
- Install your first PWA. Open the site you want in Firefox, trigger installation from the extension (or the command-line tool), and it appears as a standalone window with its own start/app menu entry and taskbar icon.
Which method to choose
| Situation | Recommended approach |
|---|---|
| You want a graphical, click-through setup | Browser extension plus in-browser instructions |
| You prefer scripting or headless management | Command-line tool |
| You only want to try one site quickly | Extension, one PWA, no extra profiles |
Practical notes
- The project uses a custom modified Firefox runtime, so your normal Firefox profile stays separate from the PWA profiles. This is the main reason installed PWAs feel app-like: no tabs, no address bar, own window.
- Automatic installation and patching are user-triggered, so expect to approve updates rather than have them happen silently.
- All Firefox add-ons and built-in features remain available inside installed PWAs, which matters if you rely on extensions for password managers or content blocking.
- If setup fails, the project's FAQ and help section are the intended first stop; the repository README has the fuller technical detail.
A sensible next step: read the installation page once end to end before running anything, then install the extension first so it can guide the native program setup. If you are on Linux and prefer package managers, check whether your distribution's repositories or the project's DEB/RPM packages are the smoother path for your system.
How do I install a website as a Progressive Web App in Firefox using this tool?
PWAsForFirefox adds standalone app installation to Firefox, which does not support it natively. You install a site as a PWA in two stages: first set up the tool itself, then install the site from Firefox.
Set up the tool
- Install the modified Firefox runtime and the companion browser extension. The project provides a command-line tool for installing, managing and running PWAs, plus an extension for in-browser control.
- Follow the in-browser installation instructions on the project's installation page. The extension is what connects the main Firefox browser to the native programs and to the isolated Firefox installation and profile(s) where PWAs are stored.
- If setup fails, the help section and FAQ page are the intended first stop.
Install a website as a PWA
- Open the site in your main Firefox browser with the extension active.
- Use the extension to install that site as a PWA. The project states that all websites can be installed, not only ones that ship a web app manifest.
- Launch the PWA from its own start/app menu entry or taskbar icon. It opens in its own window with no tabs and no address bar, which is the main reason to use it over a normal Firefox tab.
What you get, and the trade-offs
| Aspect | What this tool does | Practical effect |
|---|---|---|
| Runtime | Uses a separate modified Firefox installation and profile(s) | PWAs are isolated from your everyday browsing profile |
| Window | Own window, no tabs or address bar | Closer to a native app; less convenient for heavy tab use |
| Site support | Any website can be installed | Useful for internal tools and sites that never added PWA support |
| Extensions | Firefox add-ons and built-in features are supported | Your usual extensions can work inside the PWA |
| Updates | User-triggered installation and patching | You control when the runtime and profiles update |
A concrete scenario: someone who keeps a chat client, a project tracker and a webmail account in Firefox tabs can install each as a separate PWA, get distinct taskbar icons, and stop hunting through tabs. The trade-off is a second Firefox installation to maintain and update, plus the fact that each PWA is a full browser window rather than a lightweight tab.
Next step: check the project's user guide and FAQ at PWAsForFirefox before installing, since the setup order (runtime, then extension, then in-browser installation) matters. If you would rather avoid a separate runtime, compare with a browser that installs PWAs natively, such as Google Chrome or Microsoft Edge, where installation is a single menu action but you give up Firefox and its extensions.
What are the differences between PWAsForFirefox and native Firefox PWA support?
PWAsForFirefox exists precisely because Firefox itself does not offer native PWA installation. Firefox supports many of the underlying web APIs that PWAs rely on, but it lacks the piece that turns a website into a standalone system app — often called a Site Specific Browser (SSB). PWAsForFirefox fills that gap with a custom modified Firefox runtime, plus a command-line tool and a browser extension to install, manage and run PWAs as separate apps.
How they differ in practice
| Aspect | Native Firefox | PWAsForFirefox |
|---|---|---|
| Install as standalone app | Not supported | Supported via modified runtime |
| App window | Regular browser tab or window | Own window, no tabs or address bar |
| Start/app menu and taskbar entry | None | Yes, per installed PWA |
| Isolation | Shared browser profile | Separate Firefox installation and profile(s) |
| Add-ons and Firefox features | Available in the main browser | Available inside installed PWAs |
| Management | Not applicable | CLI tool plus extension for install, manage, run |
What this means for different users
If you only need a website open in a tab, native Firefox is simpler and requires nothing extra. If you want a site to behave like a desktop application — its own icon, its own window, no browser chrome — PWAsForFirefox is the option that provides it.
The trade-off is setup and maintenance. PWAsForFirefox installs a separate Firefox runtime and keeps PWA profiles apart from your main browsing profile. That isolation is useful for keeping work apps separate from personal browsing, but it also means a second installation to update and manage. The extension handles much of this from within Firefox, and the project notes support for user-triggered automatic installation and patching.
A practical starting point: pick one site you use daily, such as a webmail or chat service, install it through the extension, and see whether the standalone window suits your workflow before converting more. If you prefer keeping everything in one browser profile, native Firefox remains the lower-friction choice. For background on how PWAs are meant to behave across platforms, web.dev is a useful reference.
Can I use Firefox extensions and add-ons within installed PWAs?
Yes. PWAsForFirefox is built around a modified Firefox runtime, and its feature list explicitly includes support for all Firefox add-ons and extensions inside installed PWAs. That is a meaningful difference from the browser's own limited PWA behavior, which it addresses by adding a standalone, app-like installation layer.
What that means in practice
- Each installed PWA runs in its own isolated Firefox installation and profile, so extension state travels with that PWA's profile rather than your main Firefox profile.
- Because the runtime is Firefox, Firefox's built-in features (for example, container-like profile separation, developer tools, and privacy settings) remain available in the PWA window.
- PWAs launch without tabs or an address bar, so extensions that depend on toolbar buttons may have limited visible UI even though they still run.
A concrete scenario
Suppose you install a chat or documentation site as a PWA and want your password manager, an ad blocker, and a translation extension available only there. You would install those add-ons into that PWA's profile. Your main Firefox browsing stays untouched, and the PWA keeps its own extension set.
Decision criterion
Choose this approach if you want Firefox's extension ecosystem inside app-like windows and are comfortable with per-PWA profiles. If your main goal is simply having a site open in its own window without managing separate profiles, Firefox's own window features may be enough.
Next step: check the project's user guide and FAQ on PWAsForFirefox before installing, since setup involves a browser extension plus a native runtime.
How do I troubleshoot common issues with PWAsForFirefox?
Start with the project's own help resources, then narrow down whether the problem is in installation, the PWA's own profile, or the underlying Firefox runtime. PWAsForFirefox is a tool for installing, managing and running Progressive Web Apps in Mozilla Firefox, using a modified Firefox runtime plus a command-line tool and a browser extension. Because several moving parts are involved, most issues trace back to one of those layers rather than to the website itself.
First stops
- Check the project's FAQ and help section before changing anything; common setup questions are usually answered there.
- Follow the user guide for the exact installation and usage steps, since skipping the extension setup or the in-browser installation flow is a frequent cause of a PWA not appearing.
- If the extension is involved, install it first and follow the in-browser instructions, as the project recommends.
Match the symptom to the layer
| Symptom | Likely layer | Practical check |
|---|---|---|
| PWA does not install or does not appear as an app | Extension or install flow | Re-run installation from the browser extension; confirm the site is being installed as a PWA rather than opened as a normal tab |
| PWA opens but looks like a normal browser window with tabs | Runtime or profile | Confirm you launched the installed app entry, not the main Firefox window; installed PWAs are meant to have no tabs or address bar |
| Login or site data missing in the PWA | Isolated profile | Remember PWAs use their own isolated Firefox profile, so they do not share cookies or sessions with your main Firefox |
| Extension or add-on behaviour differs inside the PWA | Add-on support | PWAs support Firefox add-ons and built-in features, but check whether the specific add-on needs configuration per profile |
| Updates or patching fail | Runtime installation | Use the user-triggered installation and patching flow described in the guide |
A concrete troubleshooting sequence
- Reproduce the issue once, noting whether it happens in the main Firefox browser, in the installed PWA window, or during installation.
- Confirm the browser extension is installed and that you followed the in-browser installation instructions.
- Check the FAQ and help pages for your exact symptom.
- If the PWA runs but behaves oddly, test the same site in your normal Firefox profile to separate a site problem from a PWA profile problem.
- If installation or patching is the issue, re-run the user-triggered installation or patching step rather than manually editing files.
When to look beyond the tool
If the site fails in normal Firefox too, the problem is with the site or your network, not PWAsForFirefox. If only the installed app misbehaves, treat it as a profile or runtime issue. For background on what PWAs are and how they behave across browsers, see MDN Web Docs and web.dev. For Firefox itself, Mozilla is the authoritative source.
User reviews (0)