Answers.Body: <p>On first blush they are very similar. I think the Craft Plugin Store description of Neo sums it up nicely:</p>
  <blockquote>
  <p>Neo is a field type that builds upon the concept of the Matrix field type with a number of very useful features.</p>
  </blockquote>
  <p>Neo solves one of the biggest issues people have with Matrix and adds Oreo features: no blocks within blocks. Sometimes you need this feature, other times you can get away without it.</p>
  <h1>Matrix</h1>
  <ul>
  <li>Built-into Craft CMS / first party support</li>
  <li>Blocks use their &quot;own&quot; fields</li>
  <li>No inception (child / nested / hierarchical) support (Matrix block within another)</li>
  </ul>
  <h1>Neo</h1>
  <ul>
  <li>3rd party plugin / extra license cost / another dependency in the stack</li>
  <li>Uses existing Craft CMS fields</li>
  <li>Can clone/copy/paste blocks</li>
  <li>Blocks can be nested inside each other (inception style)</li>
  <li>Blocks can be organized in groups / tabs / drop-downs for better authoring experience</li>
  </ul>
  <h1>Summary</h1>
  <p>Neo is like Craft's own Matrix field but a different and arguably more flexible take on it. However, it comes with all the risk/reward of using 3rd party plugins.</p>
  <p>As an aside, after Craft 3 shipped, it took awhile for Neo to come over to Craft 3. I think this was partly to blame because Neo was offered as a free plugin for Craft 2 and with Craft 3's extensive changes, it's not surprising that the Craft 3 version of Neo is a paid version—3rd party developers have to eat too!</p>
  <h1>Alternatives</h1>
  <p>As an alternative to Neo, there's another plugin called Spoon which supplies some of Neo's organizational features and supercharges the built-in Matrix. That's a little bit more &quot;future-proof&quot;—so even if you decide to remove the plugin, your content will stay in place.</p>
  <p>Using Super Table, you can get some of the inception level magic that Neo offers.</p>
  <p>FWIW the plugin store allows you to try all of these plugins out on a dev instance and see for yourself which methodology you prefer.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-11T08:14:39.123Z
Answers.Text: amazing, thanks for this!
Answers.UserDisplayName: Paloma Martinez
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-10T22:46:59.053Z
Answers.LastActivityDate: 2020-11-10T22:46:59.053Z
Answers.UserDisplayName: RitterKnight
Body: <p>Im a bit new in Craft CMS
  But so far to me, seems like both allow the user to create multiple blocks of content</p>
  
Tags: <matrix><field><fieldtypes><content><blocks>
Title: What's the difference between Neo and Matrix fields?
ThreadText: # What's the difference between Neo and Matrix fields?
  
  (Asked by: username_0 on 2020-11-10)
  
  Im a bit new in Craft CMS
  But so far to me, seems like both allow the user to create multiple blocks of content
  
  **Tags:** matrix, field, fieldtypes, content, blocks
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-11-10. Score: 3 | Accepted answer
  
  On first blush they are very similar. I think the Craft Plugin Store description of Neo sums it up nicely:
  
  > Neo is a field type that builds upon the concept of the Matrix field type with a number of very useful features.
  
  Neo solves one of the biggest issues people have with Matrix and adds Oreo features: no blocks within blocks. Sometimes you need this feature, other times you can get away without it.
  
  # Matrix
  
  * Built-into Craft CMS / first party support
  * Blocks use their "own" fields
  * No inception (child / nested / hierarchical) support (Matrix block within another)
  
  # Neo
  
  * 3rd party plugin / extra license cost / another dependency in the stack
  * Uses existing Craft CMS fields
  * Can clone/copy/paste blocks
  * Blocks can be nested inside each other (inception style)
  * Blocks can be organized in groups / tabs / drop-downs for better authoring experience
  
  # Summary
  
  Neo is like Craft's own Matrix field but a different and arguably more flexible take on it. However, it comes with all the risk/reward of using 3rd party plugins.
  
  As an aside, after Craft 3 shipped, it took awhile for Neo to come over to Craft 3. I think this was partly to blame because Neo was offered as a free plugin for Craft 2 and with Craft 3's extensive changes, it's not surprising that the Craft 3 version of Neo is a paid version—3rd party developers have to eat too!
  
  # Alternatives
  
  As an alternative to Neo, there's another plugin called Spoon which supplies some of Neo's organizational features and supercharges the built-in Matrix. That's a little bit more "future-proof"—so even if you decide to remove the plugin, your content will stay in place.
  
  Using Super Table, you can get some of the inception level magic that Neo offers.
  
  FWIW the plugin store allows you to try all of these plugins out on a dev instance and see for yourself which methodology you prefer.
  
  > **Comments:**
  > **username_0**: amazing, thanks for this!  
  
  ---
  
  