300mb Movie Area

0 views
Skip to first unread message

Armanda Kicks

unread,
Aug 4, 2024, 5:21:53 PM8/4/24
to netmegusli
Imtrying to sell digital products that will all be over 300mb in size even when zipped. Is there a workaround so I can sell a link to a google drive or outside source? It only accepts files not links. If I cant find a workaround Im most likely going to have to cancel my squarespace ging forward. Any help would be appreciated!

On Squarespace, the file size limit for digital products is 300MB. If you are using Squarespace's Commerce features, the only workaround is to host your large files securely on another platform that supports larger files. This is obviously not ideal, but I'd prefer to suggest a workaround than simply tell you it cannot be done. If you use this method, you can create a simple text file such as "readme.txt" that contains the URL for the file and the password (if required). You can then upload this small text file to Squarespace as the "digital file" instead of the "product". For example, Google Drive lets you upload files up to 5TB in size.


Is there no plan to increase this file size limit?

Even a music album in high quality surpasses the 300mb limit. An while a smaller file size might have been of benefit 10 years ago. Now days it's just not an issue. The only limitation is squarespace.


If you need to reduce video files, one program you can use is Handbrake. This is a free video-compression program for both Windows and Mac, and it's amazing at reducing file size without reducing quality. The resulting videos look exactly the same as their originals. Here's a video walk-through of working with handbrake, including which settings to use, where it exports to, etc:


Second is a website called / which offers a bunch of file-compression tools to reduce file sizes of almost any kind of media (videos, audio files, pdfs, jpegs, etc.). On their website under Tools > File Compressors, you'll find all the file types you can compress.


If you need to compress videos like I did, in the Video Compressor tool ( -compressor) they allow you to define the target output size (in our case, 300MB), and not only did it work like a charm (my video went from 606MB to 287MB), the video quality also looks great to me - honestly can't tell the difference between the original and the compressed one).


Also if you can handle hard core command line Un*x tools then you can install ffmpeg on macOS. Don't know about that on Windows. Lots of examples on the web for various conversions with ffmpeg. I used MacPorts to install ffmpeg on my Mac. MacPorts is also fantastic by the way. I use ffmpeg to convert my QuickTime screen recording .mov files to .mp4. for a substantial reduction.


Find my contributions useful? Please like, upvote, mark my answer as the best ( solution ), and see my profile. Thanks for your support! I am a Squarespace ( and other technological things ) consultant open for new projects.


With this new digital "sell anything" update, this file size limit really needs to be lifted. I can't sell any of my products under 300MB. Taking people out of the store to another site, making them download a txt file is just too extra. Please raise the file size limit at least a minimum of 2GB.


Our busines relies solely on selling digital products... It is just so ridiculous, that there is a limit to 300mb. We are in Audio Production and obviously sample packs, plugins & co easily exceed 300mb. In other businesses, be it photography or video, 300mb is even faster exceeded.


It's so sad to see that a company with such beautiful templates, good service and everything is just not able to add ONE FEATURE - because of that we unfortunately had to leave Squarespace to Shopify (after testing many other ones for our desired features).


I want to sell CD quality wave file versions of my album on my site. The ZIP file is 500 MB. So a limit of 300 MB is prohibitive. That's really a bummer for me as a long time Squarespace user and means I have to migrate elsewhere.


After few years full of adventures we were extremely happy we found Squarespace!

We did the site easily, uploaded many of our products etc until.... DUH!!!!

We can't upload many of our products as they are more than 300mb.

Shocked.

Spent a happy month building a website that runs smooth and looks wonderful only to discover that the very same platform is sending us to Shopify... We will go. Sad for the wasted time and for leaving your nice platform just for a silly reason.


Please help! I have a 6 GB video I want to sell on my Squarespace website. I just have no idea how to do this. I read the instructions to upload the file to Google drive and then make a txt file to upload as the "digital file" which links to the actual file.


