GIF is a palette format, capped at 256 colors, so anything that looks like a smooth gradient in the original is usually dithering, a pattern of dots faking colors the format can't actually store. When you convert to AVIF, the tool encodes whatever pixels the GIF frame actually contains, dithering included. AVIF can't restore detail that the GIF palette already threw away, it just compresses what's there more efficiently.
The frame you extract is the frame you're stuck with
This tool always pulls the first frame of the GIF, since that's what shows up in most contexts before animation starts. If the moment you actually want sits three or ten frames in, an AVIF pulled from frame one won't show it. In that case, trim or re-export the GIF around the frame you need first, then run it through the converter, or extract a JPEG with GIF to JPG to check the frame before committing to AVIF.
AVIF isn't safe everywhere yet
Browsers handle AVIF well now, but plenty of email clients, older messaging apps, and some link preview generators still don't render it correctly, showing a broken image icon instead. If the still frame is going into an email campaign, a chat app, or anywhere outside a modern website, keep a WebP or JPEG version on hand as a fallback rather than relying on AVIF alone.
Encoding AVIF takes noticeably longer than JPEG or WebP because the underlying AV1 codec does far more work per pixel to hit its smaller file sizes. For a single GIF this is barely noticeable, but a batch of twenty or thirty files will take a real stretch of time to finish, all of it running locally in your browser tab rather than on a server.