2

Since Chrome 61 it appears that any item added to the local stage no longer gets created as a phsyical file within the local profile.

Previously running the command

localStorage.setItem('key', 'value')

Would create a SQLite file corresponding to the website in... 

%localappdata%\google\chrome\user data\default\local storage\

But this now no longer seems to be the case, new items are simply no longer created in this location.

Anyone have any ideas if this behaviour has been deprecated?

Or alternatively any idea how to add to the local storage in chrome so that a physical file gets created?

Nisarg Shah
  • 13,626
  • 5
  • 36
  • 53
James Amos
  • 306
  • 1
  • 10
  • I doubt that was ever officially supported. If it is not part of the spec, browsers can change that behavior anytime they want, without informing the community/users. – Nisarg Shah Sep 20 '17 at 14:48
  • Google can change this at any time, without any advance notice, completely at their own discretion. –  Sep 20 '17 at 14:54
  • Using Chrome `100.0.4896.127`, local storage data is still being logged in in the mentioned folder. I was able to recover some data after I navigated from `http` to `https` with no way of coming back other than rolling back the NGINX setup. Thanks! – GuiRitter Apr 25 '22 at 15:03

1 Answers1

4

Looks like it's now stored in a LevelDB database. See https://crbug.com/586194, Chrome Service Model, and LocalStorage using Chrome Service Model if you want to learn more.

Josh Lee
  • 161,055
  • 37
  • 262
  • 269