OptimageOptimage
Image Optimization

MLB's September Roster Expansion Is a Content Problem Most Teams Still Handle Badly

MLB active rosters expand from 26 to 28 on September 1, and the stretch run to the September 27 finish line means dozens of new faces need photos in the system fast. Here's the actual workflow for keeping a September call-up's image library from lagging a week behind his debut.

Optimage
Optimage
·Updated September 2026
5 min read
TL;DR

September 1 roster expansion brings new names onto MLB rosters right as the postseason race tightens, and team media and content staff have to get first-day photography into circulation immediately. The bottleneck usually isn't the photography — it's the pipeline between a raw game-day RAW file and a compressed, correctly named, web-ready image the second the player's name hits a lineup card.

Key Takeaways
  • MLB active rosters expand from 26 to a maximum of 28 players on September 1 — not the old 40-man free-for-all, but still a real influx of new names
  • A call-up's first MLB photo often has to go live same-day: box score graphics, social posts, and team site bios all need an image before the game ends
  • Minor-league headshots and MLB-quality game photography are shot on completely different equipment and pipelines, which is why the mismatch is so visible
  • The 27-day sprint to the regular-season finish line means beat photographers and team media staff are shooting and filing faster than any other stretch of the year
  • A standing compression and naming convention for new-player photo intake saves the scramble every single September

A baseball stadium press box with camera equipment set up during a night game

MLB active rosters expanded from 26 to a maximum of 28 players on September 1, and with the regular season running through September 27, every team still alive in a playoff race is now working with a deeper bench and a compressed calendar. The 40-man free-for-all that used to define "September call-ups" hasn't existed since the 2020 rule change, but the basic content problem it created never went away: a player who was shooting minor-league headshots in Triple-A on August 31 can be starting a Major League game on September 2, and every team's digital and social operation needs a usable photo of him before that game is over.

Why the Turnaround Is Genuinely Tight

A call-up doesn't arrive with a photo library. He arrives with whatever the minor-league affiliate shot months ago — often lower-resolution, inconsistently lit, and formatted for a completely different set of use cases than a Major League team's website, app, and social graphics require. The team's own photographers get maybe one game, sometimes less, to capture something usable before the content calendar needs a bio photo, a debut graphic, and social-ready crops. During a playoff push, that same photographer is also covering the actual game, which means the turnaround from shutter click to published image is measured in innings, not days.

Two Photo Pipelines That Don't Talk to Each Other

Minor-league team photography and Major League team photography are, functionally, two different businesses. Affiliate headshots are frequently shot in batches at spring training or early in a minor-league season, on whatever equipment and lighting setup the affiliate has, and saved at whatever resolution someone thought was "good enough" at the time. Major League digital teams work from professional game photography — high-resolution RAW or high-quality JPEG files from credentialed photographers, run through a color-correction and cropping pass before anything gets published.

When a call-up's name hits a lineup card, whoever manages the roster page, the app, and the social accounts is stuck choosing between publishing a visibly lower-quality affiliate photo immediately or waiting on a same-day MLB photo that might not exist until the first pitch. Most teams split the difference badly: the affiliate photo goes up first and never gets swapped, so a player can spend weeks represented by an image that looks nothing like his current team's visual standard.

What Actually Fixes the Turnaround

  1. Pre-stage a standard crop and export preset for headshots and action shots so a new file doesn't need a fresh set of format decisions every time — same aspect ratio, same file naming convention, same compression target, applied automatically.
  2. Compress at intake, not at publish. A RAW or high-resolution JPEG straight off a photographer's card is not what belongs on a roster page. Running every new player photo through a batch compression step the moment it's filed means the web team is never the bottleneck.
  3. Keep a placeholder-to-final swap process ready. If an affiliate photo has to go up first, flag it for replacement the moment MLB-quality photography exists, rather than treating "good enough for launch day" as permanent.
  4. Standardize file naming across affiliates and the parent club — a mismatched naming convention between Triple-A and the majors is a small thing that turns into hours of manual sorting during the exact week nobody has spare hours.

The Stretch Run Makes This Worse, Not Better

A quiet September for a rebuilding team is a manageable content calendar. A tight playoff race is the opposite: more games matter, more storylines need same-day graphics, and a bullpen or bench reshuffled by a September call-up needs its visual presentation updated in real time, not on next week's schedule. Teams that treat photo intake as an afterthought during the regular season find out in the last week of September exactly how much that decision costs them — scrambling to get a September addition's image current right as he potentially becomes a postseason roster storyline.

Get the Pipeline Ready Before the Next Wave

The fix isn't more photographers — it's a faster path from file to publish. Compress new player photography in batches instead of one at a time, resize to the exact dimensions your roster page, app, and social templates actually need, and convert to WebP so a stretch-run content calendar doesn't get slowed down by oversized files on top of everything else.

Related reading:

Continue reading

Try Optimage — it's free

Compress, convert, and optimize images in seconds. No sign-up, no limits.

Start Optimizing Free
← Back to The Optimage Journal