NEXTPION - Media Sending Enhancers
Speed up image and video delivery in ChatPion by using Meta’s Attachment Upload API instead of slow media URLs, ensuring faster and more reliable message sending.
This guide provides step-by-step instructions for setting up and using the NEXTPION - Media Sending Enhancers plugin, which accelerates image and video delivery by optimizing media uploads before sending.
NEXTPION - Media Sending Enhancers
The NEXTPION - Media Sending Enhancers plugin solves slow media delivery in ChatPion. Instead of sending media URLs directly (which forces Facebook to download the file each time), the plugin uploads media to Meta’s Attachment Upload API and uses the returned attachment ID for faster delivery.
Key Features
✅ Attachment Upload Optimization
Uploads media to Meta before sending so Facebook doesn’t need to re-download it.
✅ Smart Media Caching
Stores attachment IDs in the database and reuses them for future sends.
✅ Automatic Expiry Handling
Media is refreshed before expiration to avoid delivery failures.
✅ Multi-Platform Support
Works seamlessly with both Facebook Messenger and Instagram Direct messages for consistent performance across all Meta platforms.
✅ Faster Message Delivery
Second and subsequent sends of the same media are dramatically faster.
Speed Comparison Videos
Image Sending Speed (Optimized vs Original)
This test shows two Messenger conversations side-by-side. The left side uses NEXTPION - Media Sending Enhancers, while the right side shows ChatPion’s original media URL delivery. Each side has a timer that stops when the image is fully sent. The test is triggered by a keyword and sends two images in a single flow to compare real delivery speed. The images used are 178 KB and 366 KB.
Result: Optimized 06:42 vs Original 08:93 (≈ 2.51s faster, ~28% improvement).
Video Sending Speed (Optimized vs Original)
This test uses the same side-by-side setup and is triggered by a keyword, but triggers a video send. The timer pauses when the video is fully delivered on each side, making the speed difference clear. The video used is 2.63 MB and 27 seconds long.
Result: Optimized 06:15 vs Original 13:64 (≈ 7.49s faster, ~55% improvement).
These benchmarks were recorded on a 2 vCPU / 8 GB RAM server. Message delivery speed varies by server specs, hosting provider, and network conditions. The results above are for reference and may differ in your environment.
Installation Process
After purchasing the plugin from the NEXTPION marketplace, you can install it using the NEXTPION Plugin Manager.
Access Plugin Manager
Open your NEXTPION Plugin Manager from the main dashboard.
Install the Plugin
Locate the NEXTPION - Media Sending Enhancers plugin in your purchased plugins list and click the "Install" button. You’ll be prompted to enter the plugin’s license key.
Enable the Plugin
Once installation is complete, click the "Enable" button next to the plugin’s name. You’ll be redirected to the Add-on Manager within ChatPion. Locate the NEXTPION - Media Sending Enhancers plugin and enable it to activate its functionality.
Administrator Configuration
Accessing Plugin Settings
To configure the plugin, click the settings icon on the plugin card in the NEXTPION Plugin Manager.
Cron Job Settings
The plugin requires a server-side cron job to refresh expired media attachments.
Copy the Cron Job Command
Use the copy button in the settings page to copy the cron job command. Replace the demo domain with your own domain when deploying.
curl https://example.com/nextpion_media_sending_enhancers/update_expired_attachments >/dev/null 2>&1Cron hint: 0 */6 * * * (run every 6 hours).
The cron job URL should use your own domain in production. The example above uses a demo domain for reference.
Batch Limit
The Batch Limit controls how many expired attachments are refreshed per cron run:
- Default: 200
- Maximum: 1000
Attachments expire after 90 days. To prevent downtime, the system proactively treats attachments as expired after 85 days, leaving a 5-day safety window.
If no cron job is configured, the plugin still works. When a message is sent, expired attachments are automatically re-uploaded on demand.
Plugin Status
This plugin provides Function Status only. If any errors are shown, click the Repair button to resolve them.
After ChatPion updates, the Plugin Status may show errors. Use the Repair button to restore functionality.
Media Attachment Stats
The settings page also shows media statistics:
- Total Attachments
- Expired Attachments
- Images Count
- Videos Count
How It Works
- The plugin checks each media URL before sending.
- It uploads the media to Meta’s Attachment Upload API.
- The attachment ID is saved and reused for subsequent sends.
- Messages are sent using attachment IDs instead of raw URLs.
The first time you send a new image or video, the speed will be similar to before optimization since the attachment needs to be uploaded first. From the second send onward, delivery is significantly faster.
Troubleshooting
Frequently Asked Questions
Best Practices
- Configure the Cron Job: Run it every 6 hours to keep attachments fresh.
- Keep Batch Limit Reasonable: Start with 200–500 and increase only if needed.
- Test Twice: When validating speed improvements, send the same media twice to observe the optimized delivery path.
Performance Benchmark Notes
The speed comparisons above are based on a consistent benchmark setup and are meant to show the relative improvement between optimized and original delivery. Actual delivery speed varies with server performance, network conditions, media size, and concurrent traffic, so results can differ from one environment to another.
Hosting Recommendations
If you still experience slow delivery after enabling this plugin, the cause is usually server performance or network latency. Switching to a better VPS provider can significantly improve HTTP request speed.
We recommend Hostinger® for cost‑effective, reliable performance (20% discount via referral). Click a card to open the plan in a new tab:
For most ChatPion users, KVM 2 is enough, but KVM 4 is the best value. Choose KVM 8 only for high‑volume traffic.
Once optimized, media messages send much faster and more reliably compared to URL-based delivery.