Frequently Asked Questions

Every video you upload is processed into multiple resolutions (320p, 720p, and 1080p). We use HLS (HTTP Live Streaming), which allows the player to be smart: if a viewer is on a patchy mobile connection, it stays smooth at 320p; if they have fiber, it looks crisp at 1080p.

I have intentionally avoided 4K. From a First Principles perspective, 4K file sizes lead to slower load times and higher costs that don't add much value for a coaching call or a sales demo.

Yes. Because we are built on a Global Edge Network, your Loops are cached in data centers all over the world. If your viewer is in London, they get the signal from a server just a few miles away rather than waiting for it to travel from New York. This keeps latency low and ensures the video starts almost the moment they hit play.

Video is surprisingly difficult to get right across every device, especially with the quirks of Safari on iPhones. I spend a significant amount of time testing the player to make sure it's stable. It appears to work seamlessly across the vast majority of modern setups, but if you ever find a specific device where a Loop isn't playing right, you can send me the details and I'll look into the code myself.

If a new browser standard comes out in two years, I need your master file to "up-cycle" your content to the new standard. If I deleted it to save money today, your videos would be stuck in the past. Keeping the master is the only way to ensure your Loops remain future-proof.

The "Success Tax" is one of the things I hate most about legacy platforms. If a video goes viral, you shouldn't get a terrifying bill.

At 52loops, if you cross your tier limit mid-month, I will move your account to the next level immediately to keep things stable, and I'll cover the cost of that upgrade for the rest of your billing cycle. Your new rate only applies starting with your next scheduled payment.

To ensure your Loop plays for everyone, we transcode it into three resolutions and thousands of tiny HLS segments. This process usually adds about 50% to 80% to the original file size. That 1GB upload might end up sitting at 1.7GB in our vaults. I've tried to account for this by making the tier limits generous enough that you don't have to do the mental math.

I keep the math honest. Storage is the total size of your hosted files (including renditions). Bandwidth is the actual video signal delivered to your viewers. I don't count the "overhead" or small data packets used for player logic. You can track this in real-time on your dashboard.

Yes, each tier has a Loop Capacity. While we are generous with storage (GB), every video requires metadata processing and database tracking. If you have 500 tiny videos, it places more strain on the system than one large 2-hour video. We've set asset limits on each tier to ensure the dashboard stays fast and the global delivery remains instant for everyone.

I'm not a fan of hard-stopping a business mid-stride. I've designed 52loops to be flexible so your "signal" stays live even during growth spurts.

For Bandwidth Spikes (Occasional Bursts): If a video goes viral or you have a high-traffic launch, don't worry. We allow for "Occasional Bursts" where your daily usage can spike up to 20% of your monthly allowance for up to 48 hours without any penalty or upgrade. We don't throttle your videos during these moments.

For Sustained Growth (Tier Alignment): If your baseline usage or total video count (Loop Capacity) consistently stays above your tier's limit, it's a sign your business has found its resonance. We'll notify you via email and help you transition to the next frequency.

The Success Credit: If you do hit your hard storage or asset limit mid-month, the platform automatically moves you to the next tier to keep things stable. I'll cover the cost of that upgrade for the rest of your current billing cycle, i.e. you won't see the new rate until your next scheduled payment. It's my way of celebrating your growth instead of taxing it.

I use a "Referer check"—a digital bouncer for your content. When you embed a Loop, the platform checks exactly where that request is coming from. If someone tries to post your video link on a public forum, the circuit breaks and the video won't play. It's a high bar that stops the vast majority of "hotlinking" that would otherwise drain your bandwidth.

Absolutely. A video should feel like a natural part of your site, not an ad for a hosting company. You can strip away the "Powered by" badges and customize the player colors to match your frequency. We focus on clean embeds and fast loading times.

By default, the player is designed for streaming, not downloading. I've removed download buttons to keep your Loops within the circuit you've created. While a very technical user can "rip" almost any video on the web, 52loops makes it difficult enough that the average viewer stays within the player.

Most video hosts offer a free tier to inflate their user numbers, but they often end up hiding the real costs in bandwidth "overages" or "fair use" penalties later on.

It seems to me that when you have 10,000 free users, the paying customers are the ones actually subsidizing the bill. I'd rather keep the circuit exclusive to people who are serious about their work. By requiring a commitment upfront, I can ensure the platform remains fast and the infrastructure stays high-performance for everyone involved.

The 7-day full refund is a way to try it out and see if it works for you.

I think of creation as a rhythm rather than a one-time broadcast. A single video is a Loop—it's the lesson or the pitch you send out.

The platform is the Loops, the ecosystem where those signals live and return value to you. We treat it as a signal that enters a loop, where rewatches and resonance complete the circuit.

The "52" represents a full cycle of a year. Whether it's 52 weeks of consistent creation or the 52 white keys on a piano, it's about building something that lasts. I wanted a name that reflected the recurring value of your content rather than just a place where files go to sit on a shelf.

It is just me behind the scenes, but I have built 52loops to be an entirely autonomous circuit. I realized early on that for this to be a reliable backbone, it couldn't depend on me manually pushing buttons.

The "Loops"—the platform itself—are built on a modern, self-healing stack. Once you hit upload, the code takes over. Even if I am off the grid for a few days, your videos will continue to process, your embeds will stay live, and the global edge network will keep delivering your signal. I am the architect, but the infrastructure is designed to run itself.

I'm not interested in holding your content hostage. If you decide that 52loops isn't the right circuit for you anymore, you can export your data and move on. Export is free, by the way. I want you to stay because the platform provides value, not because it's too difficult to switch.