YouTube to increase upload limit from 10 to 15 minutes


Recommended Posts

Sources at YouTube tell us that online video giant will soon increase the maximum duration of uploaded video clips from 10 minutes to 15 minutes. The move may not mean much to some, but if you're a YouTube uploader, the increase would mean significantly less chopped-up installments of longer form works, and subtly redefine the medium, given that YouTube is the largest video hosting service online.

YouTube Partners (online video companies like us and other content owners who have agreements with the company involving shared ad revenue) are already able to upload videos longer than 10 minutes, but it's a fairly big deal for the rest of the ecosystem? and amateur folk make up a huge portion of that ecosystem.

Just think about it: the move would bring 50% more "haul videos," from shopaholic teen girls; 50% more crazytime rants from random dudes; 50% more hamster montages; and 50% more double (whoah that's almost a triple) rainbows.

Why now? I don't know. Why not? But I'd put my money partially on the company's recent win in the Viacom case, and a sense that they've now figured out more effectively how to help the big content owners (labels, movie studios, TV networks) identify infringing uploads, which might tend to fall largely in that longer-form category.

We're hearing something about a "15 minutes of fame" contest to celebrate the expanded video duration, in which winning uploads will be featured on the YouTube homepage in a future spotlight.

Source: http://www.boingboing.net/2010/07/29/youtube-to-increase.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+boingboing/iBag+(Boing+Boing)

Yeah, increase overall bandwidth usage when you can barely watch a YouTube clip without pausing it for 10 minutes first.

*Waits for the usual OMG WORKS FOR ME, UR CONNECTION!111*

It's starting to become a pretty widespread issue, especially among my friends and relatives who frequently use YouTube.

Don't really see it impacting the bandwidth any more than it currently get's hit.

People with videos over 10 minutes just now just break them into parts.

Yeah, increase overall bandwidth usage when you can barely watch a YouTube clip without pausing it for 10 minutes first.

*Waits for the usual OMG WORKS FOR ME, UR CONNECTION!111*

It's starting to become a pretty widespread issue, especially among my friends and relatives who frequently use YouTube.

Here I am on a crappy 768Kb/s (thats a max of ~90KB/s down) and I only ever have to pause and let YouTube videos buffer when I have other things sucking down bandwidth. But, I do live in an area that has very low usage compared to most other areas (very small town).

That being said, glad to see them increase the time limit. Will be able to watch longer gameplay demos and what not on YouTube without having to go to other sites to get the same thing not cut into pieces.

Don't really see it impacting the bandwidth any more than it currently get's hit.

People with videos over 10 minutes just now just break them into parts.

And what about the thousands if not millions of people that used to make their video blogs, game movies, gameplay footage whatever 10 minutes long

to stick 'em on YouTube, they can now up it to 15 thus requiring more bandwidth to serve when watching and the overall bandwidth usage is increased.

YouTube uses a TON of bandwidth, it uses as much bandwidth as the entire internet did in 2000 - So something like this is drastic.

Here I am on a crappy 768Kb/s (thats a max of ~90KB/s down) and I only ever have to pause and let YouTube videos buffer when I have other things sucking down bandwidth. But, I do live in an area that has very low usage compared to most other areas (very small town).

That being said, glad to see them increase the time limit. Will be able to watch longer gameplay demos and what not on YouTube without having to go to other sites to get the same thing not cut into pieces.

I'm on a 15Mbit that is always at max speed, the problem isn't on my end, it's on YouTube's end, serving the videos.

And what about the thousands if not millions of people that used to make their video blogs, game movies, gameplay footage whatever 10 minutes long

to stick 'em on YouTube, they can now up it to 15 thus requiring more bandwidth to serve when watching and the overall bandwidth usage is increased.

YouTube uses a TON of bandwidth, it uses as much bandwidth as the entire internet did in 2000 - So something like this is drastic.

I suppose, but the sites just ****ed for speed anyway, so slow half the time laugh.gif

This is friggin awesome, I hate when I need to do a video and all I need is a couple of extra minutes. I understand why they original capped it at 10 minutes but it is stupid given that piraters can easily chop up a video then upload it.

Yeah, increase overall bandwidth usage when you can barely watch a YouTube clip without pausing it for 10 minutes first.

*Waits for the usual OMG WORKS FOR ME, UR CONNECTION!111*

It's starting to become a pretty widespread issue, especially among my friends and relatives who frequently use YouTube.

I notice that too, videos load really slowly sometimes. No where near my connection speed limit.

OK, how exactly is this going to make any difference in overall bandwidth consumption? Say someone wants to upload a 30 minute video. Right now, they would have to split it into 3 pieces. After the change, they would have to split it in two pieces. The overall amount of space used is basically the same.

You Tube is extending videos up to 15 Minutes. I think it's a good idea. Because lets say you want to watch

a excerise video for instants you can wath the full video with out interupchions. But on the other side you don't want to use up all the download

because there's only so much you can do.

OK, how exactly is this going to make any difference in overall bandwidth consumption? Say someone wants to upload a 30 minute video. Right now, they would have to split it into 3 pieces. After the change, they would have to split it in two pieces. The overall amount of space used is basically the same.

Because surprisingly, a lot of video blogs, footage of games, uploaded speeches whatever sometimes exceed 10 minutes but people don't turn them into several parts, they just edit and cut it down to 10 minutes. A lot of content

is edited down to 10 minutes because people don't want to watch a 2,3 or 4 parter video usually. So now, they don't have to cut those extra minutes away and the servers will have to feed a longer video file to thousands if not millions of users

on the general scale ... And that's a huge difference in bandwidth consumption.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!