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.

Legacy giants carry the weight of thousands of employees, massive offices, and inefficient tech stacks. They need those $2,000 overage bills to keep their own machine running.

By keeping our overhead low and using high-performance, modern delivery like Cloudflare, we don't have to "tax " your viral moments. We aren't carrying the weight of a legacy empire, so we can afford to be an empathetic peer.

Egress is simply the movement of data from a server to your viewer. Most platforms use outdated architectures that incur high costs from their own providers, and they pass that markup (often 500% or more) on to you.

By building on a modern, zero-egress backbone and partnering with providers in the Cloudflare Bandwidth Alliance, we eliminate the middleman markup. You pay for the actual delivery, not the legacy company's overhead.

Yes. Most learners watch course videos on 1080p screens or smaller. According to StatCounter's global desktop resolution data, 1920x1080 is the single most common monitor resolution among PC users, and most laptops ship at 1080p or below.

At typical viewing distances on a 13-inch or 14-inch laptop screen, the human eye cannot resolve the additional pixel density that 4K provides over 1080p. The perceptual difference from upgrading beyond 1080p is negligible for the majority of your students, while the bandwidth cost is roughly 3 to 4 times higher.

Recording in 4K and delivering in 4K are separate decisions.

Recording in 4K is reasonable if your camera supports it. You gain post-production flexibility, including room to crop, reframe, and stabilize footage without losing sharpness in the final export. A video recorded at 4K and exported at 1080p often looks cleaner than one recorded natively at 1080p.

Delivering in 4K to students increases bandwidth cost without a meaningful quality improvement for most learners. The practical recommendation: record in 4K if your workflow benefits from it, then export and upload at 1080p.

52loops transcodes and delivers up to 1080p. You can upload at your recorded resolution, including 4K source files, and the platform will transcode down to an optimized delivery format.

The 1080p delivery cap is a deliberate infrastructure decision, not a technical limitation. It aligns the delivery resolution with what most learners can actually see, and it is what makes the fixed-capacity pricing model operationally stable. For more on the reasoning, see the article on why 1080p is the sweet spot for course creators.

4K delivery is technically possible. We will add it when the data shows a meaningful share of students can actually benefit from it, meaning widespread 4K screen adoption among learners.

Until that threshold is reached, enabling 4K delivery would mean charging more for something most students cannot see. The current 1080p cap is not a technical constraint. It is a deliberate alignment between what learners can perceive and what you should pay to deliver.

When the hardware reality changes, the delivery cap will change with it.

HLS (HTTP Live Streaming) is the delivery standard 52loops uses for all video playback. Instead of sending a single fixed-quality video file, the platform encodes your upload into multiple quality levels (320p, 720p, 1080p) and breaks each into short segments.

The player monitors your viewer's available bandwidth in real time and selects the appropriate quality level automatically. On a fast connection, your viewer gets 1080p. On a mobile connection mid-commute, the player steps down to 720p or 320p to keep playback smooth without buffering.

The practical result is that your video starts faster and stalls less often, regardless of the viewer's network conditions. HLS is the same delivery method used by Netflix and YouTube, and it is supported natively on every modern device and browser.

A CDN (Content Delivery Network) is delivery infrastructure. It moves files from servers to viewers quickly, using a global network of edge nodes. Bunny.net, Cloudflare, and AWS CloudFront are CDNs.

A video platform is a complete product built on top of delivery infrastructure. It includes the player, transcoding pipeline, domain-locking, analytics, and support, assembled and maintained so you do not have to.

