Where Does Via Browser Store Data?
Via Browser is a tiny WebView shell on Android under package mark.via.gp, with bookmarks exportable and sync through user-chosen WebDAV.
Last updated
Via is minimalism as a browser. It wraps the system WebView rather than shipping Chromium, so the familiar User Data profile tree simply does not exist. Bookmarks leave through HTML export or WebDAV sync to folders you choose.
The package name carries its own history. Current builds use mark.via.gp after a rename from the shorter original, and stale references still float around. Quote the new ID everywhere. Downloads default to system Download with user overrides.
Where Via Browser stores this, by platform
/data/data/mark.via.gp
Private app root for the current gp-suffixed package. Holds prefs with WebView data under system conventions. No Chromium profile and no documented inner filenames, so only the root is quoted.
/storage/emulated/0/Download
Default download target on shared storage, changeable in settings. Bookmark sync goes to user-chosen WebDAV folders rather than any fixed local path.
Frequently asked questions
How do I back up Via bookmarks?
Export bookmarks to HTML from inside the app or point WebDAV sync at a folder you choose. There is no fixed local bookmark file to copy, since sync targets vary by user choice. The private app root needs root to browse directly.
Where is the Via Chromium profile?
It uses the system WebView instead. Via bundles no Chromium and keeps no User Data Default profile, which is why it stays tiny. Clearing Android System WebView data affects rendering while Via's own prefs sit in its private root.
Why do two Via package names exist?
The rename happened upstream from mark.via to mark.via.gp. Old guides and blocklists reference the retired ID. Current installs answer to the gp-suffixed package, so use that in every path and rule.
Notice an outdated path? Let us know.