How to delete indexedDB?

Question

I'm working in a project which involves using IndexedDB. As I'm begining to know this technology, I need to be able to delete an indexedDB by hand so I can start over.

I found the way to do it in Firefox, but I can't find the way for Google Chrome.

I tried deleting the content of this folder (I'm using Mac):

{home}/Library/Application Support/Google/Chrome/Default/IndexedDB

but it seems Chrome stil have the DB anywhere so I can't start over.

Answer 1

In theory, all you need to do to delete an IndexedDB in Chrome is:

1. In Chrome, go to Options > Under the Hood > Content Settings > All cookies and Site Data > find the domain where you created the IndexedDB
2. Hit either the "X" or click "Indexed Database" > Remove

In Windows, the file is located here:

%USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default\IndexedDB

On Mac, do the following:

1. In Chrome, go to "Settings" (or "Preferences" under the Chrome menu)
2. Click "show advanced settings" (at the bottom of the page)
3. Go to "Privacy" > "Content Settings" > "All cookies and Site Data" > find the domain where you created the IndexedDB
4. Hit either the "X" or click "Indexed Database" > Remove

On Mac, the folder is located here:

/Users/[USERNAME]/Library/Application Support/Google/Chrome/Default/IndexedDB/

On Linux, the folder is located at:

/home/[USERNAME]/.config/google-chrome/Default/IndexedDB/

Answer 2

I've had success running the following in Chrome:

indexedDB.deleteDatabase('DB NAME')

Answer 3

Alternarive is to do it in the developers console, using this command:

indexedDB.deleteDatabase("databaseName")

Answer 4

In Chrome webkit you can use webkitGetDatabaseNames which returns all database names

With this code, you can delete all local indexedDB:

window.indexedDB.webkitGetDatabaseNames().onsuccess = function(sender,args)
{
    var r = sender.target.result;
    for(var i in r)
        indexedDB.deleteDatabase(r[i]);
}; 

Answer 5

To remove all Chrome IndexedDB databases run the following in OSX terminal emulator.

rm -rf ${HOME}/Library/Application\ Support/Google/Chrome/Default/IndexedDB/*

Now restart your browser and that's it.

---

Because I need to purge IndexedDB databases very often, I have set up an alias in my ~./bash_profile.

alias purge-idb="rm -rf ${HOME}/Library/Application\ Support/Google/Chrome/Default/IndexedDB/*"

Answer 6

To delete an IndexedDB from the OS X version of Chrome:

1) In Preferences, show Advanced Settings then click the "Content Settings" button under the "Privacy" section.

2) In the "Content Settings" popup, click the "All Cookies and Site Data" button under the "Cookies" section.

3) In the "Cookies and site data" popup, use the "Search Cookies" textbox to look up the domain that is the source of the IndexedDB.

4) Click on the domain entry in the list.

5) Click on the "indexed database" tag listed under the domain.

6) Click on the "Remove" button in the drop down detail for the indexed database.

Answer 7

In Debian GNU/Linux directory

/home/[username]/.config/google-chrome/Default/IndexedDB/chrome-xxx.indexeddb.leveldb/

contains regular files (for example):

000003.log, CURRENT, LOCK, LOG, MANIFEST-000002

Answer 8

It's not possible to delete IndexedDB database (as opposed to stores and indexes) programmatically.

As for manual workarounds, this post details the location of the database on Windows systems for Firefox and Chrome.

Update: Thanks to developer Joshua Bell, Chrome implements an off-spec (but insanely useful) deleteDatabase method on the window.indexedDB object. Here's the crbug that landed this patch. Moreover, in newer versions of IE, you can delete databases via a settings panel.

Answer 9

Chrome Developer tools now have an option to delete all databases for an app, under "Application/Clear Storage".

Answer 10

Chrome -> Inspector Window -> Application -> look at left hand menu -> Storage -> IndexedDB

Answer 11

write this code segment in console

window.indexedDB.deleteDatabase(<your db name>)

Answer 12

Alternatively, use your web application in a new incognito window, and close it when you're done: database deleted.

Answer 13

In chrome OSX- /Users/user/Library/Application Support/Google/Chrome/Default/IndexedDB Firefox OSX - Users/user/Library/Application Support/Firefox/Profiles/4zaemxcn.default/indexedDB

You just need to make visible the library folder. All of the files are stored in folders(which are called as domain name) and the files use hash, but you can figure out the name of database from it. You can delete data from IDB because it is a client side database and all of the data is stored locally.

Answer 14

In windows, you can manually delete the whole IndexedDB databases by locating the IndexedDB directory for the browser and deleting it

For Chrome:

C:\Users\user-name\AppData\Local\Google\Chrome\User Data\Profile 1\IndexedDB

You can delete every folder which clears up the indexedDB. You can start over now.

Answer 15

This is maybe overkill for your specific question, but I kept ending up here in my struggle to delete my idb.

My solution in the end was based on mozilla's documentation, but required that I first close the database.

For me, in Javascript, the code looked like this:

my_db_instance.close(function(e){console.log(e)});
var DBDeleteRequest = indexedDB.deleteDatabase("my_db_name");

// When i had the base open, the closure was blocked, so i left this here
DBDeleteRequest.onblocked = function(event) {
  console.log("Blocked");
};

DBDeleteRequest.onerror = function(event) {
    console.log("Error deleting database.");
  console.log(event);
};

DBDeleteRequest.onsuccess = function(event) {
  console.log("Database deleted successfully");
};

Answer 16

I needed to get rid of an indexedDB in Chrome. So I search for this lousy thing called "email assistant" on my computer using MasterSeeker. Found the thing in a bunch folders that were indexedDB in Chrome. It seemed too easy that I just delete those files. I looked up how, and ended up here. I went to chrome settings with my Windows 10 PC. I just gave it a shot at trying to clear the browsing data. Presto - all those files disappeared from indexedDB, including that dreaded "email assistant" crapola. Now when I look in the indexedDB folder all I see that has reappeared is https_mail.google.com_0.indexeddb.leveldb - which looks like a safe non-irritating thing.