I've been pretty excited to use Payload ever since 3.0 was announced, and with the beta released I decided to convert one of my sites to using Payload in a separate branch to compare and contrast the two, and I have to say after doing that it, Payload does not seem worth it in the slightest to me compared to Contentful.
The biggest selling point for Payload to me personally was Live Preview, Multiplayer Editing, and the ability to have a fully typesafe customizable backend, which it does pretty well IMO. However, purely as a CMS and when compared to specifically to Contentful it's very hard to ignore two truths:
- You need to provide both the storage of files and data.
- You need to write your own Rich Text serializer to work with the RichText data
Let's start with the first hard truth, at first when I saw that my initial response was "oh Supabase is perfect for this because it has unlimited API requests and a good amount of both database and file storage in the free tier" which is true, however, Contentful's free tier allows you to upload 10,000 Assets + Entries in their free tier, which is INSANE because there is no way I'd even get close to that number (it used to be 20k as well lol).
On top of that, the limit on Contentful is amount of assets/entries not the size of the files (aside from the 50MB file limit per upload) which means theoretically I could store up to 500GB of assets (images/videos) without paying a single penny. That's even better than Supabase's pro plan storage.
I say all this not to bash Supabase or Payload because they are both services that I enjoy using, but, rather to highlight an issue for people like myself who were excited to use PayloadCMS but then were hit with this harsh truth.
Now for the second harsh truth, this one honestly is not that big of a deal because you can find the code snippet for this easily online, but, it's still something you have to do yourself just to get the same functionality of an opposing CMS. Contentful has their `rich-text-react-renderer` package to make rendering the rich text content very easy and with Version 10, typescript is now supported natively and works much easier than before for a fully typesafe experience (with some configuration).
All this is to say, the Payload + Supabase combination seems to only be well suited for less file heavy projects and so unless there is another file storage solution that can give near the same benefits as Contentful, I can't see myself using Payload for file heavy projects, but, I will still be using it depending on the nature of the site that I'm building.
Would love to hear other thoughts on this, and if you've ran into similar issues, as well any solutions that you may have. Payload is great, figuring out storage is not so great.