How and where do I make a txt file? How do I do this to link to a google drive file? Isn't txt just for text files? I have a video file, so will txt even work to link to a video file in Google Drive? I'm so confounded.


I agree but sadly the same is true for any digital product, even those that are less than 300MB and sold directly on Squarespace. We can only remind customers about copyright law and encourage them not to share their purchases. There are no technical controls that can prevent a purchaser from downloading their digital file and then re-upload it to a hosting service (such as Google Drive) where it can be shared online.


I'm a digital artist setting up my shop to sell some of my assets and content. However, I've run into a wall with how small the max file size is for digital products. 300mb is nothing in todays day and age. It is by far the lowest out of any of the major commerce platforms. We pay good money for Squarespace and they claim to be an all in one commerce platform but lack major functionality, this being one of the big ones.


What makes it even more ridiculous is that this forum itself has a max total attachment size of 50mb. The fact that you can only sell digital products that are only up to 6x larger than an attachment to a forum post is crazy to me.


To those still holding on to Squarespace just don't. I personally ended up switching to wix. They offer more space, bigger file sizes for digital products, member areas built in, a lot more video time, and a ton of analytics for your sales.


But considering the alternative which is not being able to sell your products at all, it's the best solution possible. If Squarespace decides to lift these incredibly limiting features I might consider switching back to Squarespace but for now, it's Wix all the way!


My task is to open a large file in READ&WRITE mode and i need to search some portion of text in that file by searching starting and end point.Then i need to write that searched area of text to a new file and delete that portion from the original file.


The above process i will do more times.So I thought that for these process, it will be easy by loading the file into memory by CharBuffer and can search easily by MATCHER class.But im getting HeapSpace exception while reading, even though i increased to 900MB by executing like belowjava -Xms128m -Xmx900m readLargeFileMy code is


You definitely do NOT want to load a 300MB file into a single large buffer with Java. The way you're doing things is supposed to be more efficient for large files than just using normal I/O, but when you run a Matcher against an entire file mapped into memory as you are, you can very easily exhaust memory.


First, your code memory maps the file into memory ... this will consume 300 Meg of memory in your virtual address space as the file is mmaped into it, although this is outside the heap. (Note that the 300 Meg of virtual address space is tied up until the MappedByteBuffer is garbage collected. See below for discussion. The JavaDoc for map warns you about this.) Next, you create a ByteBuffer backed by this mmaped file. This should be fine, as it's just a "view" of the mmaped file and should thus take minimal extra memory. It will be a small object in the heap with a "pointer" to a large object outside the heap. Next, you decode this into a CharBuffer, which means you make a copy of the 300 MB buffer, but you make a 600 MB copy (on the heap) because a char is 2 bytes.


To respond to a comment, and looking at the JDK Source code to be sure, when you call map() as the OP is, you do in fact map the entire file into memory. Looking at openJDK 6 b14 Windows native code sun.nio.ch.FileChannelImpl.c, it first calls CreateFileMapping, then calls MapViewOfFile. Looking at this source, if you ask to map the whole file into memory, this method will do exactly as you ask. To quote MSDN:


The way the OP is calling map, the "specified portion" of the file is the entire file. This won't contribute to heap exhaustion, but it can contribute to virtual address space exhaustion, which is still an OOM error. This can kill your application just as thoroughly as running out of heap.


Finally, when you make a Matcher, the Matcher potentially makes more copies of this 600 MB CharBuffer, depending on how you use it. Ouch. That's a lot of memory used by a small number of objects! Given a Matcher, every time you call toMatchResult(), you'll make a String copy of the entire CharBuffer. Also, every time you call replaceAll(), at best you will make a String copy of the entire CharBuffer. At worst you will make a StringBuffer that will slowly be expanded to the full size of the replaceAll result (applying a lot of memory pressure on the heap), and then make a String from that.

3a8082e126
Reply all
Reply to author
Forward
0 new messages