DEV Community: Dev Std

How I Built a Multilingual Instagram Downloader with Pure PHP (No Framework)

Dev Std — Sat, 10 Oct 2026 10:28:12 +0000

Most developers reach for Laravel or Symfony when starting a PHP project. I went the opposite direction I built iGram.pk, a free Instagram downloader that supports 16 languages, using nothing but vanilla PHP, .htaccess routing, and a clean file structure.

Here's what I learned and how I structured it.

Why No Framework?

For a tool like this, a full framework is overkill. The app does one thing: accept an Instagram URL, fetch the media, and serve it for download. I needed:

Fast page loads (no framework overhead)
Clean SEO-friendly URLs
Multi-language support without bloated i18n libraries
Easy deployment on shared hosting or Heroku

Vanilla PHP gave me all of this with a tiny footprint.

The Routing Layer

Instead of a framework router, I used a single index.php as the entry point with .htaccess rewrites:


apache
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]

Then in index.php, I parse the URI and route to the right page:

$uri = trim(parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH), '/');
$segments = explode('/', $uri);

// Check if first segment is a language code
$supportedLangs = ['ar', 'bn', 'de', 'es', 'fr', 'id', 
                   'it', 'ja', 'ko', 'pl', 'pt', 'ru', 
                   'th', 'tr', 'vi'];

$lang = 'en';
if (in_array($segments[0], $supportedLangs)) {
    $lang = array_shift($segments);
}

$page = implode('/', $segments) ?: 'home';

No regex libraries. No route definitions file. Just array lookups and string parsing. It handles 260+ URLs with zero dependencies.

Multi-Language Without i18n Libraries

Each language gets a single PHP file that returns a nested array:

// includes/translations/ko.php
return [
    'common' => [
        'site_name' => 'iGram',
        'download_btn' => '다운로드',
        'paste_placeholder' => 'Instagram 링크를 여기에 붙여넣으세요',
        'how_to_title' => '다운로드 방법',
    ],
    'story-saver' => [
        'title' => 'Instagram 스토리 세이버',
        'description' => '공개 Instagram 스토리를 다운로드하세요',
    ],
];

The loader merges common strings with page-specific ones:

function loadTranslations($lang, $slug = null) {
    if ($lang === 'en') return [];
    $file = __DIR__ . '/translations/' . $lang . '.php';
    if (!file_exists($file)) return [];
    $all = include $file;
    $common = $all['common'] ?? [];
    if ($slug === null) return $common;
    $page = $all[$slug] ?? [];
    return array_merge($common, $page);
}

function t($translations, $key, $fallback = '') {
    return $translations[$key] ?? $fallback;
}

The $fallback parameter is key — English pages just use the fallback strings directly, so there’s no English translation file at all. Less files, less maintenance.

SEO With Structured Data

Every tool page gets proper Schema.org JSON-LD without any library:

function schemaWebApplication($name, $path, $description, $lang = 'en') {
    return [
        '@context' => 'https://schema.org',
        '@type' => 'WebApplication',
        'name' => $name,
        'url' => 'https://igram.pk/' . ltrim($path, '/'),
        'description' => $description,
        'applicationCategory' => 'MultimediaApplication',
        'operatingSystem' => 'Any',
        'inLanguage' => $lang,
        'isAccessibleForFree' => true,
        'offers' => [
            '@type' => 'Offer', 
            'price' => '0', 
            'priceCurrency' => 'USD'
        ],
    ];
}

This plus proper hreflang tags for all 16 languages gives Google clear signals about what each page is and which language it targets.

Hreflang for 16 Languages

Each tool page outputs hreflang links for every language variant:

$languages = getSupportedLanguages(); // returns all 16 codes
foreach ($languages as $code) {
    $href = $code === 'en' ? "/$slug" : "/$code/$slug";
    echo '<link rel="alternate" hreflang="' . $code . '" 
          href="https://igram.pk' . $href . '"/>';
}
echo '<link rel="alternate" hreflang="x-default" 
      href="https://igram.pk/' . $slug . '"/>';

The sitemap mirrors this with xhtml:link entries — 260 URLs total, all with proper language annotations.

