<p>It's not that it’s not recommended, it’s not supported at all. <a href="https://craftcms.com/docs/5.x/requirements.html#minimum-system-specs" rel="nofollow noreferrer">https://craftcms.com/docs/5.x/requirements.html#minimum-system-specs</a></p>
<p>MySQL 5.7 doesn’t have many of the features that Craft 5 requires to operate successfully (specifically around native JSON column data types and support, but many other areas).</p>
<p>Would not recommend.</p>

CC BY-SA 4.0
2024-04-17T03:41:22.127Z
Ah,sorry, i misspoke, not recommended, but unsupported.  
The cp screen appeared to work fine, so the question was asked with the aim of checking what specific problems it could lead to.  

> native JSON column data types  
These are the parts I understand.
shin_develop
CC BY-SA 4.0
2024-04-17T03:18:16.943Z
2024-04-17T03:18:16.943Z
Brad Bell
<p>The recommended MySQL version for Craft 5 is 8.0.17+, but it appears to work with 5.7.<br />
How does this version (5.7) affect site construction and functionality?<br />
We understand that as long as it is not recommended, its introduction should be avoided...</p>
<p><a href="https://i.sstatic.net/K5VT9.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/K5VT9.png" alt="enter image description here" /></a></p>

<craft5>
Behaviour of MySQL 5.7 on Craft 5
# Behaviour of MySQL 5.7 on Craft 5

(Asked by: username_0 on 2024-04-17)

The recommended MySQL version for Craft 5 is 8.0.17+, but it appears to work with 5.7.  
How does this version (5.7) affect site construction and functionality?  
We understand that as long as it is not recommended, its introduction should be avoided...

[![enter image description here](https://i.sstatic.net/K5VT9.png)](https://i.sstatic.net/K5VT9.png)

**Tags:** craft5


---

## 1 answers

### Answer by username_1 on 2024-04-17. Score: 1 | Accepted answer

It's not that it’s not recommended, it’s not supported at all. <https://craftcms.com/docs/5.x/requirements.html#minimum-system-specs>

MySQL 5.7 doesn’t have many of the features that Craft 5 requires to operate successfully (specifically around native JSON column data types and support, but many other areas).

Would not recommend.

> **Comments:**
> **username_0**: Ah,sorry, i misspoke, not recommended, but unsupported.   The cp screen appeared to work fine, so the question was asked with the aim of checking what specific problems it could lead to.    > native JSON column data types   These are the parts I understand.  

---

