Instagram plans that fit weekly publishing

The real question behind Instagram plans

Many creators start by asking which Instagram plan to buy. The better question is how to structure a weekly publishing rhythm that reuses assets across Reels, carousels, and Stories without daily logins. FlixySocial answers that by letting you queue content once and push to Instagram plus six other networks from a single self-hosted instance.

Start with the posting cadence that matches your output

A workable Instagram plan begins with three distinct cadences. Short-form video goes out three times per week. Static carousels land on Tuesdays and Fridays. Story sequences run daily for 24-hour windows. These numbers come from the same workflow we use at our own desk: record once on Monday, trim in 90-second segments, then export three vertical files at 1080x1920.

Video batch day

Record three talking-head clips back to back. Each clip runs 45-60 seconds. Drop them into a shared folder named 2026-07-14-reels. FlixySocial watches that folder and pulls the files into the compose queue automatically.

Carousel batch day

Create five slides per carousel. Use 1080x1080 square files saved as PNG-24 with 72 dpi. Name them slide-01.png through slide-05.png so the scheduler can order them correctly.

Connect once, publish everywhere

After you finish recording, open Compose and attach the files. Add captions once. The tool then distributes the same asset to Instagram, TikTok, and Threads using each platform's native aspect ratios. You never paste the same text five times.

Platform Settings stores the Instagram Business token and the Facebook Page ID in one place. Revoking access later happens from the same screen, which satisfies the data deletion flow described on the Data Deletion page.

Approval handoff for teams

Solo operators skip this step. Small teams route drafts through the dashboard. An editor leaves comments on the caption field. The creator receives a notification inside the Dashboard and can approve or request changes before the post time arrives. The entire thread stays inside the self-hosted database.

Asset storage and naming rules

Store raw files on a local NAS volume mounted at /media/instagram. Keep final exports in /media/instagram/exports/2026-07. Six concrete examples of file names that parse correctly:

• reel-2026-07-14-01.mp4 (45 s, 1080x1920, H.264)
• carousel-2026-07-16-01.png (1080x1080)
• story-2026-07-17-01.jpg (1080x1920)
• caption-2026-07-14.txt (UTF-8)
• thumbnail-2026-07-14.jpg (1200x630)
• analytics-2026-07-20.csv (export from native insights)

Platform-specific repurposing matrix

Not every asset fits every network. The table below shows the mapping we apply inside FlixySocial before scheduling.

Source format	Instagram	TikTok	LinkedIn	X
60 s Reel	Reel	Video	Document	Thread
5-slide carousel	Carousel	n/a	Carousel	Thread
24 h Story	Story	n/a	n/a	n/a

The mapping lives in the compose template so one click applies the correct crop and caption length for each destination.

Analytics review loop

Every Sunday we pull the previous week's numbers from Dashboard. The report lists reach, saves, and profile visits for each post. We keep only two metrics per format: average saves per Reel and average profile visits per carousel. If saves drop below 2 % of reach, we adjust hook length in the next batch.

Tradeoffs nobody lists in the marketing copy

Self-hosting removes the monthly per-user fee charged by cloud schedulers. It also requires you to maintain the server and renew the SSL certificate every 90 days. If your team publishes fewer than eight posts per week, the maintenance overhead can exceed the saved subscription cost. FlixySocial does not hide this limit.

The one decision rule

Build the plan around the single weekly recording block first. Everything else—captions, crops, approvals—slots into that fixed time. Once the block is protected on the calendar, open Compose and let the scheduler handle distribution.

Privacy and Terms pages detail how tokens and media stay on your infrastructure. No external service ever receives the raw files.

Weekly template you can copy

Monday 09:00 – Record three Reels Tuesday 10:00 – Build two carousels Wednesday 14:00 – Review and approve drafts in Dashboard Thursday 09:00 – Queue Stories for the next three days Friday 11:00 – Export analytics CSV and log two changes for next week

That sequence produces nine distinct Instagram touches from five hours of focused work. The same files feed the other six networks without extra steps.

Setting up automated folder imports

FlixySocial monitors designated directories for new media files and pulls them into the compose queue without manual uploads. Create a top-level watch folder at /media/instagram/incoming and subfolders for each content type. The system parses file names that follow the pattern type-yyyy-mm-dd-nn.extension to assign correct post formats and dates. For example, a file named reel-2026-07-21-02.mp4 lands as a Reel scheduled for the following Monday.

Configure the watcher interval in folder watcher settings to scan every five minutes during work hours. Exclude temporary files by adding patterns such as *.tmp and ._. This prevents partial exports from triggering erroneous posts. When the watcher detects a match it logs the import event in the activity feed and attaches the file to a draft entry ready for caption addition.

Test the setup with a single file first. Drop one 45-second clip into the reel subfolder and verify that it appears in the queue within the expected scan window. If the file fails to import check the extension whitelist and confirm the NAS volume remains mounted. The logs page records every scan attempt so you can trace permission or path errors quickly.

Managing platform rate limits

Each network enforces its own posting cadence and daily caps. Instagram allows roughly 25 feed posts and 100 Stories per day from a single account while TikTok limits video uploads to around 20. FlixySocial surfaces these constraints in the rate limit dashboard so you can see remaining quota before queuing additional items.

Build a simple buffer rule into weekly planning: reserve 30 percent headroom below the stated limits. If your plan calls for three Reels and two carousels schedule them across separate days rather than stacking on Tuesday. The dashboard highlights approaching limits with color cues and blocks new posts once the threshold is reached until the rolling window resets.

Cross-posting the same asset to multiple networks counts against each platform separately. A single 60-second clip sent to Instagram, TikTok and Threads therefore consumes one slot on each service. Review the per-platform counters before bulk scheduling to avoid mid-week blocks.

Building reusable caption templates

Caption templates store variable placeholders that expand at publish time. Create a library entry called Reel-Hook-Open that contains the string "[day] tip: " followed by the body text. When you attach a file dated 2026-07-22 the system replaces [day] with Tuesday and produces the final caption without retyping.

Store templates in the template library and tag them by format and network. A single template can hold multiple platform versions so the Instagram version keeps hashtags while the LinkedIn version drops them. Export the library as JSON for backup and import it on a second self-hosted instance when expanding to additional team members.

Test each template with a sample post before committing it to the weekly rhythm. Verify that line breaks and emoji placement survive the expansion step. Update the template whenever platform character limits change rather than editing individual drafts.

Backup and recovery checklist

Self-hosted instances require a documented backup routine to protect tokens, media paths and the post queue. Run the following steps every Friday after the analytics review:

• Export the full database dump to an encrypted external drive
• Copy the /media/instagram/exports folder to the same drive
• Verify that the most recent five posts can be restored in a test environment
• Record the backup checksum in a text file dated for that week

Store the external drive offsite or in a separate physical location. If the main server experiences disk failure restore the database first then remount the media volume so file paths remain valid. Test the restore process quarterly to confirm the procedure works under time pressure.

The checklist also covers token revocation. After a restore, visit Platform Settings and regenerate any Instagram Business tokens that show as expired. This keeps the connection live without exposing raw credentials in the backup archive.