Deployment

The whole app runs on Heroku’s free tier with one line in the Procfile:

web: vendor/bin/heroku-php-apache2

No build step. No compilation. Push and it’s live.

Performance Results

Without a framework:

First Byte Time: ~120ms
Total page weight: ~45KB (including CSS and JS)
Lighthouse Performance: 95+
Zero npm dependencies
What I’d Do Differently
Use a simple template engine — I started with raw <?php echo everywhere. Even a 50-line template function would’ve saved time.
Add automated tests earlier — Vanilla PHP makes it easy to skip testing. Don’t.
Plan the translation structure upfront — Adding languages 3 at a time when you started with 13 means retrofitting every page template.
Try It

The tool is live at igram.pk. It supports downloading Instagram videos, Reels, photos, carousel posts, Stories, Highlights, and profile pictures — all free, no login required.

If you’re building a simple web tool, consider whether you actually need that framework. Sometimes plain PHP is the fastest path to production.

[Boost]

Dev Std — Sat, 10 Oct 2026 00:57:40 +0000

Dev Std

Oct 9

Building a Multi-Language Instagram Downloader with PHP - No

#php #webdev #seo #opensource

4 min read

Building a Multi-Language Instagram Downloader with PHP - No

Dev Std — Fri, 09 Oct 2026 08:37:09 +0000

I recently built iGram.pk, an Instagram downloader that supports 13 languages, serves 9 dedicated tool pages, and runs on a single index.php front controller with zero framework dependencies. Here's what I learned about routing, i18n, SEO, and shipping fast without Laravel or Symfony.

Why No Framework?

The project needed to be:

Fast to load - every millisecond counts for a tool people use on mobile
Cheap to host- Heroku free/basic tier with Apache
Simple to deploy - git push and done

A framework would add 20-50MB of vendor code, boot time overhead, and complexity that a tool site doesn't need. The entire codebase fits in a handful of files.

The Routing Problem

With 9 tool pages, 13 languages, 40+ blog posts, and static pages (about, contact, FAQ, legal), I needed clean URLs like:

/download-instagram-reels        (English)
/ar/download-instagram-reels     (Arabic)
/fr/story-saver                  (French)
/blog                            (Blog index)
/how-to-download-instagram-videos (Blog post)

The solution is a single index.php that acts as a front controller. Apache's .htaccess sends everything there:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /index.php [L,QSA]

Then index.php parses the URI, extracts the language prefix (if any), and routes to the correct PHP file:

$requestUri = parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH);
$requestUri = rawurldecode($requestUri);
$slug = ltrim($requestUri, '/');

// Extract language prefix
$languages = ['ar', 'de', 'es', 'fr', 'id', 'it', 'ja', 'pl', 'pt', 'ru', 'tr', 'vi'];
$currentLang = 'en';

foreach ($languages as $l) {
    if (strpos($slug, $l . '/') === 0) {
        $currentLang = $l;
        $slug = substr($slug, strlen($l) + 1);
        break;
    }
}

// Route to the right file
$toolPages = ['story-saver', 'downloadgram', 'download-instagram-reels', ...];
if (in_array($slug, $toolPages)) {
    include __DIR__ . '/pages/tools/' . $slug . '.php';
    exit;
}

No regex router library, no route registration — just an array lookup. It handles hundreds of URL combinations with zero overhead.

Multi-Language Without a Framework

The i18n system is file-based. Each language gets a PHP file that returns an associative array:

// includes/translations/ar.php
return [
    'common' => [
        'download' => 'تحميل',
        'paste_link' => 'الصق رابط Instagram هنا',
        'video_downloader' => 'تحميل فيديو',
        // ...
    ],
    'story-saver' => [
        'title' => 'حفظ ستوري انستقرام - تحميل القصص | iGram.pk',
        'description' => '...',
        'steps' => ['...', '...', '...'],
    ],
];

The loader merges common translations with page-specific ones:

function loadTranslations($lang, $slug = null) {
    if ($lang === 'en') return [];
    $all = include __DIR__ . '/translations/' . $lang . '.php';
    $common = $all['common'] ?? [];
    $page = $all[$slug] ?? [];
    return array_merge($common, $page);
}

