Support
TP-Link VIGI Camera FTP Snapshot Resolution Guide
TP-Link VIGI Support
Summary
Use this guide when FTP event snapshots from a VIGI camera look lower resolution than the camera's normal live view or recorded footage.
Applies to
- TP-Link VIGI cameras with FTP or event snapshot functions
- Sites using FTP for image uploads or alerting
- Users comparing FTP images with NVR or app footage
Difficulty and time
Difficulty: Moderate
Estimated time: 20 to 40 minutes
What you will need
- Access to the camera or NVR interface
- One known FTP event example
- Ability to compare the FTP file with the live image or recording
- Camera model and firmware version
What this guide covers
- Why FTP snapshots can look different from the main image
- What to check in stream and event settings
- How to test the FTP result properly
- When to use NVR or SD card recording instead
A lot of people compare an FTP image with the main live stream and assume the camera is "downgrading" the image for no reason. In reality, the snapshot function may be tied to a different path, depending on the model and firmware.
That means the job here is to prove what the camera is actually generating, not to assume the FTP server is compressing it or the NVR is doing something behind the scenes.
Before you start
Test one clean event from start to finish before changing multiple settings.
- Keep one example FTP file that shows the issue.
- Take a screenshot of the live view at the same time if possible.
- Check whether the camera also records to NVR or SD card for comparison.
- Write down the model and firmware before you start changing anything.
FTP snapshots are often an alert path, not the main evidence path
If the site needs full-resolution evidence for incidents, do not assume the FTP snapshot workflow is the best place to get it.
In many real jobs, the cleaner answer is to use the recorder or SD card for evidence and keep FTP as a quick-notification path.
What usually causes this
- The snapshot path is using a different profile from the main stream.
- The event engine is generating a lower-resolution image than the live-view image being compared.
- The customer is comparing an FTP still image with full recorded video.
- The camera firmware or model has limits around how FTP snapshots are produced.
- The site really needs recorded evidence rather than an FTP still workflow.
Step 1: Confirm exactly what is lower resolution
Start by comparing like with like. Is the complaint that the FTP image is smaller than the main stream, smaller than the NVR export, or smaller than a manual snapshot taken from the interface?
- Record the pixel dimensions of one FTP image if possible.
- Compare it with the camera's configured recording or main-stream resolution.
- Check whether the NVR or SD card footage still looks correct.
- Do not rely only on "it looks blurrier" without comparing the actual file type and size.
Step 2: Check stream, event and snapshot settings
Different VIGI models and firmware versions can handle event image generation differently. The key question is whether the FTP upload follows the same profile the customer thinks it does.
- Open the camera event and snapshot settings and look for any dedicated snapshot options.
- Check whether the event upload is tied to a specific stream or event profile.
- Review whether the site is using main-stream recording but expecting the FTP image to match it exactly.
- If there is a relevant firmware note or limitation for that model, record it before promising a fix.
Step 3: Run one known event and compare all outputs
The clean way to troubleshoot this is to stage one known event and compare every output created by the system.
- Trigger one controlled event in front of the camera.
- Save the FTP image generated from that event.
- Check the same moment in the local recording.
- If the interface supports a manual snapshot, compare that as well.
Step 4: Choose the right path for the real business need
If the customer needs a quick image email or a light notification workflow, FTP may still be fine. If the customer needs strong evidence, plate detail or better audit quality, the NVR or SD card path is usually the smarter answer.
- Use FTP snapshots for quick visual confirmation where appropriate.
- Use NVR or SD recording as the primary evidence path.
- If the site wants scheduled or scripted image capture from a stream, that is a different workflow from the normal FTP event snapshot path.
- Do not claim unsupported behaviour unless it has been proven on that exact model and firmware.
Remote gate site wanted clearer incident images
Situation: A customer was happy with VIGI live view but unhappy that the FTP image uploaded on each trigger looked softer than the recorded footage.
Solution used: The site kept FTP for event notifications but switched its evidence process to NVR export and SD backup for incidents.
Why this was chosen: The FTP image was doing its alert job, but it was not the strongest evidence path for that site.
Installation notes: This is a common example of matching the output path to the business need rather than expecting every function to do the same job.
Common mistakes
- Assuming the FTP snapshot always uses the main stream.
- Blaming the FTP server before proving what the camera is actually sending.
- Comparing still snapshots with full recorded video as if they are identical workflows.
- Updating firmware first without capturing the current behaviour clearly.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| FTP file is smaller than expected | Snapshot profile, event path, file dimensions | Compare the FTP file directly against local recording and manual snapshots. |
| Recording looks fine but FTP still looks soft | Different output workflows | Treat FTP as an alert path and use recording export for evidence. |
| No one knows which settings drive FTP images | Camera model, firmware and event menu | Document the model and current menus before promising any exact behaviour. |
| Customer needs higher-quality incident images | Business requirement, not just FTP setup | Reframe the job around NVR, SD or export workflow instead of relying on FTP stills alone. |
When to contact support
Contact SecurityWholesalers support with your order number, product model, firmware version and one example FTP file if you still need help. It is especially helpful to include a comparison screenshot or note showing how the FTP output differs from local recording.
Related support guides
- Tech Support Guides - Main support hub.
- TP-Link VIGI Support Guides - VIGI support sub-hub.
- How to Export Footage from a TP-Link VIGI NVR - Use this if the real goal is evidence extraction rather than FTP upload.
- How to Add a TP-Link VIGI NVR to the VIGI App - Useful if the site also has app or cloud questions.
Related buying guides
- TP-Link VIGI Buying Guide - Broader VIGI range guidance.
- NVR Buying Guide - Recorder-path guidance if the site needs stronger evidence workflow.
Relevant product categories
- TP-Link VIGI CCTV - VIGI cameras, NVRs and accessories.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Why are my TP-Link VIGI FTP snapshots lower resolution than expected?
Usually because the snapshot path is not behaving like the full main-stream recording path the customer is comparing it against.
-
Do FTP snapshots always use the main stream?
No. That depends on the model, firmware and event workflow.
-
Is this always an FTP server issue?
No. Often the FTP server is receiving exactly what the camera generated.
-
What is the best workaround if I need better evidence?
Use NVR recording, SD recording or proper export workflow for evidence and treat FTP stills as alert images.
-
What should I send support?
Send the camera model, firmware, one example FTP file, and a note showing how it differs from local recording or live view.