Classroom is a hallway, not a screen
Classroom does very little rendering of its own. It routes files to students and collects them back. So the question is never whether Classroom supports animation. It is what the GIF is sitting inside when a student finally opens it.
- An image on a Stream announcement. The fastest way to make one instruction unmissable, and the fastest way to make a class page exhausting. Once a week, for the thing that genuinely matters.
- A file attached from Drive. Drive's own image preview has generally played animation, and a student who downloads it instead gets whatever their device's image viewer does, which is usually fine and occasionally a still.
- Inserted into a Doc or a Slide. Both animate in the browser, Slides during a presentation, and both carry the file's weight inside the document from then on. The Docs guide covers that side properly.
- Printed, or exported to PDF. One frame, always the first one. If any part of your class works on paper, frame one has to make sense alone.
The Chromebook already records the screen, and already makes GIFs
Worth saying plainly, because the tool is sitting right there under Shift + Ctrl + Show windows. ChromeOS's built-in capture records the screen or a selected region and writes a .webm into Downloads, and recent versions offer a GIF option that writes a .gif directly. If that gets you what you need for tomorrow's lesson, use it and go home.
What it does not give you is a trim after the fact, a crop to a ratio, a frame rate, a color count, a caption, or a way to join two takes. A raw region recording is also usually several times heavier than the same seconds encoded with a reduced palette, which matters when thirty devices open it at once. Drag the .webm into the editor and every one of those dials is there.
Build for the slowest device in the room
Nobody opens your file on your laptop. It opens on a four-year-old Chromebook, on shared school wifi, thirty at once, in the first two minutes of a period. That is the machine the file has to please.
- Width 480 to 720 px. Big enough to read a menu, small enough that the whole class gets it before the bell.
- 10 to 12 fps. Pointer-and-menu footage does not need more, and every extra frame is a full picture in GIF.
- 64 colors. A flat interface has maybe a dozen real colors in it. Spending 256 on that is pure weight.
- Under 1 MB, under 10 seconds. If it will not fit, it is two lessons, not one loop.
Then crop hard. A full desktop shrunk to a phone-sized preview is unreadable, and the menu you are actually pointing at is 300 px wide and deserves the entire frame. Getting a small file out of video runs through the levers in the order that pays.
The footage usually has a child in it
This decides which tool a teacher should be using, and it does not get said often enough. Classroom footage is student work with a name on it, a gradebook column, a recorded meeting with faces, a shared screen with a roster visible in the corner. The standard free-converter bargain is that you hand that file to a company you have not heard of, under terms written for stock video, on a district device.
There is no bargain to weigh here because there is no upload. The page loads once and then runs on the machine in front of you, offline if the wifi in the portable classroom drops again. No account, no email address, no file sitting in a processing queue. If a name does sneak into frame, a solid shape overlay covers it before the export, and that redaction happens on your side of the wire too.
What a silent loop cannot teach
A GIF has no sound and no controls. For a procedure that is a feature: the student watches the same four seconds until it clicks, with no scrubber to get lost in and no play button to fail to press. For anything with reasoning in it, it is a wall. No narration, no pausing for a student who reads slowly, no captions for a student who needs them, no way to go back one step.
So the division is clean. A loop for what it looks like when it works: the drag, the toolbar, the formula being entered correctly. A narrated video or a numbered handout for anything that needs explaining. Captions in the editor can label a step, and up to three of them can be timed across one loop, which helps a great deal, but a label is not an explanation. The tutorial guide is about pacing footage that has to teach.
One more honest limit: a GIF has no accessible text layer. Whatever is in the animation is invisible to a screen reader, so the alt text and the instruction next to it are carrying more weight than they would in a document. Write them as if the image did not load, because for some students it effectively did not.