Zilfu publishes to Instagram, TikTok, LinkedIn, Threads, Pinterest, Facebook, and X from one workspace. This page takes you from a fresh account to a scheduled post, and flags the things that catch people out on the way.
Signing up creates your first space — a workspace with its own connected accounts, posts, slots, and timezone. Agencies usually run one per client, businesses one per brand. Add more from the space switcher in the top-left. Your team is not one of the things a space keeps to itself: members belong to your organization and reach every space in it.
Connect an account
Open Settings → Channels and pick a network. You'll authorise Zilfu on the platform's own login screen and land back in the app. Zilfu never sees your password; the token that comes back is stored encrypted.
Two prerequisites catch people out:
- Instagram and Facebook need a Professional (Business or Creator) account, connected through the Facebook Page that manages it. A personal profile can't be connected.
- Every account you connect uses a slot on your plan, including a second or third profile on the same network. Free allows 2, counted across every space you own.
Zilfu starts working from the moment you connect. It does not import posts you published before that, so analytics and history begin at connection time.
If a token expires — platforms rotate them on their own schedule — the account shows a Reconnect badge and stops publishing until you clear it. Reconnecting is free and doesn't consume another slot.
Disconnected accounts still count
Disconnecting an account leaves the row in place, and it keeps occupying a plan slot. Delete it from Accounts to get the room back. This is deliberate: it means reconnecting later restores the account rather than rebuilding it.
Write your first post
Hit Create Post, pick one or more accounts, write the caption, and attach media.
Selecting several accounts creates one post per account from a single composition. They're grouped when created, but each publishes independently from then on — an Instagram rejection doesn't hold back the LinkedIn version. Where networks disagree on caption length, the composer counts your caption against each selected account's limit as you type. Media rules differ too, and some are only checked at the moment a post publishes — so a post can schedule cleanly and still be refused by the network.
Your media library keeps originals. Upload a photo at whatever size you exported it and that is what gets stored, at the dimensions shown — nothing is re-encoded or downscaled on the way in, so it is still the full file the next time you reach for it.
Images too large for a particular network are resized on the way out, per network. A photo too heavy for X goes to X as a resized copy and to Pinterest at full size, and your original is untouched either way. The same goes for dimensions: LinkedIn caps an image at 36.2 megapixels, so a photo over that goes to LinkedIn scaled down and everywhere else at the size you uploaded. Format is handled the same way: Instagram accepts JPEG and nothing else, and Threads accepts JPEG and PNG, so a file either won't take is converted for that network alone — a PNG going to both stays a PNG on Threads. Transparency doesn't survive that conversion, since JPEG has no alpha channel and it lands on white. So you don't have to think about each network's limits. Images can be JPEG, PNG or WebP, up to 32 MB and 60 megapixels — that ceiling is what we can process to do the resizing with, not what the networks accept, and it's above what any phone camera shoots.
Video is different: we can't re-encode it, so its limits are the strictest of what the networks themselves take — MP4 or MOV, up to 512 MB, 1920px wide and 140 seconds. A network that accepts more is judged by its own number: a YouTube post takes up to 180 seconds, the length of a Short. A post going to several networks at once has to clear the strictest of them, since it's one file going to all of them. Height is unlimited, so ordinary vertical video is fine; it's width the networks cap. A video outside those is flagged in the composer before you can schedule it — as long as we can read its width and length out of the file. A few exports don't state them in the header we read, and those schedule cleanly and get refused by the network instead.
Uploading a file into your media library is not where these limits are enforced — one that breaks them still lands there, so you can see what you picked. Only two things are turned away outright: a format that isn't on the lists above, and a file over the ceiling on what we can take at all, 100 MB for an image and 2 GB for a video. If it can't be published, the composer says so the moment you attach it — or at save, for a file we couldn't measure until then — and the post can't be scheduled until you swap it out.
Then choose when it goes out: Publish now, Schedule for a specific date and time, Slot to take the next free time from the space's recurring schedule, or Save as draft to keep it out of the queue. Scheduled times use the space's timezone rather than your browser's, so a distributed team all reads the same calendar. Set it under Space settings → Timezone.
Give it a rhythm
Picking a timestamp for every post gets old. A slot is a recurring weekly publishing time that belongs to the space — Tuesday 09:00, Thursday 17:30 — defined once under Settings → Posting times. A new space starts with none, so add the times you actually want. Choosing Slot in the composer offers the next free times from that schedule.
Slots are a schedule, not a content source: an empty slot simply passes. Nothing is invented to fill it, and nothing is recycled.
Every post carries one of six statuses — Draft, Awaiting approval, Scheduled, Processing, Published, or Error — and the tabs on Posts are grouped by them. A post that errors keeps the network's own message, so you can tell a caption that was too long from an account that needs reconnecting, and it can be retried once you've fixed the cause.
Invite your team
Members are unlimited and free on every plan. Invite from Team, in the account menu.
The team belongs to your organization, not to one space: a member you invite reaches every workspace you own, including ones you create later. There is one invitation and one role per person, rather than one per workspace.
Choose the role that matches what each person does:
| Role | Grants |
|---|---|
| Creator | Create and edit posts; publishing always goes through approval |
| Publisher | Create, edit, publish, retry, and delete posts without approval |
| Approver | Review and approve posts without creating or publishing them |
| Manager | Manage content, approvals, connected social accounts, and team members |
| Owner | Full control of the organization and every workspace |
New invitations default to Creator. Roles are fixed so responsibilities stay consistent and easy to review. Every member holds at least one role — there is no role-less, read-only member.
Publish posts is the permission that changes the workflow. Without it, a member's posts are never sent straight to a network: they're created as drafts and submitted for approval automatically, carrying whatever schedule the author picked. The space owner and anyone with Approve posts can then approve it or send it back. Approving keeps the schedule the author picked; sending it back clears it, so whoever resubmits chooses a new time.
Plan limits
| Plan | Accounts | Posts |
|---|---|---|
| Free | 2 | 15 per month |
| Pro | 10 | Unlimited |
| Business | 100 | Unlimited |
| Scale | 300 | Unlimited |
Both limits belong to the workspace owner and are pooled across every space they own — not per space, and not per member. What counts as a post:
- One per account. Sending the same composition to three accounts spends three.
- Drafts are free. A post awaiting approval is not — submitting it is the moment it's charged, and sending it back to draft refunds it.
- Thread replies are free; only the root post they hang off counts.
- The month resets at the start of the UTC month, whatever your space's timezone is.
Members, spaces, and API access are unlimited on every plan, including Free.
Automate it
Everything the dashboard does is available over the REST API and an MCP server, on every plan. Your API key is waiting under Settings → REST APIs — copy it, then either:
- Drive it from a script or a Zapier/n8n workflow — see the API quickstart.
- Point an AI assistant at
https://zilfu.app/mcp/social-mediaand schedule in plain language — see What is MCP?.
The same token authenticates both.