3 Best APIs for CDN Delivery in Nigeria

The Image Thumbnails Generator API is a REST API service for programmatically creating resized thumbnail images from source images specified by URL. It enables developers to generate thumbnails at any dimension without requiring server-side image processing libraries like ImageMagick or GD, removing a common infrastructure dependency from web and mobile application backends. The core workflow is straightforward: provide the URL of a source image along with desired output dimensions (width, height), specify a crop mode if needed, and the API returns a URL pointing to the generated thumbnail hosted on a CDN. This on-demand generation model means developers do not need to pre-generate thumbnails at every possible size — they can request any dimension at runtime and receive a cached URL for subsequent requests. The API supports multiple crop modes to handle aspect ratio differences between source images and target dimensions. Cover mode fills the entire output frame by cropping the source image, which is ideal for profile photos and product images where uniform dimensions are critical. Contain mode letterboxes the image to fit within the target dimensions without cropping, preserving the full image. Fill mode stretches the image to exactly match the target, which is appropriate when aspect ratio distortion is acceptable. Quality control parameters allow developers to specify the output quality level for JPEG outputs, trading file size against visual fidelity. For performance-critical applications, lower quality settings produce smaller files that load faster over mobile connections, while high-quality settings preserve visual fidelity for print or display contexts. Output format options include JPEG (lossy, smallest file size), PNG (lossless, supports transparency), and WebP (modern format with superior compression). Nigerian developers building for mobile-first audiences benefit from WebP output, which delivers significantly smaller files than JPEG at equivalent visual quality — reducing data consumption for Nigerian users on metered mobile connections. For Nigerian e-commerce platforms, the need to display product images at multiple sizes across different contexts (product listings, detail pages, cart thumbnails, social sharing cards) is universal. Manually creating and storing all these variants for every product image requires substantial storage and pre-processing effort. With this API, the application simply stores the original high-resolution image and requests appropriately sized thumbnails for each context at render time, with the CDN caching results for performance. Nigerian media platforms and news portals that display article featured images in multiple contexts (homepage hero, article list thumbnails, related article widgets) can similarly benefit from on-demand thumbnail generation. The API enables a single source image to serve all display contexts without pre-generation overhead. The freemium pricing model makes this API accessible to Nigerian developers at all stages. The free tier provides 100 thumbnail generations per month, sufficient for prototyping and small personal projects. Paid tiers starting at $5/month scale to thousands of generations, appropriate for production applications with real user traffic. Integration requires an API key from the dashboard, which is passed as a query parameter or header with each request. The REST interface is compatible with any programming language or framework and requires no special client libraries. Image Thumbnails Generator API's output can be directly referenced by URL in HTML img tags and CSS background-image properties, making it trivial to integrate generated thumbnails into any Nigerian web or mobile application frontend without additional file handling or CDN configuration on the developer's side.

Supabase Storage is the file storage service embedded within the Supabase open-source backend platform, providing object storage with database-integrated access control and built-in image transformation capabilities. Unlike standalone cloud storage services, Supabase Storage is deeply connected to the Supabase PostgreSQL database and authentication system, enabling access control policies that reference the same user identities and database data as the rest of the application without separate permission management infrastructure. The storage data model in Supabase uses buckets as top-level containers and objects as individual stored files within those buckets. Buckets can be configured as public (all objects are publicly accessible via URL) or private (access requires authentication and policy authorization). This per-bucket visibility setting covers the default access model, while Row Level Security (RLS) policies on the storage schema tables provide fine-grained per-object and per-path access control for private buckets. Row Level Security integration is the defining technical characteristic of Supabase Storage's access control model. Rather than a separate permission system, Supabase Storage access is controlled by PostgreSQL RLS policies on the storage.objects table. This means access rules can reference any data in the PostgreSQL database — user roles, team memberships, subscription plans, content ownership — using the same SQL-based policy syntax used for all other RLS policies in a Supabase project. A single policy expression can restrict file access to the authenticated user who owns the file, members of a specific team, or users with specific subscription-granted permissions. The Supabase Storage API exposes standard REST endpoints for file operations: upload (single and multipart for large files), download, list objects within a bucket or path prefix, copy, move, and delete. Presigned URLs with configurable expiration times are supported for both uploads and downloads, enabling applications to generate time-limited direct-access URLs for private files. The JavaScript client library, available as part of the @supabase/supabase-js package, wraps these REST operations into a convenient SDK that handles authentication header injection automatically using the current session from Supabase Auth. Image transformation is built natively into Supabase Storage through the Transform API. Images stored in Supabase Storage can be resized, reformatted, and quality-adjusted by appending transform parameters to the image URL. A product image stored at its original resolution can be requested at a specified width and height, automatically cropped or scaled by Supabase Storage's transform service, without pre-generating multiple image variants at upload time. Format conversion to WebP for modern browsers is supported, reducing image payload size for Nigerian users on mobile data connections. Supabase Storage is backed by S3-compatible object storage, either Supabase's managed cloud infrastructure or a self-hosted MinIO or compatible storage backend when self-hosting Supabase. This architecture means that stored objects are durable and the Supabase Storage API layer handles authentication, policy evaluation, and transformation while the underlying storage provides the object persistence layer. For Nigerian developers building applications with Supabase as their backend, Storage is the natural file storage choice because it shares authentication state with Supabase Auth. When a user is signed in through Supabase Auth, the same JWT token that authorizes database queries also authorizes Storage operations — there is no separate file storage authentication flow to implement. This unified auth model significantly reduces the complexity of building file upload features into Supabase-backed applications. Common use cases for Nigerian Supabase projects include profile photo and avatar storage for social apps, document upload for KYC and verification workflows in fintech applications, media upload for content-sharing platforms, and attachment storage for productivity and communication tools. The combination of integrated auth, database-connected RLS policies, and image transformation makes Supabase Storage a complete file management solution that eliminates the need for integrating separate storage, CDN, and image processing services for most application needs.