Ecosystem & Emerging Terms

AI Slop (and Workslop)

Also called: slop · workslop · AI-generated slop

AI slop is low-quality, unreviewed AI-generated content produced in volume; workslop is the same thing at work: AI output that looks like finished work but leaves the recipient to fix or redo it.

AI slop is a pejorative term for generic, error-prone, or padded AI-generated text, images, and video that is published without meaningful human review, often in bulk. The name echoes "spam": it is not the technology that is slop, but the low-effort, high-volume use of it.

Workslop applies the idea inside organizations: a polished-looking report, deck, or summary that is shallow or wrong, so the colleague who receives it has to spend time interpreting, checking, or redoing it. Related informal coinages such as deckslop and promptslop follow the same pattern. The labels became common in 2025-2026 commentary about AI adoption.

For agent builders it is a useful design lens: an agent that produces output faster than it can be verified creates slop, whatever the model quality.

Example

A manager forwards an AI-drafted project update that is confident and well-formatted but misstates two milestones and omits the blocker. The team lead spends an hour reconstructing the real status. The document existed, but the work was transferred, not done.

How it differs

Slop vs. hallucination: a hallucination is a specific failure, a confident false statement by a model. Slop is a broader quality-and-effort problem: content can be slop without a single false claim if it is generic, padded, or unhelpful.

Common misconceptions

Often assumed: AI slop means any AI-generated content.
Actually: The term targets low-effort, unreviewed output. AI-assisted content that a person has checked and shaped is not what the label refers to.

FAQ

What is AI slop?
Low-quality, generic or error-prone AI-generated content published in volume without meaningful human review.
What is workslop?
AI-generated work product that looks polished but is shallow or wrong, so the person receiving it must spend time fixing or redoing it.
How can teams avoid producing AI slop?
Keep a person accountable for reviewing output before it ships, give the model specific context, and measure whether the result actually saves the recipient time.

Last checked: 2026-09-20

Related terms