<p>There's nothing in Craft limiting the amount of Matrix Blocks and fields you can add, it's purely environmental.</p>

<p>The most common values to increase are <code>max_input_vars</code>, <code>post_max_size</code> and <code>memory_limit</code>, so you'd need to bump one or more of those to higher values to be able to add more.</p>

<p>If you're running things like <a href="https://suhosin.org/stories/index.html" rel="nofollow noreferrer">Suhosin</a> or <a href="https://www.modsecurity.org/" rel="nofollow noreferrer">mod_security</a>, they provide their own additional settings that sit on top of php.ini settings that you might need to adjust as well.</p>

CC BY-SA 3.0
2017-07-24T08:08:21.693Z
It actually was environmental as you mentioned. Switched to a new local server but somehow it ignored the settings made in the .htaccess file. Had to change it server sided. Thanks for pointing me that way!
Justin Dekkers
CC BY-SA 3.0
2017-10-25T20:30:19.780Z
I ran into this same issue today. I added 5 fields and it dropped 3 existing fields. Luckily, I was in a development environment. Is there a way to mitigate losing existing fields or to warn the user of possibly losing fields on the roadmap?
kotyy
CC BY-SA 3.0
2017-10-25T23:57:54.833Z
@kotyy that would be pretty difficult to detect (and be reliable) from PHP.
Brad Bell
CC BY-SA 3.0
2017-10-26T14:57:31.640Z
@BradBell When saving a Matrix, would serializing the existing fields, appending the newly-created fields reduce the likelihood of dropping an existing field? I noticed in the logs that the POST values were being trimmed from the end. I'd rather lose a new field over an existing field. My two cents.
kotyy
CC BY-SA 3.0
2017-07-21T17:25:16.477Z
2017-07-21T17:25:16.477Z
Brad Bell
<p>I have a really big / flexible Matrix field for one of my websites. It works great and is easy to handle.</p>

<p>The problem is that I need to add another block containing some fields.
I already extenended the <code>php_value max_input_vars</code> to <code>9000</code>. This worked for a while but I guess I need even more now. </p>

<p>The Matrix field contains <strong>25 blocks</strong> with an average of 5 fields per block as of now but, I need to build another one. If I add another block right now the block will stay but If I add a field to the block and save it, it won't appear when reloading the matrix field.</p>

<p>I know it's alot of blocks inside a matrix field but, it actually is really easy to work with.</p>

<p>Now the question is. <strong>Is there another way to extend the limit or maybe a better solution?</strong>  </p>

<templating><matrix><database><limit>
Can't add anymore fields / blocks to Matrix Field
# Can't add anymore fields / blocks to Matrix Field

(Asked by: username_0 on 2017-07-21)

I have a really big / flexible Matrix field for one of my websites. It works great and is easy to handle.

The problem is that I need to add another block containing some fields.
I already extenended the `php_value max_input_vars` to `9000`. This worked for a while but I guess I need even more now.

The Matrix field contains **25 blocks** with an average of 5 fields per block as of now but, I need to build another one. If I add another block right now the block will stay but If I add a field to the block and save it, it won't appear when reloading the matrix field.

I know it's alot of blocks inside a matrix field but, it actually is really easy to work with.

Now the question is. **Is there another way to extend the limit or maybe a better solution?**

**Tags:** templating, matrix, database, limit

---

## 1 answers

### Answer by username_1 on 2017-07-21. Score: 3 | Accepted answer

There's nothing in Craft limiting the amount of Matrix Blocks and fields you can add, it's purely environmental.

The most common values to increase are `max_input_vars`, `post_max_size` and `memory_limit`, so you'd need to bump one or more of those to higher values to be able to add more.

If you're running things like [Suhosin](https://suhosin.org/stories/index.html) or [mod\_security](https://www.modsecurity.org/), they provide their own additional settings that sit on top of php.ini settings that you might need to adjust as well.

> **Comments:**
> **username_0**: It actually was environmental as you mentioned. Switched to a new local server but somehow it ignored the settings made in the .htaccess file. Had to change it server sided. Thanks for pointing me that way!  
> **username_2**: I ran into this same issue today. I added 5 fields and it dropped 3 existing fields. Luckily, I was in a development environment. Is there a way to mitigate losing existing fields or to warn the user of possibly losing fields on the roadmap?  
> **username_1**: @kotyy that would be pretty difficult to detect (and be reliable) from PHP.  
> **username_2**: @BradBell When saving a Matrix, would serializing the existing fields, appending the newly-created fields reduce the likelihood of dropping an existing field? I noticed in the logs that the POST values were being trimmed from the end. I'd rather lose a new field over an existing field. My two cents.  

---

