It was as I thought. Did a test now with a server component and a client both with the same data object. If you included the client component, the entire object is saved in the page .rsc/html file if you send it as a prop. But not if it is a server component. I assume because it will only be html and css and no js when it is a server component, but when it is a client, it must have all the data that is sent to become interactive. Feels like this should be somewhere in the next.js docs. It's not something you really think about when you go from the page router as you fetch everything at the top and send all the data down through the react tree

Came across the same issue. This really should be highlighted in the docs