<p>You would only need to add a prefix if you were planning on multiple installs of Craft on the same DB, most likely you are not so you can just leave it blank.</p>
<p>You don't need seperate DBs for a multi-site install.</p>
<p>If you did install with different DB prefixes for each, each Craft install would need to be licensed seperately; again probably not what you want.</p>

CC BY-SA 4.0
2024-03-12T22:59:07.060Z
Thank you for the clarification.
flip
CC BY-SA 4.0
2024-03-20T17:54:10.793Z
100% agree with Seth. Worth mentioning if you're on a recent version of Craft, there is a `php craft db/drop-table-prefix` CLI command, which goes the other direction. i.e. remove table prefixes if you're using them.
Brad Bell
CC BY-SA 4.0
2024-03-12T14:13:56.110Z
2024-03-12T14:13:56.110Z
Seth Warburton
<p>I finally have been able to install Craft CMS. During installation I left the table prefix field empty. I assume that for each site separate tables are created. Therefore, it would be more user-friendly to use a different table prefix for each site. How can I add a table prefix after the installation?</p>
<p>Is it sufficient to rename each table manually and then add the prefix to the .env file?</p>

<database><mysql><table>
Use table prefix after installation
# Use table prefix after installation

(Asked by: username_0 on 2024-03-12)

I finally have been able to install Craft CMS. During installation I left the table prefix field empty. I assume that for each site separate tables are created. Therefore, it would be more user-friendly to use a different table prefix for each site. How can I add a table prefix after the installation?

Is it sufficient to rename each table manually and then add the prefix to the .env file?

**Tags:** database, mysql, table

---

## 1 answers

### Answer by username_1 on 2024-03-12. Score: 1 | Accepted answer

You would only need to add a prefix if you were planning on multiple installs of Craft on the same DB, most likely you are not so you can just leave it blank.

You don't need seperate DBs for a multi-site install.

If you did install with different DB prefixes for each, each Craft install would need to be licensed seperately; again probably not what you want.

> **Comments:**
> **username_0**: Thank you for the clarification.  
> **username_2**: 100% agree with Seth. Worth mentioning if you're on a recent version of Craft, there is a `php craft db/drop-table-prefix` CLI command, which goes the other direction. i.e. remove table prefixes if you're using them.  

---

