Foscam Forum • View topic - Example On How To Tweak FPS Rates For All IP Camera Models

Important Message from Foscam Digital Technologies Regarding US Sales & Service

Foscam.US (aka Foscam Digital Technologies and now Amcrest Technologies) is an independent United States based distributor of "Foscam" branded products. We have been offering telephone support, US local warranty and building the Foscam brand in the US for the past 7 years. Based on our experiences with Foscam and feedback from end users we have launched our own new and improved line of wireless IP cameras and security systems under the Amcrest brand. Working in partnership with the second largest security camera manufacturer in the world, Amcrest was founded with a deep commitment to end-user privacy and security, highly reliable software and hardware as well a seamless and intuitive user experience. For more information, please visit

If you are having trouble with your Foscam cameras, we sincerely apologize for this inconvenience and would love to help. For technical support, response to inquiries and for obtaining replacements for any Foscam IP Cameras or NVR products, please reach out to or call 1-844-344-1113.

If you are interested in exchanging your Foscam camera for an Amcrest camera, we can offer you a massive loyalty discount, even if you are out of warranty. Please send an email to, or call 1-888-212-7538

If you are subscribed to Foscam Cloud (, please contact for support.

If you currently use the manufacturer's cloud service ( or linked in any way to, you will need to contact them directly for support, at

Example On How To Tweak FPS Rates For All IP Camera Models

Users can ask and answer questions regarding Foscam IP Cameras

Moderators: mycam, FOSCAM

Example On How To Tweak FPS Rates For All IP Camera Models

Postby TheUberOverLord » Sat Sep 21, 2013 10:30 am

These examples can be used with any Foscam MJPEG based cameras as well as any newer H.264 based Foscam camera models. Including the FI9821W V1 and V2 and all other H.264 based Foscam camera models currently being sold.

Additional free tools have recently been created, please see these as well as the ones here:

You can use these Interfaces from ANY Internet browser capable device from Computers to Tablets, to Phones and TVs using any operating system and browser they may have. To see how fast each of those devices can process data from the camera. In some cases. The device being used maybe throttling what the camera is actually able to provide.

This may also help you to benchmark your different devices that you use to access your cameras, to see how they perform. When accessing your cameras. Using both local and remote connections. For any of the devices you use to access your cameras.

Please note. You are at the mercy of the ARM based CPU inside the acutal cameras. These CPU's inside the cameras, are not GHz based CPU's. The MJPEG based cameras have slower CPU's then the newer H.264 based camera models but they also have lower resolutions for video and snapshots then the newer H.264 based camera models.

The examples also have links ("In them") that you can use with your own cameras to do these measurements. Without the need to actually download and configure a copy of these Interfaces first ("Which is suggested for long term use").

Please do NOT use an Admin level User Id for your camera, when doing this, using the demo link for your own cameras. You can in fact create a throw-away Operator User Id for your camera, that you can afterwards change the password for or delete from your camera, if needed afterwards. When or if you use these methods.

This also can help you determine the health of your local network, especially more so, if your camera is in wireless mode. By doing different things to increase the FPS ("Frames Per Second") and the Bps ("Bytes Per Second") rates, you see with your cameras. Using these methods.

In the future. Once you use these methods and determine what the average FPS and Bps rates are for your cameras from any given Internet browser capable device. You can simply use these interfaces again to evaluate, if you see any differences. From any of those devices.

It's a good way to easily benchmark, how well your cameras are operating as well as how any Internet browser capable devices you use to access your cameras are performing and if things can be tweaked to make things better.

This all said. It's very important if your camera is using a wireless connection or the device(s) you are using to access your camera are using a wireless connection, to verify that all is well ("First"), with that wireless connection. More here:

Still images from a H.264 based camera. Gain no compression benefit, because that compression is for video, not JPEG based, still images.

A MJPEG based camera set at a resolution of 640x480 has a still image size as an example, that is about 18k bytes per still image. Whereas, the newer H.264 based Foscam camera models are about 80k bytes per still image size, as an example, with a resolution of 1280x720. So, while the H.264 based cameras CPU's are faster then the MJPEG based cameras. The images produced by them are more than 4 times larger, in bytes, per still image. Sizes of images, do vary based on image brightness and complexity as well as camera models. These are simply example image sizes.

Because of this, your FPS rates of still images can be not only throttled by bandwidth, but they also can be throttled by CPU horsepower, required to create these images.

So. I would not compare any of these benchmarks to another benchmark, you may have done, using a daytime cloudy day, to a bright sunny day. Or complex daytime images to non-complex daytime images. Or daytime images to nighttime images. If you want to compare one benchmark to another. It would be best to do so, using the same image based circumstances, with devices accessing your cameras. This is because while one benchmark may have a slower or higher FPS rate. The Bps rate may also be lower or higher as well. Because the size of each image. Could also be smaller or larger at the time, that a specific benchmark is done. You may want to do both daytime and nighttime benchmarks.

It's also important to note, that these cameras have a primary purpose. Which is security. Supporting whatever functions you configure for alarms. So, snapshot requests during non-alarm periods of time are really secondary purpose requests.

These cameras should not and do not, allow these secondary purpose requests, to impact the CPU horsepower they will need to perform the primary purposes they have. If they did, then you might miss whatever you configured to happen during alarm periods, for your camera, that may occur during these secondary purpose requests.

The average FPS rate for the newer H.264 based cameras, is about 1.60 FPS when a camera is being accessed remotely for still images. This is because the images are so large. 1280x720 and there are no methods to change that resolution currently. Minus, presenting that image, as a smaller one.


All these examples, must be viewed in a IE ("Internet Explorer") browser to see both the FPS rates and the Bps rates. Otherwise, using any other browser, you will only see FPS rates.

If you use these methods with your own cameras from within your local network. You will see, FPS and Bps rates as slightly higher then mentioned here.

You can use these methods with your own cameras locally by using your local IP Address and port for your camera or remotely by using your ISP IP Address and port for the camera or your DDNS and port for the camera. This will allow you to see if there are any major differences between the way your camera is accessed.

To get your current ISP IP Address from within your local network. You can use this link:

The internal FPS rate selection In these examples defaults in the examples shown here at 1 FPS. It's more of a maximum limit, then any promise that you can achieve the selected FPS rate, with your camera. You can change the selected FPS rates, in all these examples as well as when using these Interfaces, with your own cameras.

The Internal FPS rate was created as a configurable default value for camera owners to control bandwidth if they allowed others to use these interfaces, or they placed these interfaces in web pages. It does not actually change anything in the camera configuration. It simply is used as a throttle for these Interfaces.

When using these interfaces with your own cameras, it's best to set the internal FPS rate to 30. This will allow you to achieve the current maximum FPS rate possible with your cameras, from the device you are currently using, the interface from.

FI9821W V1 Demo Camera in Houston, TX.

Note: The actual size of the image above has been shrunk to be more web page friendly. Of course this takes no burden off the cameras CPU. Since it's still really producing a 1280x720 image each time.

The actual size of images returned by the camera can be seen using this example:

FI9821W V1 Demo Camera in Houston, TX. Default Image Size:

Whereas, the MJPEG based cameras have a higher FPS rate for still images, because you can select the resolution of the images. 160x120, 320x240 and 640x480.

MJPEG Based Demo Camera

Note: If you use the above interface for your MJPEG based camera and change the resolution. It does change your MJPEG camera resolution. So you will need to change that resolution back, to what it should be.

Even the MJPEG based cameras have an average FPS rate for still images of about 4.20 at 640x480. Yet at a 160x120 resolution, they have an average FPS rate of over 9.00 FPS, for still images.

Please note. That the actual FPS rates you see using the examples above, may vary, depending on how many others are accessing the above examples, at the same time.

The same applies to using these Interfaces with your own cameras. It would be best while using these Interfaces with your own cameras. To be using only this Interface and nothing else at the same time, while using these Interfaces to benchmark your own cameras.

While all these examples are using still images and their FPS rates. These methods do show without using video. How you can help your cameras operate at peak efficiency. By possibly making changes, to achieve the highest possible still image FPS rate possible, for your environment. With each and any of the devices, you use to access your cameras.

Of course there are other methods that can be used by camera owners to determine how their cameras are currently performing.

However, these methods are free. They work with ALL Foscam camera models that are currently being sold. They are convenient and simple to use, require no download, setup or installation and can be used from all Internet browser capable devices, camera owners use, to access any of their Foscam based camera models.

Whereas, other methods, may not currently support or have, all of these benefits.

Direct Links To These Interfaces For Use With Your Cameras:


Please do NOT use an Admin level User Id for your camera, when doing this, using the demo links below for your own cameras. You can in fact create a throw-away Operator User Id for your camera, that you can afterwards change the password for or delete from your camera, if needed afterwards. When or if you use the links below.

You can use any of the below, with these Interfaces, for your own cameras, with these links. From ANY internet browser capable device. Which is running on any Operating System. Which is using any browser. Without the need to use any leading http://


You may want to compare differences, from the same or different devices. Using local, ISP and DDNS access methods.

You may also wish to also create shortcuts, to these links, from those devices. For emergency use, as well. So that you can have alternative access methods to your cameras, from those devices.

For All Foscam MJPEG Based Camera Models:

For All Foscam H.264 Based Camera Models Currently Being Sold:

Note: There is a 5 minute limit for the above links. You can refresh your browser window to reset this, if needed. It's suggested to download your own free copy of the Interface you need, for long term use. This allows you to also be able to configure your copy as needed, for your camera. Which does not have any time limit, by default configuration settings.

Once you are done doing these benchmarks for Foscam MJPEG based cameras. There really is not much you can do that will benefit you even when accessing your MJPEG based cameras with video. This is because, there is no video compression going on. With MJPEG based camera models.

This is NOT true for camera owners, that have Foscam H.264 based camera models. Because there are in fact, other things you can do to tweak your cameras and increase your FPS rates for video as well.

More here for H.264 based Foscam camera owners:

Posts: 13110
Joined: Fri Jun 22, 2012 11:52 pm

Return to Technical Support

Who is online

Users browsing this forum: No registered users and 6 guests