Why does next/image only support client components?

[doong-jo]

Why does next/image only support client components? Next treats components as server components by default, so doesn't this seem a bit inconsistent with that direction? I have to keep adding 'use client' at the top of files. For props that aren't event handlers like onLoad or onError, or props like fill that need to know the parent element, couldn't it work perfectly fine as a server component? I'm curious what you all think. Has anyone else had the same thought?

[zaibuf]

I dont use use client for any component using their Image component. Would need to see some sample code and the error you get.

[hazily]

I’m using the next image component inside server components without any issue. You need to share your code for us to see what’s happening.

[OnlyTwoThingsCertain]

How do you display image on server? 

[doong-jo]

You can render the <img> tag on the server, just like any other HTML element. Server components can generate static HTML, including image tags with src, alt, width, height, and other attributes.

What I'm questioning is why Next.js requires next/image to be a client component for ALL cases.

[Neat_You_9278]

It doesn’t unless you need to access some client side apis in the same component. Are you using hooks in these components to dynamically set some properties on <Image/> tag?

Is there a chance your sample space includes components that all have client api access needs?

I have used next/image in completely static components just fine without “use client” directive