Surprise: Chiefs cut Jeremy Maclin, save $10 million against the cap

How’s this for a June surprise: the Kansas City Chiefs are cutting Jeremy Maclin. It’s official.

This is certainly a surprise but talk of cutting Maclin wasn’t unheard of this offseason. He was due a lot of money - $12.4 million against the cap - and had a down year last year so we talked about this. Still, I’m surprised. Take our poll below and tell us how you feel in the comments.

Maclin seemed to know the pressure was on last week when he met with the media. “I got something to prove,” Maclin said. “I struggled a little bit last year with injuries and everything else. I’m healthy and I’m looking forward to getting this thing back on the road.”

The Chiefs now save $10 million in cap space, according to Over The Cap, and will carry $2.4 million in dead money. (We’ll need to confirm those cap numbers because the cap is notoriously confusing)

MNChiefsfan decided months ago when we talked about this that it was an awful idea. Unless Chris Conley takes a big step forward I’m not sure how I feel about this either. The Chiefs offense needs to get more dynamic, not less. And that $10 million in cap savings is great ... if they’re going to use it someplace. There is the chance the Chiefs thought Maclin lost a step which if so that makes more sense. They did make this move after seeing him in six practices the past two weeks.

Maclin had a down year last year with just 536 yards receiving after he was injured and went through some personal problems. His first year with the Chiefs was solid though with over 1,000 yards receiving.

Photo by Andy Lyons/Getty Images

Cutting Jeremy Maclin is an awful idea, writes MNChiefsfan.

The biggest factor here - besides Maclin’s dip in play last year and his cap hit - is the emergence of Tyreek Hill. His play last year at receiver made a move like this possible. He had 593 receiving yards last year but his ceiling is sky high entering year two. I think it’s safe to say Tyreek will be an important part of the offense this year.

I’m not sure if it being post-June 1 came into play here but that’s a notable date in salary cap accounting.