{"id":"pg_4syj632arx8c","property_id":"prp_pfcr5h8cztsp","domain_id":"dom_gkgeprhezjg4wq","root_domain":"smashsend.com","locale":"en","url":"https://smashsend.com/blog/email-attachment-size-limit","url_hash":"b915b1fae5b159cf5596144230a5a0de36ffc2cc3db174e03d3cc533e6fb6988","path":"/blog/email-attachment-size-limit","depth":1,"canonical_url":"https://smashsend.com/blog/email-attachment-size-limit","canonical_page_id":null,"page_type":"article","page_type_guess":"article","state":"indexed","skip_reason":null,"priority":"1.4","discovered_via":"sitemap","first_seen_at":"2026-08-28T03:07:01.092Z","last_seen_at":"2026-09-27T04:07:03.013Z","http_status":200,"content_hash":"319bb5c11e02bba868fca03fc3deba9c10aae2f8e3300b2435dd9326c8a32ed3","title":"Navigating The Email Attachment Size Limit: A B2B SaaS Guide","description":"Stop your emails from bouncing. This guide unpacks the email attachment size limit, hidden costs, and smart strategies for B2B SaaS teams to ensure delivery.","author":"SMASHSEND","published_at":"2026-02-06T00:00:00.000Z","modified_at":"2026-02-06T00:00:00.000Z","word_count":3479,"reading_time_sec":949,"lang_detected":"en","images":[],"links_out":null,"markdown_source":"readability","refresh_interval":"monthly","last_fetched_at":"2026-09-27T04:11:00.868Z","next_refresh_at":"2026-10-27T04:11:00.868Z","runs_count":2,"changes_count":0,"last_changed_at":null,"fail_count":0,"last_error":null,"created_at":"2026-08-28T03:07:01.092Z","updated_at":"2026-08-28T03:07:01.092Z","inlinks":0,"inlinks_body":0,"outlinks":33,"outlinks_external":20,"anchor_terms":[],"template_score":null,"cash":"0","cash_total":"0.10","pagerank":"0.00145661129697194","is_orphan":true,"link_confirmed":true,"discovered_wave":0,"embedded_hash":null,"embedded_at":null,"domain_name":null,"brand_color":null,"domain_rank":null,"spam_score":null,"markdown":"1.  [\n    \n    Home\n    \n    ](https://smashsend.com/)\n\n/\n\n3.  [\n    \n    Email Marketing Blog\n    \n    ](https://smashsend.com/blog)\n\n/\n\n5.  [\n    \n    Email Attachment Size Limit\n    \n    ](https://smashsend.com/blog/email-attachment-size-limit)\n\nYou send a critical invoice. You fire off a welcome email with a PDF guide. And then… bounce.\n\nThe culprit is almost always an **email attachment size limit**, a frustratingly simple hurdle that can bring your most important B2B communications to a screeching halt. It's like trying to send a massive piece of furniture through a tiny mail slot—it just isn't going to fit.\n\n## Why Your Most Important Emails Are Bouncing\n\nWhen a crucial email fails, it's not just a technical hiccup. It's a business problem. A bounced email can stall customer onboarding, delay payments, and even chip away at your hard-earned sender reputation. The first step to fixing this is understanding _why_ it happens in the first place.\n\nThe root of the issue lies in a set of invisible rules that govern every single email sent. Every email provider, from Gmail to Outlook, puts a cap on the _total size_ of a message. And that's the key part—it's not just about the file you attach. The limit applies to everything: the text in your email, the images in your signature, and even the hidden encoding data that makes your attachment bigger in transit than it looks on your computer.\n\n## The Evolution of Email Limits\n\nThese limits have been around forever, evolving from the dial-up days of the 90s. Back in the early 2000s, Gmail made waves by setting a **25 MB** total message size limit. This was a game-changer compared to competitors like Hotmail, which only allowed a measly 2 MB at the time.\n\nBut even with today's larger limits, the core problem hasn't gone away, especially for businesses sending rich, detailed documents. A seemingly innocent attachment can easily tip an email over the size limit once all the other elements are factored in.\n\n> For a SaaS business, a bounced email isn't just a failed delivery. It's a failed customer touchpoint that can disrupt the entire user lifecycle, from activation to renewal. Improving your sending strategy is key to maintaining strong [email deliverability best practices](https://smashsend.com/blog/email-deliverability-best-practices).\n\n## Beyond Just One File\n\nThings get even trickier when you're sending multiple files. If your most important emails are bouncing because you've included several large images, it's a good time to learn how to [attach pictures in email the right way](https://receiptrouter.app/blog/how-to-attach-pictures-in-email).\n\nEach file adds to the total weight of the message. The cumulative size can quickly blow past provider limits, even if each individual file seems small enough. We'll break down exactly how this happens and give you practical strategies to get around these limits for good.\n\n## Understanding Email Provider Attachment Limits\n\nEvery email provider plays by its own set of rules when it comes to attachment sizes, creating a confusing patchwork of standards across the internet. But over the years, a general consensus has emerged. Most of the big players—like [Gmail](https://www.google.com/gmail/), [Outlook](https://outlook.live.com/), and [Yahoo Mail](https://mail.yahoo.com/)—have settled around the same magic number: **25 MB**.\n\nBut that **25 MB** cap isn't just for your file. It's for the _entire_ message. That includes the email body, your fancy signature, any inline images, and all the hidden header information. Think of it like checking a bag at the airport; they weigh the whole suitcase, not just what you packed inside. If the total package is overweight, it gets rejected on the spot.\n\nThis wasn't always the standard. The journey from tiny text-only attachments to today's 25 MB limit reflects decades of evolving infrastructure and user expectations.\n\n![Diagram showing the evolution of email attachment sizes from <1MB in the 1990s to 25MB today.](https://smashsend.com/blogs/email-attachment-size-limit/email-attachment-size-limit-attachment-evolution.jpg)\n\nAs you can see, the slow but steady increase in attachment size has mirrored our growing need to share richer, more complex information.\n\n## The Hidden Weight of Base64 Encoding\n\nNow for the part that trips up almost everyone. The moment you hit \"send,\" your attachment actually gets bigger. To travel safely across the internet's complex network of servers, email systems use a process called **Base64 encoding**. This essentially converts your binary file into a plain text format that any email server can understand.\n\nThis encoding step is non-negotiable for compatibility, but it comes with a cost: it bloats your file size by roughly **33-37%**.\n\n> This means your **20 MB** presentation is actually closer to **27 MB** by the time it reaches the recipient's server. This encoding overhead is the number one reason emails with seemingly \"safe\" attachments get bounced for being too large.\n\nBecause of this hidden size increase, a file that looks perfectly fine on your desktop can easily tip the scales and exceed the 25 MB limit once it's encoded. As a rule of thumb, the _true_ maximum file size you can reliably attach is closer to **18 MB**. Anything larger is a gamble.\n\n## Decoding Common Provider Limits\n\nWhile **25 MB** is the common benchmark, it's far from a universal law. Some providers are a bit more generous, while others—especially in corporate IT environments—enforce much stricter internal limits to manage server load and security. When you're sending B2B emails, you can never assume the person on the other end has the same capacity you do.\n\nTo help you navigate this, here's a quick reference guide for some of the most common email services.\n\n## Quick Guide to Email Provider Attachment Limits\n\nThis table breaks down the advertised limits versus the practical reality after encoding.\n\nEmail Provider\n\nAdvertised Attachment Limit\n\nActual Sendable Size (Approx)\n\nKey Consideration\n\n**Gmail**\n\n25 MB (total message)\n\n~18 MB\n\nAutomatically prompts users to send larger files via Google Drive.\n\n**Outlook & Microsoft 365**\n\n20 MB (total message)\n\n~15 MB\n\nBusiness plans can often be configured for larger sizes by an admin.\n\n**Yahoo Mail**\n\n25 MB (total message)\n\n~18 MB\n\nSimilar to Gmail, with a hard cap on the total encoded message size.\n\n**Zoho Mail**\n\n25 MB (total message)\n\n~18 MB\n\nOffers higher limits (up to 1 GB) via its WorkDrive integration.\n\n**Proton Mail**\n\n25 MB (total message)\n\n~18 MB\n\nCan send up to 100 files, as long as the total size is under the limit.\n\nAs you can see, the advertised number is never the full story. For developers integrating with these platforms, it's crucial to understand these nuances. For instance, when working with Gmail, it's helpful to get familiar with the [Google Mail API](https://smashsend.com/blog/google-mail-api) and its specific behaviors around attachments and large files.\n\nUnderstanding these hard numbers—and the crucial impact of encoding—is the first and most important step to preventing deliverability failures before they ever happen.\n\n## The Real Business Cost of Hitting an Attachment Limit\n\nHitting an email attachment size limit feels like a simple tech glitch, but for a B2B SaaS company, the fallout is anything but simple. This isn't just a bounce notification in your outbox. These failures create real, measurable business problems that can stall onboarding, choke cash flow, and quietly chip away at your sender reputation.\n\nThink of it from the email provider's perspective. When an email from your domain bounces, it's a small red flag. When it happens consistently because of oversized attachments, providers like [Gmail](https://www.google.com/gmail/about/) and [Outlook](https://www.microsoft.com/en-us/microsoft-365/outlook/email-and-calendar-software-microsoft-outlook) start seeing you as a risky sender. Over time, this cumulative damage to your reputation means even your perfectly sized, mission-critical emails are more likely to get routed to spam.\n\n## How It Hits Your Users and Your Revenue\n\nDeliverability is just one piece of the puzzle. The bigger problem is the terrible user experience. A new customer is eagerly waiting for your \"Getting Started\" guide. Your finance team is counting on an invoice getting paid. A hot lead is expecting a proposal.\n\nIn each case, the recipient is just met with silence. They have no idea the email bounced—all they know is that you didn't deliver. This friction inevitably leads to frustrated support tickets, delayed payments, and a first impression that feels clunky and unprofessional.\n\nFor any SaaS business, the consequences are painfully direct:\n\n-   **Failed Onboarding:** Your welcome email with a crucial setup PDF gets rejected. That new user is now stuck, confused, and far more likely to churn before they even get started.\n    \n-   **Delayed Cash Flow:** An invoice with a detailed statement of work attached bounces back. That's a direct hit to your company's finances, pushing your payment cycles out.\n    \n-   **Lost Sales Deals:** You send a detailed proposal to a high-value prospect, but their server rejects it. Your team looks unresponsive, and the deal quietly goes to a competitor.\n    \n\nEach of these isn't just a failed email; it's a critical breakdown in your customer lifecycle. The cost is lost activation, lost revenue, and lost retention—all triggered by a file that was just a few megabytes too big.\n\n## The Hidden Mess of Data Sprawl\n\nThe problem doesn't stop with emails that fail to send. Relying on attachments as a primary way to share information creates a massive internal headache: data sprawl. Research shows this common practice generates nearly **6,000 unnecessary duplicate files per employee every single year**. Across an entire company, that balloons into petabytes of uncontrolled, unmanageable data.\n\n> We're talking about an \"attachment apocalypse.\" This chaos creates serious security and compliance holes. Countless duplicates of sensitive documents—proposals, invoices, contracts—are left sitting in inboxes with zero version control, exposing your business to data breaches and making [GDPR compliance](https://gdpr-info.eu/) a nightmare.\n\nTrying to manage this digital clutter burns through IT resources and kills productivity as your team wastes time hunting for the right version of a file. What seems like a harmless act of attaching a document becomes a huge operational and financial drag when scaled across an organization. Suddenly, the true cost of hitting an email attachment limit looks a lot bigger than a single bounce notification.\n\n## Smarter Ways To Send Large Files\n\nHitting an email attachment size limit doesn't mean you have to abandon sharing important files. It just means it's time to adopt smarter, more reliable methods that work _with_ modern email infrastructure, not against it.\n\nInstead of crossing your fingers and hoping a massive attachment makes it through, you can use proven strategies that guarantee your files arrive safely every time. These approaches don't just bypass size restrictions; they also give you far better security, control, and tracking.\n\n![Diagram illustrating data transfer: a box labeled 'attachment' sends a 'cloud link' to a paper airplane labeled 'zip', flying towards a cloud with a gear.](https://smashsend.com/blogs/email-attachment-size-limit/email-attachment-size-limit-data-transfer.jpg)\n\nThis really shows the evolution of file sharing—moving from clunky compression to streamlined, direct cloud links that just work.\n\n## The Old Way: Compressing Files\n\nFile compression, or \"zipping\" files, has been the go-to trick for decades. The idea is simple: package one or more documents into a single, smaller `.zip` archive to hopefully sneak under the attachment limit.\n\nThis can work wonders for files that aren't already compressed, like text documents, source code, or spreadsheets. But it's far from a silver bullet.\n\n-   **Limited Effectiveness:** Media files like JPEGs, PNGs, or MP4 videos are already highly compressed. Zipping them barely makes a dent in their size.\n    \n-   **Security Red Flags:** Many corporate firewalls and email security gateways automatically block `.zip` files on sight. They are a classic delivery vehicle for malware, so your well-intentioned email could easily end up quarantined or in the spam folder.\n    \n\nWhile zipping might seem like a quick fix, you're often just trading one deliverability problem for another.\n\n## The Best Way: Using Cloud Storage Links\n\nHonestly, the most reliable and professional way to share large files is to stop attaching them to emails completely. Instead, upload your file to a secure cloud service and just share the link.\n\nThis approach completely sidesteps the **email attachment size limit**.\n\nServices like Google Drive, Dropbox, or your company's own Content Delivery Network (CDN) are built for this exact purpose.\n\n> By sending a lightweight link, your email's total size remains tiny, virtually guaranteeing it won't be rejected. This method also unlocks powerful features you'd never get with an attachment, like version control, access permissions, and even download tracking.\n\nIf you're still stuck, it's worth learning [how to send large files email](https://hostmora.com/how-to-send-large-files-email/) using modern techniques that avoid these outdated limitations.\n\n## The Developer Way: Leveraging a Transactional API\n\nFor developers and product teams building automated communications—think reports, invoices, or data exports—a transactional email API is the most bulletproof solution. Instead of trying to attach a bulky file directly, you use the API to dynamically generate a secure, time-sensitive download link.\n\nHere's what that looks like in a typical B2B SaaS app:\n\n1.  A user in your platform requests a large data export.\n    \n2.  Your backend gets to work, generating the file and storing it securely in the cloud (like on Amazon S3).\n    \n3.  Your system then calls a transactional email service like SMASHSEND to fire off an email to the user.\n    \n4.  That email contains a unique, secure link for them to download the file they just requested.\n    \n\nThis automated workflow ensures **100% reliable delivery** for even the largest files. It keeps your core transactional emails lean and deliverable while giving your users a secure and seamless experience. It completely solves the attachment problem at scale.\n\n## How SMASHSEND Solves Attachment Headaches for Good\n\n0:00\n\n/\n\n0:00\n\nTrying to force large attachments through email is like trying to fit a square peg in a round hole. It's a constant battle against the built-in limits of the system. Instead of fighting that losing battle, the [SMASHSEND platform](https://smashsend.com/) sidesteps the problem entirely.\n\nWe've built our system around a simple, powerful philosophy: create lean, engaging emails that drive action, without ever attaching a single bulky file. This turns your email from a slow, unreliable delivery truck into a smart, nimble messenger.\n\n## Link to Resources, Don't Attach Them\n\nThe secret is to stop sending the _file_ and start sending the _path_ to the file. Host your key documents—case studies, white papers, invoices, or onboarding guides—on a secure, central server. Then, use SMASHSEND's personalization engine to send each user a direct link to the exact asset they need.\n\nThink about how this streamlines common SaaS workflows, all without a single attachment:\n\n-   **New User Onboarding:** A welcome email automatically includes a personalized link, taking a new user directly to the setup guide for their specific subscription plan.\n    \n-   **Sales Follow-Ups:** An email to a prospect contains a tracked link to a case study most relevant to their industry, pulled dynamically from your content library.\n    \n-   **Billing and Invoices:** Automated notifications link customers directly to their secure portal to view and download their latest invoice.\n    \n\nIn every one of these scenarios, the email itself stays small, fast, and highly deliverable. You get all the credit for sharing critical information with none of the deliverability risks.\n\n## Making Sure Your Link-Based Emails Actually Arrive\n\nOf course, sending a link is useless if the email lands in spam. This is where SMASHSEND's deliverability infrastructure becomes your unfair advantage. We handle all the technical heavy lifting to give your emails the best possible shot at hitting the inbox.\n\n> A link-based email strategy only works if your deliverability is rock-solid. Otherwise, you've just traded one problem for another. SMASHSEND is built to ensure these crucial, link-driven communications don't just get sent—they get delivered, opened, and clicked.\n\nOur platform gives you the tools you need to build and protect a stellar sender reputation. From dedicated IPs and automated warm-up sequences to ensuring your **SPF**, **DKIM**, and **DMARC** records are perfectly configured, we've got you covered.\n\nThis foundation means you can confidently build your entire messaging strategy around secure, lightweight links. It's time to stop worrying about attachment limits and start focusing on what really matters: driving results.\n\n## Avoiding The Gmail 102 KB Clipping Problem\n\nAttachments aren't the only size limit that can trip you up. There's another, equally frustrating issue lurking in your email's code, and it has nothing to do with attached files. It's [Gmail](https://gmail.com/)'s notorious **102 KB** HTML size limit.\n\nThis limit is all about the raw weight of your email's underlying code. If your beautifully designed marketing newsletter, product update, or automated lifecycle message is too complex, Gmail will unceremoniously \"clip\" it. This shoves your call-to-action, unsubscribe link, and other critical content behind an intrusive \"View entire message\" link. Just like that, your carefully crafted message is broken, and engagement plummets.\n\n![A sketch illustrating an email message clipped due to a 102 KB size limit, partially visible within an envelope.](https://smashsend.com/blogs/email-attachment-size-limit/email-attachment-size-limit-clipped-email.jpg)\n\n## Why This Obscure Limit Still Matters\n\nThis weird limitation is a ghost from Gmail's original 2004 architecture. For some reason, it's stuck around, crippling modern newsletters and automated campaigns sent to its massive user base. With over **1.8 billion** Gmail users, this isn't a niche problem you can afford to ignore. Some growth teams have even traced significant engagement drops directly back to this jarring formatting quirk. Discover more insights about [Gmail's persistent 102 KB limit](https://tedium.co/2020/12/22/gmail-102kb-email-size-limit-history/).\n\nWhen your message gets clipped, it's not just a bad look. Your tracking pixels often don't fire, leading to wildly inaccurate open rates. Even worse, the most important content—usually sitting at the bottom of the email—becomes completely invisible to a huge chunk of your audience.\n\n> Clipping is a silent killer for B2B SaaS emails. It can hide critical links for feature adoption, obscure important billing information, and make it impossible for users to unsubscribe easily, which can lead to spam complaints.\n\n## Practical Tips To Keep Your HTML Lean\n\nThe good news? Keeping your email's code under the **102 KB** limit is totally achievable with a few smart habits. The goal is to trim unnecessary code bloat without sacrificing your design.\n\n-   **Minimize Your CSS:** Ditch the overly complex or redundant CSS styles. Always use shorthand properties where you can, and consider \"inlining\" your styles, which is often more efficient for email clients anyway.\n    \n-   **Optimize and Compress Images:** While the image files themselves don't count toward the HTML limit, the code used to embed them absolutely does. Use descriptive but concise file names and alt text.\n    \n-   **Keep Your Code Clean:** Before you send, strip out any unnecessary comments, white space, and nested tables from your final HTML. A lot of email builders add extra junk code that can be safely removed.\n    \n\nKeeping these tips in mind will help ensure your entire message is always visible. For a much deeper dive, check out our complete guide on [how to create clean HTML emails](https://smashsend.com/blog/create-html-email) that always render perfectly.\n\n## Common Questions About Email Attachments\n\nYou've got questions, we've got answers. Here are some of the most common things we hear from marketers and developers trying to navigate the tricky world of email attachments.\n\nReady to stop worrying about attachment limits and start focusing on deliverability? **SMASHSEND** gives you the tools to create lightweight, link-based emails that always get delivered. [See how SMASHSEND can help your SaaS grow](https://smashsend.com/).\n\n## 🎯 Key Takeaways\n\n-   Email attachment size limits aren't just about the file—they include the entire message including headers, body text, and encoding overhead\n    \n-   Base64 encoding increases file size by 33-37%, meaning a 20MB file becomes ~27MB in transit\n    \n-   Most email providers have a 25MB total message limit, but the safe sendable size is closer to 18MB\n    \n-   Bounced emails from oversized attachments damage your sender reputation and can affect future deliverability\n    \n-   Cloud storage links are more secure, reliable, and professional than email attachments for sharing large files\n    \n-   Gmail's 102KB HTML limit can clip your emails, hiding critical content and breaking tracking pixels\n    \n\n## Frequently Asked Questions\n\nWhat's the absolute max file size I can safely email?\n\nThere's no single magic number, because the final gatekeeper is always the recipient's email server. But if you want the highest possible chance of your email landing safely in their inbox, keep attachments under 10 MB. That's the unofficial gold standard. Anything larger than that, and you're rolling the dice. Using a secure cloud link is the modern, bulletproof way to guarantee delivery for bigger files.\n\nCan I just zip a file to make it small enough?\n\nSometimes, but it's not a reliable fix. Zipping works wonders on text-based files, but it barely makes a dent in formats that are already compressed, like JPEGs or MP4s. You won't see much of a change. The bigger issue? Many corporate firewalls and security systems are configured to automatically block .zip files on sight, flagging them as potential security risks. So, you might solve the size problem only to create a brand-new deliverability one. A hosted link sidesteps this problem entirely.\n\nHow does attachment size impact my sender reputation?\n\nThink of it this way: every time you send an email with an attachment that's too big, it bounces. Internet Service Providers (ISPs) see those bounces as a huge red flag. If it happens consistently, your sender reputation takes a direct hit. This tells ISPs that you might not be following best practices, making it much more likely that all your future emails—even the ones without attachments—get sent straight to the spam folder.\n\nAre cloud links actually more secure than attachments?\n\nIn almost every scenario, yes. When you use a cloud storage platform, you get a whole suite of security controls that attachments just don't have. You can add password protection, set specific access permissions, and even make links expire after a certain date. It gives you total control over who sees your sensitive documents and for how long. Once you send an attachment, it's out of your hands. It can be downloaded, saved, and forwarded to anyone, forever, without you ever knowing.","storage":{"htmlKey":"stealpage/html/smashsend.com/pg_4syj632arx8c/run_24xqxhe34ket.html.gz","markdownKey":"stealpage/md/smashsend.com/pg_4syj632arx8c/run_24xqxhe34ket.md.gz"},"facets":null,"assets":[{"kind":"image","src_url":"https://smashsend.com/blogs/email-attachment-size-limit/og-image.jpg","r2_key":null,"alt":null,"caption":null,"width":null,"height":null,"is_hero":true,"zone":"main"},{"kind":"image","src_url":"https://smashsend.com/_next/static/media/smashsend_dark.da05b6ec.svg","r2_key":null,"alt":"SMASHSEND email marketing - The #1 Email Marketing Tool that turns emails into revenue","caption":null,"width":135,"height":30,"is_hero":false,"zone":"unknown"},{"kind":"image","src_url":"https://smashsend.com/dashboard/integrations/zapier_icon_filled.png","r2_key":null,"alt":"Zapier","caption":null,"width":20,"height":20,"is_hero":false,"zone":"nav"},{"kind":"image","src_url":"https://smashsend.com/dashboard/integrations/mailchimp_icon.png","r2_key":null,"alt":"Mailchimp","caption":null,"width":20,"height":20,"is_hero":false,"zone":"nav"},{"kind":"image","src_url":"https://smashsend.com/dashboard/integrations/webhooks_icon_gradient.png","r2_key":null,"alt":"Webhooks","caption":null,"width":20,"height":20,"is_hero":false,"zone":"nav"},{"kind":"image","src_url":"https://smashsend.com/dashboard/integrations/events.png","r2_key":null,"alt":"Events API","caption":null,"width":20,"height":20,"is_hero":false,"zone":"nav"},{"kind":"image","src_url":"https://smashsend.com/_next/image?q=75&url=%2Favatar-profile.png&w=3840","r2_key":null,"alt":"Jorge Ferreiro","caption":null,"width":null,"height":null,"is_hero":false,"zone":"nav"},{"kind":"image","src_url":"https://smashsend.com/_next/image?url=%2Favatar-profile.png&w=3840&q=75","r2_key":null,"alt":"Jorge Ferreiro","caption":null,"width":null,"height":null,"is_hero":false,"zone":"nav"},{"kind":"image","src_url":"https://smashsend.com/blogs/email-attachment-size-limit/email-attachment-size-limit-attachment-evolution.jpg","r2_key":null,"alt":"Diagram showing the evolution of email attachment sizes from <1MB in the 1990s to 25MB today.","caption":null,"width":null,"height":null,"is_hero":false,"zone":"unknown"},{"kind":"image","src_url":"https://smashsend.com/blogs/email-attachment-size-limit/email-attachment-size-limit-data-transfer.jpg","r2_key":null,"alt":"Diagram illustrating data transfer: a box labeled 'attachment' sends a 'cloud link' to a paper airplane labeled 'zip', flying towards a cloud with a gear.","caption":null,"width":null,"height":null,"is_hero":false,"zone":"unknown"},{"kind":"image","src_url":"https://smashsend.com/blogs/email-attachment-size-limit/email-attachment-size-limit-clipped-email.jpg","r2_key":null,"alt":"A sketch illustrating an email message clipped due to a 102 KB size limit, partially visible within an envelope.","caption":null,"width":null,"height":null,"is_hero":false,"zone":"unknown"},{"kind":"image","src_url":"https://smashsend.com/_next/image?q=75&url=%2F_next%2Fstatic%2Fmedia%2Fsmashsend_favicon.24650314.png&w=256","r2_key":null,"alt":"","caption":null,"width":80,"height":80,"is_hero":false,"zone":"footer"},{"kind":"image","src_url":"https://smashsend.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fsmashsend_favicon.24650314.png&w=256&q=75","r2_key":null,"alt":"","caption":null,"width":80,"height":80,"is_hero":false,"zone":"footer"},{"kind":"image","src_url":"https://smashsend.com/_next/static/media/smashsend_light.be8a3849.svg","r2_key":null,"alt":"SMASHSEND email marketing - The #1 Email Marketing Tool that turns emails into revenue","caption":null,"width":171,"height":38,"is_hero":false,"zone":"footer"},{"kind":"image","src_url":"https://smashsend.com/marketing/legal/gdpr_compliance.png","r2_key":null,"alt":"SOC2","caption":null,"width":null,"height":50,"is_hero":false,"zone":"footer"}],"shots":[],"history":[{"id":"run_24xqxhe34ket","started_at":"2026-09-27T04:11:00.861Z","http_status":200,"fetcher":"direct","changed":false,"diff":{"added":0,"removed":119,"similarity":null},"word_count":3479},{"id":"run_3-3j_vp_1frb","started_at":"2026-08-28T03:17:19.108Z","http_status":200,"fetcher":"direct","changed":false,"diff":null,"word_count":3598}],"citedBy":[]}