# Adminer PHP memory settings

**URL:** <https://community.localwp.com/t/adminer-php-memory-settings/27237>\
**Category:** Feature requests\
**Tags:** database, phpini, adminer\
**Created:** [August 17, 2021, 2:23pm UTC](https://community.localwp.com/t/adminer-php-memory-settings/27237 "2021-08-17T14:23:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tonytiger](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@tonytiger](https://community.localwp.com/u/tonytiger)\
**Post date:** [August 17, 2021, 2:23pm UTC](https://community.localwp.com/t/adminer-php-memory-settings/27237/1 "2021-08-17T14:23:24Z")

</div>

Since the upload cap is so low Adminer can’t be used to import medium to large databases. This would be simple enough to solve by editing phpini for local to allow larger file uploads.  
Since the lack of open source database handlers we do only get a paid option with TablePlus.  
The primary reason for using local is the simplicity, speed and GRAPHICAL interface. Having to resort to command line for database is… not just right.  
Would love to be able to set the upload limits as any other web server so Adminer can be used as it should.

---

<div class="post-metadata">

**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\
**Post date:** [August 17, 2021, 3:46pm UTC](https://community.localwp.com/t/adminer-php-memory-settings/27237/2 "2021-08-17T15:46:40Z")

</div>

Thanks for creating this feature request!

Out of curiosity, how large are you thinking when you say “medium to large” database?

Hundreds of megabytes? Gigabytes?

---

<div class="post-metadata">

**Author:** ![tonytiger](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@tonytiger](https://community.localwp.com/u/tonytiger)\
**Post date:** [August 18, 2021, 6:56am UTC](https://community.localwp.com/t/adminer-php-memory-settings/27237/3 "2021-08-18T06:56:00Z")

</div>

Thanks for replying. I am currently using databases in the ranges of 50 MB to 1.5 GB (in some cases 5GB), most of them under 1 GB however. Would be enough to set limits up when needed.

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [May 9, 2024, 3:26pm UTC](https://community.localwp.com/t/adminer-php-memory-settings/27237/4 "2024-05-09T15:26:58Z")

</div>

An update here that we’ve created a new feature request for this issue after some recent users have run into the same problem. I’m going to close this one out and we’ll rely on the new one for tracking. Feel free to comment, upvote or follow along here:

> [@Allow Users to Raise the Memory Upload Limit for Adminer](https://community.localwp.com/t/allow-users-to-raise-the-memory-upload-limit-for-adminer/42787):
>
> Currently, the Memory Limit for Adminer is hard-coded at 256 MB which means if you’re importing a large database you might get an error like these: A note that this is not related to the PHP Memory value set in php.ini which you can edit to a larger value. Steps for this are included at the bottom of our [Troubleshooting Performance Issues help article here](https://localwp.com/help-docs/troubleshooting/troubleshooting-performance-issues-in-local/). The workaround for the Adminer error is to manually import the database file as mentioned in our [Manually Importing a Local Site guide](https://localwp.com/help-docs/getting-started/how-to-import-a-wordpress-site-into-local/#Manually-Import-a-Local-site).…

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [May 9, 2024, 3:27pm UTC](https://community.localwp.com/t/adminer-php-memory-settings/27237/5 "2024-05-09T15:27:03Z")

</div>


