<p>Just like <strong>khalwat</strong> said ^^  If you're using MAMP like me, it is in your MAMP Application file MAMP/bin/php/PHP_version_your_using/conf/<strong>php.ini</strong></p>

<p>It was a combination of upping both <strong>memory_limit</strong> &amp; <strong>post_max_size</strong> to 128M</p>

<p>This did the trick. 
Hope this saves somebody's time.</p>

CC BY-SA 3.0
2017-08-07T01:09:32.627Z
2017-08-07T01:09:32.627Z
mateostabio
<p>This is because of a combination of settings in your <code>php.ini</code> file:  <code>max_input_vars</code> &amp; <code>post_max_size</code>, not any limitation in Craft CMS. c.f.:</p>

<p><a href="https://craftcms.stackexchange.com/questions/2765/matrix-field-input-error-from-within-the-control-panel">Matrix field input error from within the control panel</a></p>

CC BY-SA 3.0
2015-11-23T17:36:54.047Z
This solved my problem on my local development environment as well as on Heroku. For anyone interested, you can modify your php.ini settings by placing a file named .user.ini in the public directory.
chrisyour
CC BY-SA 3.0
2015-11-24T22:02:18.587Z
I regularly have this problem when working locally but never encounter it on any remote servers. Probably because my WAMP default settings are too low.
Clive Portman
CC BY-SA 4.0
2020-10-31T17:44:52.163Z
I noticed I hit a limit on extending a Matrix field’s scope which correlated with `craft_fields` having 255 rows: where 255 was OK but more than 255 was not. 255 seems like a highly significant number, but my `max_input_vars` was set to 1000, so it’s not clear how 255 relates to 1000. Increasing both `max_input_vars` and `post_max_size` worked. Not sure which one made the difference.
Jonathan Schofield
CC BY-SA 3.0
2015-11-22T16:53:10.960Z
2015-11-22T16:53:10.960Z
2017-04-13T12:51:00.253Z
andrew.welch
<p>I have a matrix with around 75 fields in it. They are spread over multiple "Block Types". When I create a new field and save the matrix, the new fields aren't being saved. </p>

<p>Even worse, when I create a new block type with new fields and then drag it up in the order, when I save, Craft is deleting (trimming) the last fields in the matrix - even though they are old (already created) fields.</p>

<p>Does Craft have a limit on the number of fields in a single matrix?</p>

<p>Thanks for your help!</p>

<matrix>
Is there a maximum number of fields in a single matrix?
# Is there a maximum number of fields in a single matrix?

(Asked by: username_0 on 2015-11-22)

I have a matrix with around 75 fields in it. They are spread over multiple "Block Types". When I create a new field and save the matrix, the new fields aren't being saved.

Even worse, when I create a new block type with new fields and then drag it up in the order, when I save, Craft is deleting (trimming) the last fields in the matrix - even though they are old (already created) fields.

Does Craft have a limit on the number of fields in a single matrix?

Thanks for your help!

**Tags:** matrix

---

## 2 answers

### Answer by username_2 on 2015-11-22. Score: 12 | Accepted answer

This is because of a combination of settings in your `php.ini` file: `max_input_vars` & `post_max_size`, not any limitation in Craft CMS. c.f.:

[Matrix field input error from within the control panel](https://craftcms.stackexchange.com/questions/2765/matrix-field-input-error-from-within-the-control-panel)

> **Comments:**
> **username_0**: This solved my problem on my local development environment as well as on Heroku. For anyone interested, you can modify your php.ini settings by placing a file named .user.ini in the public directory.  
> **username_3**: I regularly have this problem when working locally but never encounter it on any remote servers. Probably because my WAMP default settings are too low.  
> **username_4**: I noticed I hit a limit on extending a Matrix field’s scope which correlated with `craft_fields` having 255 rows: where 255 was OK but more than 255 was not. 255 seems like a highly significant number, but my `max_input_vars` was set to 1000, so it’s not clear how 255 relates to 1000. Increasing both `max_input_vars` and `post_max_size` worked. Not sure which one made the difference.  

---

### Answer by username_1 on 2017-08-07. Score: 2

Just like **khalwat** said ^^ If you're using MAMP like me, it is in your MAMP Application file MAMP/bin/php/PHP\_version\_your\_using/conf/**php.ini**

It was a combination of upping both **memory\_limit** & **post\_max\_size** to 128M

This did the trick.
Hope this saves somebody's time.


---

