Upload rejection on a TeamSpeak server usually comes down to numbers, not content. Avatars that come straight off a phone are thousands of pixels wide and megabytes heavy. Our TeamSpeak avatar resizer exists to enforce one dimension rule and report the rest, and knowing exactly which rules it enforces saves you a failed upload.
The single dimension rule, 320 pixels
The tool passes one constraint to the compression library, a maximum of 320 for width or height. The library, browser-image-compression version 2.0.2, scales the image down until its longer side fits within that maximum.
Two consequences follow directly from that rule.
1. Smaller images pass through unchanged. The library scales down to fit a maximum, so a 200 by 200 input is never blown up to 320. If your source is tiny, the tool cannot add detail.
2. Aspect ratio survives. A 1600 by 900 landscape photo becomes 320 by 180, letterboxed by whatever the client draws around it. The tool never stretches or crops to force a square.
The TeamSpeak client displays avatars in small frames, so the missing crop matters less than you might fear. What matters is that your subject sits inside the center of the frame, because edges of wide images shrink hardest.
What happens to each input format
The accept filter takes JPG, PNG, and GIF. The output rule is short.
- JPG input stays JPG.
- PNG input stays PNG.
- GIF input converts to PNG, which flattens animation into a single static frame.
The GIF rule exists in the code as an explicit type mapping, and it matches how TeamSpeak treats avatars anyway. An animated upload would animate nowhere.
One naming quirk survives from the same code path. The download filename is always ts3-avatar followed by a timestamp and a .png extension, even when the processed file is actually JPG from a JPG source. The pixels are fine, but the extension lies about the container. Rename the file to .jpg after download if a tool complains, or feed the resizer PNG sources to keep the name honest.
Byte size is reported, never enforced
The options object sets three keys, the dimension cap, the web worker flag, and the output type. No byte target is passed. The tool does not chase a kilobyte limit, and no such limit is guaranteed because server administrators configure their own.
What the tool does instead is measure. After processing, the result panel shows the final file size next to the original, computed on a 1024 base and labeled B, KB, or MB. That number is your acceptance test.
Apply this rule. If your server rejects large avatars, read the final size on screen before you download. If it exceeds what your server allows, compress the source further upstream or simplify the image, because running it through the resizer again will not change the result for an image already under 320 pixels.
Resize an avatar in five steps
1. Open the TeamSpeak avatar resizer and select your image with the file picker. The original appears as a grayed preview on the right.
2. Confirm the subject is centered, since no crop control exists to fix composition later.
3. Press the resize button and wait for the processing state to clear. Work happens in a web worker inside your browser, and the image never leaves your machine.
4. Read the final file size in the result panel against your server limit.
5. Press Download and rename the file if the extension does not match your input type.
Honest downsides
The tool enforces one rule and leaves the rest to you. There is no crop UI, so off center subjects stay off center. There is no quality dial, because no byte target exists to trade quality against. There is no batch mode for a whole clan roster at once. Processing errors are logged to the browser console only, so a failed run looks like a button that did nothing.
The privacy claim is structural rather than promised. All processing runs in the browser through a web worker, and the code contains no upload call. You can verify this by watching the network tab while you resize.
Checklist before you upload
- [ ] The longer side of the output is no more than 320 pixels.
- [ ] The final size shown on screen fits your server limit.
- [ ] GIF sources were checked for lost animation, which is expected behavior.
- [ ] The filename extension matches the actual file type after the rename.
- [ ] The avatar reads clearly at the small channel list size, since the large preview flatters every image.
The 320 cap covers the dimension side of the equation, and the size readout covers the byte side. Run your current avatar through the [TeamSpeak avatar resizer](/en/teamspeak-avatar) and note how many kilobytes the resize alone saved you. If your server still rejects the file, tell us the final size it reported and we will narrow down which limit you hit.
