Feature cluster

Media upload API for social scheduling

Media cannot live in local browser storage forever. That road ends in sadness, support tickets, and someone saying the word quota.

Coming next. Native account strategy. Agent-first scheduling.

Best for

Who this page is for.

Image posts
Video campaigns
Cross-channel launch assets
Capabilities

What Hey Tasky is built to handle.

Object storage

Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.

Direct uploads planned

Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.

Preview thumbnails

Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.

Per-network validation

Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.

Media references in posts

Part of the Hey Tasky direction for agent-assisted social scheduling, native account publishing, and reviewable workflows.

Limits

Check these before scheduling.

Confirm your connected accounts and the workflow you want to use.

Production media pipeline is being built
Video processing is later
Some network limits vary by account
FAQ

Questions people ask before choosing a scheduler.

Why does media need its own page?

Media upload is a core search and product concept for schedulers. It also explains a real production gap cleanly.

Will Hey Tasky validate media before posting?

Yes, that is part of the planned publisher layer.