52loops is a video platform. It uses a CDN (Cloudflare's global edge network) as part of its infrastructure, but the CDN is one component among several, not the product itself.

The distinction matters for cost estimation. A CDN price covers delivery only. A video platform price covers delivery plus everything required to make delivery work reliably for non-technical operators.

A Highway Unit is the fundamental building block of your 52loops account. Instead of forcing you into restrictive tiers, we provide you with a fixed bucket of resources.

Every single feature, including our high-performance Player, Global CDN, ad-free hosting, and referer protection—is included in every Highway Unit.

Each unit provides a base of: - 1TB Bandwidth (Upgraded to 2TB for Founding members ) - 100GB Storage - 100 Video Slots

As your business grows, you simply add more units to increase these limits. See How Stacking Units works .

Instead of complex "Pro" or "Enterprise" tiers where you pay for features you don't need, 52loops scales linearly. Each Highway Unit you add gives you exactly the same predictable capacity.

Example: - 1 Unit: 1TB Bandwidth, 100GB Storage, 100 Videos ($20/mo) - 2 Units: 2TB Bandwidth, 200GB Storage, 200 Videos ($40/mo) - 5 Units: 5TB Bandwidth, 500GB Storage, 500 Videos ($100/mo)

You have the same total freedom and features regardless of whether you have 1 unit or 100.

Most platforms treat your storage and video slots as a "metered" resource that can be taken away or shared. At 52loops, your Highway Units represent reserved capacity.

Think of it like a mobile data plan with a dedicated data bucket: you've bought a specific amount of space and bandwidth that is yours to use. Those slots and gigabytes are dedicated to your account, ensuring guaranteed performance and availability for your assets at all times.

It's the penalty legacy platforms charge you for doing exactly what you set out to do—succeed.

When your video goes viral or your message reaches a massive audience, traditional hosts see that traffic as a "liability" or a cost to be recovered. They trigger automated overage fees or force you onto enterprise plans mid-month, effectively taxing your growth. At 52loops, we view that same traffic as a signal to be amplified, not a billable event.

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 genuinely cross your unit limits mid-month, the system automatically adds an additional "Highway Unit " to your account to keep things stable. I cover the cost of that upgrade for the rest of your current billing cycle.

Example: Imagine you have 1 Highway Unit (1TB Bandwidth). On the 15th of the month, a video goes viral and you hit 2.5TB. 1. We automatically add a 3rd Unit (increasing your limit to 3TB). 2. Your videos keep playing without interruption. 3. You pay $0 extra for that 3rd unit for the remainder of the month. 4. At the start of the next cycle, you can choose to keep the 3rd unit if your growth is permanent, or drop back to 1 unit if it was just a temporary spike.

I distinguish between temporary spikes and sustained growth to keep your billing fair.

A Burst is a temporary traffic spike, like when a video gets picked up by a newsletter for 48 hours. It's a moment of celebration, not a reason to force you onto an "Enterprise" plan. These are covered by our Growth Buffers .

Resonance is when that traffic level remains consistent over several months. This indicates your business has genuinely grown, and it makes sense to stack another Highway Unit to support that new baseline.

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 usage can spike without immediate penalty. We don't throttle your videos during these moments.

**For Sustained Growth (Stacking Units ):** If your usage consistently stays above your current allowance, it's a sign your business has found its resonance . You can simply add another Highway Unit to increase your capacity (Storage, Bandwidth, and Videos) linearly.

**The Growth Buffer :** If you do hit your hard limits mid-month, the platform automatically adds the next Highway Unit to keep things stable. I'll cover the cost of that additional capacity for the rest of your current billing cycle. You won't see the new rate until your next scheduled payment. It's my way of celebrating your growth instead of taxing it.

Legacy hosts often wait until the end of the month to "tax" you for traffic you've already used. At 52loops, we never bill you for past usage. If you exceed your limit, our Growth Buffer covers you for the rest of the cycle at no cost. You only ever decide to move to a higher capacity for *future* billing cycles.

Invoice Anxiety is the psychological burden felt by business owners when using usage-based billing models. It occurs when success—like a viral video or a successful product launch—leads to unpredictable and often massive overage charges.

Instead of celebrating a win, you're stuck doing damage control on your bank account. We built 52loops specifically to eliminate this anxiety by using Reserved Capacity instead of metered billing.

Early adopters are the lifeblood of this platform. To thank you for joining early, I have doubled the standard bandwidth for all Highway Units . While a Highway Unit normally includes 1TB, Founding members get 2TB of bandwidth per unit. This bonus is locked in for the life of your subscription, as long as you stay active, you keep the double capacity.

Yes, each Highway Unit includes a 100-video capacity. While we are generous with storage (GB), every video requires metadata processing and database tracking.

Legacy platforms often use a "Content Tax" by charging per-video regardless of size. At 52loops, 100 videos is a manageable chunk for most micro-businesses, and if you need more, you simply stack another Highway Unit linearly.

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 Highway Unit 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.

No. I find the "Seat Tax" common in legacy SaaS to be particularly frustrating. You shouldn't be penalized for hiring a virtual assistant or collaborating with a partner. You are taxed on the resources the platform uses (bandwidth and storage), not on the number of people in your team.

Yes. I want you to be completely confident in the circuit you're building. We offer a 7-day no-hassle refund guarantee. If you find that 52loops doesn't fit your workflow within the first week, just send me an email and I'll refund your payment in full, no questions asked.

Yes, directly. Higher resolution means larger file sizes and more bandwidth consumed per view.

A single minute of 4K video at standard bitrates requires approximately 15-25 Mbps to stream. The equivalent 1080p stream requires 5-8 Mbps. On file size, 4K runs roughly 4 times the storage footprint of 1080p.

On platforms that bill per gigabyte of bandwidth delivered, this math shows up directly in your invoice. As your course library grows and student count scales, the resolution decision compounds. Delivering at 4K on a usage-based platform will cost significantly more than delivering at 1080p with fixed-capacity pricing.

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.

An Infrastructure Anchor is a philosophy of billing that prioritizes stability and predictability over variable "metered" costs.

In the same way an anchor holds a ship steady during a storm, your Infrastructure Anchor ensures your hosting expenses remain fixed and manageable even during traffic spikes. By using Highway Units , we provide a stable backbone for your business operations so you can focus on growth without fear of your tools turning against you.

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 no-hassle 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.