content://cz.mobilesoft.appblock.fileprovider/cache/blank.html: What It Is & How to Fix It
Last updated: November 2026
Quick Answer: content://cz.mobilesoft.appblock.fileprovider/cache/blank.html is a harmless placeholder page created by AppBlock, the app and website blocker from MobileSoft. It loads when AppBlock stops a blocked site or app. It is not a virus. If it shows up when it shouldn’t, check your AppBlock schedules, clear its cache, and re-grant its permissions.
If you copied that long address out of Chrome or a notification and pasted it into Google, you’re in the right place. It looks like system code, which makes it easy to assume something is wrong with your phone. In most cases nothing is. Below you’ll find what the address means, when it’s normal and when it’s worth fixing, and the steps that actually solve it.
This guide is part of our overview of strange app names and content:// addresses on Android.
What Does content://cz.mobilesoft.appblock.fileprovider/cache/blank.html Mean?


The address is a content URI. Android uses these to let one app hand a file to another app without exposing the real file path on your storage. Here’s each part in plain English:
| Part | What it means |
|---|---|
content:// |
The file is shared through Android’s content provider system, not opened from a normal web address. |
cz.mobilesoft.appblock |
The package name of AppBlock. MobileSoft is the Czech developer behind it, which is why it starts with cz. |
.fileprovider |
AppBlock’s FileProvider, the Android component that safely shares files from inside the app. |
/cache/ |
The file lives in AppBlock’s temporary cache folder. |
blank.html |
A small, empty HTML page used as a stand-in for blocked content. |
Put together: AppBlock has handed your browser (or another app) an empty page from its own cache. That is how it “replaces” something it was told to block.
Is It a Virus or Normal?

It is not a virus. The file belongs to AppBlock, sits in its private cache, and contains nothing. It can’t read your data or install anything. The real question is whether you expected to see it.
Usually normal
- You opened a site or app that is on your AppBlock block list.
- A schedule, usage limit, or Strict Mode session is active right now.
- You tapped a link inside a blocked app and it opened in a browser tab.
- The blank page appears for a moment, then the AppBlock block screen shows up.
Worth fixing
- Sites you never blocked open as a blank page.
- The blank page stays even after you pause or end all schedules.
- It shows up in apps you don’t use with AppBlock at all.
- You don’t remember installing AppBlock (see the section further down).
Why It Shows Up in Chrome, Apps, or WebView


Website blocking on Android works through the Accessibility permission. AppBlock watches the address bar in supported browsers, and when it spots a blocked site or keyword it steps in. Sending the browser to its own blank page is a quick way to stop the real page from loading before the block screen appears.
Sometimes the handoff gets stuck. Common reasons include:
- A leftover tab. The browser reopens the last tab after a restart, and that tab still points at blank.html.
- Old cached data in AppBlock after an update.
- A missing permission. If Display over other apps is off, AppBlock can load the blank page but can’t draw its block screen on top, so you only see white.
- Battery optimization killing AppBlock in the background, leaving it half-working.
- A broad rule, such as a keyword that matches many sites. AppBlock’s help center notes that blocking a specific page on a domain can block the whole main site.
How to Fix It (Step-by-Step)

Work through these in order. Most people are sorted by step 3. Exact menu names differ a little between Samsung, Xiaomi, Pixel, and other phones, so look for the closest match on yours.
- Check your AppBlock rules. Open AppBlock and look at your active schedules, usage limits, and Strict Mode. Make sure the site you’re trying to open isn’t on a list, and look for broad keywords that could be catching it by accident. If Strict Mode is on, you may need to wait until the session ends before you can change anything.
- Close the stuck tab. In Chrome or your browser, close the tab showing blank.html completely, then open the site in a fresh tab. This alone fixes a lot of “it keeps coming back” cases.
- Clear AppBlock’s cache. Go to your phone’s Settings > Apps > AppBlock > Storage and tap Clear cache. Don’t tap “Clear storage” or “Clear data” unless you’re ready to set the app up again, because that wipes its settings.
- Re-check the required permissions. AppBlock’s official help lists these as the most important ones on Android:
- Usage access, so it can detect which app is open
- Display over other apps, so the block screen can appear on top
- Accessibility, needed for website and keyword blocking
- Battery optimization turned off for AppBlock, so Android doesn’t stop it in the background
- Autostart on phones that have it
AppBlock has a Troubleshooting screen in its Profile/Help area that shows which permissions are missing. On some Samsung phones Accessibility is greyed out until you allow “restricted settings” for AppBlock from its App info page.
- Update AppBlock and your browser. Open Google Play and install any pending updates for both. Bugs around blank pages are often fixed in newer releases.
- Try a different browser. Website blocking only works in supported browsers, and behaviour can differ between them. If the issue only happens in one browser, clearing that browser’s cache usually helps.
- Restart your phone. A reboot refreshes AppBlock’s system permissions and background services. AppBlock’s own support pages recommend it.
- Back up, reinstall, restart. If nothing else works, back up your AppBlock settings if your account supports it, uninstall the app, restart the phone, then install it again from Google Play and grant the permissions when asked. If you use Strict Mode with uninstall protection, you’ll need to end that first.
If the blank page is still there after all of that, contact MobileSoft through the help center at appblock.app and tell them your phone model and Android version.
If You Don’t Use AppBlock