English is the default — if a translation key is missing, the template falls back to the hardcoded English string using the null coalescing operator:

$pageTitle = $t['title'] ?? 'Instagram Story Saver - Download Stories | iGram.pk';

This approach is simple, fast (no database queries), and easy to extend. Adding a new language is literally creating one PHP file.

SEO Architecture

For a content site competing in search, SEO structure matters as much as content quality. Here's what I implemented:

Structured Data (Schema.org)

Every page type gets appropriate JSON-LD markup through helper functions:

function schemaArticle($headline, $description, $path, $published, $modified) {
    return [
        '@context' => 'https://schema.org',
        '@type' => 'Article',
        'headline' => $headline,
        'description' => $description,
        'datePublished' => $published,
        'dateModified' => $modified,
        'author' => ['@type' => 'Organization', 'name' => 'iGram.pk'],
        // ...
    ];
}

Tool pages use WebApplication schema, blog posts use Article, FAQ sections use FAQPage. Each schema type is a function that takes the page's actual data, so the markup always matches the visible content.

Hreflang for Multi-Language

Each tool page generates hreflang tags for all 13 language variants:

foreach (getSupportedLanguages() as $l) {
    $hreflangPages[$l] = ltrim(langUrl($l, $slug), '/');
}

This tells Google which version to show French users vs Arabic users vs English users. Without hreflang, Google might index the wrong language variant for a given region.

Blog Posts Are English-Only

Blog content is only in English. If someone hits /fr/how-to-download-instagram-videos, the router 301 redirects to the English version. This avoids thin translated content and keeps the canonical clear.

if ($currentLang !== 'en') {
    header('Location: /' . $blogSlug, true, 301);
    exit;
}

AI Search Optimization

With ChatGPT, Perplexity, and Google AI Overviews reshaping how people find tools, I added signals that AI crawlers specifically look for:

llms.txt

This is a structured file at the site root that tells AI crawlers what the site is about:

# iGram.pk
> iGram.pk is a free, web-based Instagram downloader...

## Tools
- [Video Downloader](https://igram.pk/download-instagram-video): download videos in HD
- [Story Saver](https://igram.pk/story-saver): save Stories before expiry
...

robots.txt AI Bot Permissions

Explicitly allowing AI crawler bots:

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

Many sites block these bots. Allowing them increases the chance your tool gets recommended in AI-generated answers.

Performance on Heroku

The entire app runs on Heroku's basic tier with Apache:

web: vendor/bin/heroku-php-apache2

With Cloudflare in front for caching and SSL, the setup handles the traffic without issues. PHP's built-in opcache handles the rest — no Redis, no Memcached, no queue workers.

Total infrastructure cost: basically free.

What I'd Do Differently

Start with more tool pages — dedicated pages for each content type (video, Reels, photos, carousel, Stories, Highlights, profile photos) rank independently in search. I should have built all 9 from day one instead of starting with 3.
Schema markup from the beginning — I added FAQPage and Article schema later. Having it from launch would have earned rich snippets sooner.
Content velocity matters — writing 40+ blog posts in the first two weeks had a measurable impact on organic traffic. Each post is a new entry point from search.

Results

Within the first week:

1,500+ daily clicks from organic search
143,000+ impressions for branded queries
Ranking on page 1 for multiple "igram" keyword variations
9 tool pages, 43 blog posts, 13 language variants

The site is at igram.pk if you want to see the implementation live. The blog has all 43 guides and tutorials.

Takeaways

You don't need a framework for a tool site. Plain PHP with a front controller is fast, simple, and deployable anywhere.
Multi-language support with file-based translations is underrated. It's faster than database lookups and easier to maintain than JSON files.
SEO is architecture, not just content. Clean URLs, hreflang, structured data, and proper canonicalization compound over time.
Ship fast, iterate based on search console data. GSC shows you exactly what people search for — write content that matches those queries.

Built with PHP, deployed on Heroku, cached with Cloudflare. No framework, no build step, no node_modules.