That address can only come from an app with the package name cz.mobilesoft.appblock. If you’re sure you never installed it:
- Go to Settings > Apps and look for AppBlock. A family member, school, or employer may have set it up, especially on a shared or managed device.
- Check whether it was installed from Google Play. Copies from random APK sites can be modified, and a fake “AppBlock” is something to remove.
- Run a scan with Google Play Protect (in the Play Store menu).
- If the app is there and you don’t need it, uninstall it. The blank.html page will go with it.
While you’re cleaning things up, it’s also worth knowing how cookies and site settings work in Chrome, since a browser misconfiguration can make pages look broken too.
For Developers: FileProvider and WebView Notes
If you hit this URI in your own app’s logs or WebView, here’s the short version:
- AppBlock exposes the file through Android’s FileProvider. It generates
content://URIs and grants temporary read access instead of sharing raw file paths. - Your app can only read it if a read permission was granted for that URI. Otherwise you’ll get a
SecurityExceptionor an empty response, which is expected. - A WebView loading
content://URLs needssetAllowContentAccess(true). Don’t try to bypass the provider. Treat the page as a signal that the user’s blocker intercepted the navigation. - Don’t hardcode or cache this URI. It belongs to another app and can change or disappear at any time.
Frequently Asked Questions
Is content://cz.mobilesoft.appblock.fileprovider/cache/blank.html a virus?
No. It’s an empty placeholder page from AppBlock, a legitimate app blocker by MobileSoft. It sits in the app’s private cache and does nothing on its own. The only real concern is if AppBlock came from an untrusted APK site.
Why does blank.html open in Chrome?
AppBlock redirects blocked sites to this empty page before showing its block screen. If Chrome reopens an old tab, or if AppBlock can’t draw over other apps, the blank page can stay on screen instead of the block message.
How do I stop AppBlock showing a blank page?
Check that the site isn’t in an active schedule, close the stuck tab, clear AppBlock’s cache, and confirm Usage access, Display over other apps, Accessibility, and the battery optimization exception are all set. Restart the phone if needed.
Can I delete the blank.html file?
You can’t reach it directly because it’s in AppBlock’s private storage. Clearing AppBlock’s cache from Settings removes it, but the app may recreate it the next time it blocks something. That’s normal and harmless.
Does clearing cache delete my AppBlock settings?
No. Clear cache only removes temporary files. Your schedules and block lists stay. “Clear storage” or “Clear data” is different: it resets the app, so avoid that unless you plan to set it up again.
What if I don’t have AppBlock installed?
Look in Settings > Apps, because someone else may have installed it or it may be part of a managed device. If you find a copy you didn’t install from Google Play, uninstall it and run a Play Protect scan.
Seeing an unfamiliar system name like com.android.cts.priv.ctsshim in your app list? See what com.android.cts.priv.ctsshim is and whether it is safe.
Summary
The blank.html address is AppBlock doing its job, or getting slightly stuck while doing it. Check your rules, clear the cache, and re-grant the permissions, and the problem is usually gone in a few minutes. If you’re also tidying up other apps, our guide to clearing Facebook cache on Android and iPhone uses the same Settings steps, and if AppBlock is part of a school device plan, see our take on allowing phones in school with limits.
