Website profiles · Technology insights · Alternatives

tinywebgallery.com No paid content found

Categories: Artificial Intelligence

TinyWebGallery is a free image gallery /php web photo gallery /web gallery that is very easy to install, extremely user friendly with many unique features.

Visit website

Updated: 2026-10-02 05:58 Language: English (default) Access: Normal

Profile views 4 Outbound visits 0
TinyWebGallery Full homepage screenshot
Editorial Review

Website Review

What is TinyWebGallery?

TinyWebGallery is a free PHP photo gallery script for publishing image albums on a website you host yourself. It stores its album data in XML files rather than in a database, which makes it attractive when you want a gallery without setting up or maintaining MySQL.

What it does well

  • Installs by uploading files to your web space; no database server is required.
  • Manages albums and images through a browser-based interface rather than hand-editing code.
  • Fits personal portfolios, club or event photo archives, and small business galleries where a full CMS would be overkill.
  • Works alongside the same developer's WordPress plugin, Advanced iFrame, if you want to embed gallery pages inside a WordPress site.

Trade-offs to weigh

  • XML storage is simple but less suited to very large collections or multi-user editing than a database-driven gallery.
  • You are responsible for hosting, backups and PHP version compatibility.
  • The site mixes two products, TinyWebGallery and Advanced iFrame, so check which documentation applies to your setup.

A practical next step: if you have PHP hosting and a folder of photos, download the TinyWebGallery package, install it in a subdirectory, and create one test album before migrating your full collection. Compare it with a hosted option such as Flickr if you would rather not manage server files.

How do I install TinyWebGallery without a database?

TinyWebGallery is designed for exactly that: it stores its gallery data in XML files rather than a database, so installation is mostly a matter of copying files and setting folder permissions. You do not need MySQL, PostgreSQL or any database setup step.

What the install actually involves

  1. Check your hosting. You need PHP hosting with a normal web directory. Because there is no database, even basic shared hosting or a small personal server is enough.
  2. Upload the gallery files. Unzip the TinyWebGallery package and upload the folder to your web space, typically via FTP or your host's file manager.
  3. Set write permissions. The gallery needs to write XML files and thumbnails, so the relevant folders must be writable by the web server. This is the step people most often get wrong.
  4. Run the setup in your browser. Open the gallery URL and follow the built-in configuration, where you choose gallery folders, language and appearance.
  5. Add images. Put your photos in the gallery folder (or upload them through the admin area) and let TinyWebGallery generate the XML index and thumbnails.

The official site is TinyWebGallery, where the download and documentation live.

Why the no-database approach matters

The trade-off is simple. You gain portability and simplicity: the whole gallery can be backed up by copying files, moved to another host without exporting SQL, and run on cheap hosting. You give up the querying and scaling that a database provides, so very large collections with heavy traffic may feel slower, and any multi-user or dynamic features are limited.

Practical next step

Before uploading, create a test folder such as /gallery-test/ and install there first. If thumbnails generate and images appear, move it to its final location. For permissions, a common approach is setting the gallery data and thumbnail folders to 755 first, and only widening to 775 or 777 if your host requires it. If you already run WordPress and mainly need to embed external content rather than host a gallery, the same site also covers Advanced iFrame, which is a different tool for a different job.

How does TinyWebGallery compare to other PHP photo galleries for a small personal website?

For a small personal site, TinyWebGallery's main advantage is that it stores gallery data in XML files rather than requiring a database. On shared hosting or a minimal LAMP setup, that removes one setup step and one thing that can break during backups or migrations. The trade-off is scale and workflow: XML files are fine for hundreds of photos, but they are not the right tool if you expect thousands of images, multi-user uploads, or heavy tagging and search.

Where it fits

  • You have FTP/SSH access and can drop a PHP gallery into a folder.
  • You want a self-hosted gallery without MySQL.
  • You prefer a simple file-based structure you can copy or archive.
  • You do not need a CMS-style admin with user roles and a database.

Where a database-backed gallery wins

  • Large libraries where queries, pagination and search matter.
  • Multiple contributors uploading and editing.
  • Integration with an existing CMS or e-commerce system.

A practical comparison for a personal site:

Need TinyWebGallery approach Typical database-backed PHP gallery
Setup Copy files, no DB Create DB, run installer
Backup Copy folders/XML Dump database plus files
Very large libraries Less comfortable Built for it
Multi-user editing Not the focus Common feature
Portability High Depends on DB export

If you already run WordPress, the same site also points to Advanced iFrame, which may be more relevant if your goal is embedding external content rather than managing a standalone gallery. For a pure photo gallery on a small site, the no-database design is the deciding factor: choose TinyWebGallery when simplicity and portability matter more than scale and multi-user workflows. A reasonable next step is to install it in a subfolder, add 20–30 representative photos, and test load time and mobile layout before committing your main gallery to it. If that test feels slow or awkward to update, a database-backed option such as Piwigo or a CMS-integrated gallery will likely serve you better.

Can I embed TinyWebGallery images into a WordPress site using Advanced iFrame?

Yes, you can embed TinyWebGallery into WordPress using Advanced iFrame, but it works differently from a native WordPress gallery block. Advanced iFrame embeds an external page inside a WordPress page via an iframe, so the TinyWebGallery installation itself runs on its own PHP host and appears inside a framed window on your site.

How the two parts fit together

  • TinyWebGallery is a free PHP photo gallery that stores data in XML files rather than a database, as described on TinyWebGallery. That makes it simple to drop onto basic shared hosting, but it is a separate application, not a WordPress plugin.
  • Advanced iFrame is the WordPress plugin from the same site that handles the embedding. The site presents it as its iframe plugin for WordPress, with examples for common scenarios.
  • The practical result: visitors browse your WordPress site and see the gallery inside a page, while the gallery's own files and XML data live on the other host.

When this makes sense

A photographer who already runs TinyWebGallery on cheap hosting and wants to keep that setup while gaining a WordPress front end is the clearest case. It also suits anyone who wants one gallery reused across multiple sites. The trade-off is that you are maintaining two systems and two hosting environments, and iframe content can behave awkwardly on mobile or with browser security restrictions.

A simpler alternative to weigh

If the gallery is the main point of the site, a native WordPress gallery plugin keeps images in the media library, where themes, search and SEO tools can reach them. If you only need to display a handful of images, that route is usually less work than running TinyWebGallery plus an iframe wrapper.

Next step

Install TinyWebGallery on its own host first and confirm the gallery URLs load correctly on their own. Then install Advanced iFrame, create a page, and embed that gallery URL. Test on a phone and check whether the iframe resizes as expected before committing to the approach.

How do I upgrade TinyWebGallery or Advanced iFrame to the latest version?

Upgrade TinyWebGallery and Advanced iFrame separately, because they ship on different release tracks. The site's own news notes that Advanced iFrame had breaking changes in version 2025.2 (the iframe fullscreen button and the Freemius migration, plus the external workaround using ai_external.js), and that Advanced iFrame is now distributed through Freemius and CodeCanyon. That means the safest upgrade path depends on which platform your license came from.

TinyWebGallery (TWG)

TWG is the free PHP gallery that stores its data in XML files instead of a database. The site lists TWG 2.8 as a download, so upgrading means replacing the program files with the newer package while keeping your gallery data and configuration.

Practical steps:

  • Back up the whole TWG folder, especially your albums, XML files and any custom templates or theme files.
  • Download the current TWG package from TinyWebGallery.
  • Replace the core program files, but leave your content folders and config in place.
  • Open the gallery in a browser and check that albums, thumbnails and captions still render.
  • If you had edited core files directly, re-apply those edits to the new versions rather than overwriting them.

Because there is no database, rollback is simple: restore the folder you backed up.

Advanced iFrame

Advanced iFrame is the WordPress iframe plugin from the same developer, offered in free and pro versions. The upgrade route differs by edition.

Edition Where it came from How to update
Free WordPress plugin directory Use the normal WordPress update on the Plugins screen
Pro via Freemius Freemius licence Automatic updates through WordPress once the licence is connected
Pro via CodeCanyon CodeCanyon purchase Download the new package and install it manually

Before updating a pro copy, check whether you rely on either feature flagged in the 2025.2 breaking-change notice: the iframe fullscreen button, or the external workaround that uses ai_external.js. If you do, follow the migration notes rather than updating blind.

A sensible order for a live WordPress site: take a full site backup, update on a staging copy first, confirm your iframes still load and resize correctly, then repeat on production.

A concrete scenario

If you run a small photography portfolio, your TWG gallery might hold a few hundred images in XML-backed albums, while a WordPress page embeds it through Advanced iFrame. In that setup, upgrade Advanced iFrame first on staging, verify the embedded gallery still displays at the right size, then update TWG's files and re-check the albums. Doing both at once makes it hard to tell which change broke the layout.

For exact version numbers, changelogs and the breaking-change instructions, the news and download sections on TinyWebGallery are the authoritative source.

Is TinyWebGallery free to use, and what paid options exist for Advanced iFrame?

TinyWebGallery is the free half of this site's offering; Advanced iFrame is the commercial one, sold in free and pro editions.

TinyWebGallery (TWG) is described as a free web gallery / PHP photo album. It is easy to install, needs no database (it stores its data in XML files), and still includes the features you would expect from a web gallery plus extras. The download page lists a TWG 2.8 build dated 09.03.2026, so the free gallery is still being maintained rather than abandoned.

Advanced iFrame is an iframe plugin for WordPress, offered in free and pro versions. The page names three purchase routes for the pro edition: Freemius, CodeCanyon, and the site's own register/buy page. Freemius brings automatic WordPress-style updates, monthly/yearly/lifetime plan options, and multi-site licensing tiers described as personal, business (5 sites) and agency (50 sites). The pro build is versioned 2025.2 / 2026.1 depending on where you look on the page.

TinyWebGallery Advanced iFrame
Cost Free Free version plus paid Pro
What it does Standalone PHP photo gallery, XML storage, no database Embeds external content in WordPress via iframes
Buying route Direct download Freemius, CodeCanyon, or site checkout
Main trade-off You host and manage the files yourself Pro cost and licence tier depend on site count

A practical note on the 2025.2 Pro release: the developer flagged two breaking changes — the fullscreen button on iframes and the migration to Freemius affecting the external workaround using ai_external.js. If you already run an older Pro version and rely on either, read the upgrade notes before updating.

Which one you want depends on your job. If you need a self-contained image gallery on ordinary PHP hosting, TWG costs nothing and avoids database setup. If your goal is pulling external pages or tools into a WordPress layout, that is Advanced iFrame's territory, and the Pro licence only makes sense once you need the paid features across a known number of sites.

Next step: check the download page for the current TWG build and the Advanced iFrame version notes, then pick the licence tier that matches how many WordPress sites you actually run.

Related questions

More questions →
How to Upload Videos to Netu.tv: Desktop, Remote URL, and FTP Methods

You can upload to Netu.tv three ways: directly from your desktop, by pasting remote URLs (up to 50 at a time), or over FTP. You don't need an account to start an upload, but you do need to register or log in to manage your videos afterward. Before you begin, check the limits: each video can be no more than 8096 MB and no longer than 500 minutes, and the service recommends mp4 with H.264 (720p, 1500 kb/s) and AAC audio (44100 Hz / 128 kbps).

Before you upload: limits and recommended format

Constraint Value
Max file size 8096 MB
Max duration 500 minutes
Recommended video codec H.264, 720p, 1500 kb/s
Recommended container mp4
Recommended audio AAC, 44100 Hz, 128 kbps
Formats "a variety of formats" (mp4/H.264 recommended)

If your file is larger or longer than these limits, re-encode or split it before uploading — the upload will not accept it as-is. Matching the recommended encoding also reduces the chance of playback problems later.

Method 1: Desktop upload

  1. Open the upload page. You can do this while logged out — the page shows "Select videos (you are not logged in)."
  2. Select your video file(s). The page supports uploading multiple files at once.
  3. Click Start upload. You can cancel with Cancel upload or clear the queue with Delete.
  4. To manage the videos afterward (rename, organize, track status), register or log in.

Expected result: the file enters the upload queue and, once finished, becomes available to share. If you stay logged out, you can still upload and share, but you lose the management tools.

Method 2: Remote URL upload (beta)

This method pulls a video from a link you already host elsewhere, instead of pushing it from your machine.

  1. Paste your URLs into the URL field. You can add up to 50 URLs.
  2. To set a title, append ###title to the end of the link — for example, https://example.com/video.mp4###My Title.
  3. Click Add to upload queue.
  4. Watch the queue table, which tracks File name, URL, Created, Status, File-Code, and Adult?. Use Update list to refresh and Delete Selected From Queue to remove entries.

Expected result: each URL appears as a row with a status you can monitor. This is labeled beta, so expect occasional hiccups on large batches.

Method 3: FTP upload

FTP upload is listed alongside the other two methods on the upload page. It's the practical choice when you're moving many or very large files and don't want to keep a browser tab open. The page confirms FTP is supported but doesn't publish the server credentials here — get those from your account area after logging in.

Common failures and how to fix them

Old videos stop loading after you switch your site to HTTPS. Some older videos may still be requested over HTTP. The page's fix is to add the appropriate reference so those HTTP links resolve — if you don't have HTTP links, you can close that notice.

Videos deleted by robots. If automated crawlers are removing your videos, load the iframe src only after a captcha challenge. You can also put a captcha in front of videos or enable Cloudflare's "I'm under attack!" option to block bot access.

Domain or subdomain blocked on some ISPs. Rotate your domain/subdomain over time, using 301 redirects, so a blocked domain doesn't take your whole library down.

Popunder firing on blank areas. If you use popunder ads, they should fire only when a user clicks an element, not on the blank body — the page links a script for this.

After upload: sharing and webmaster tips

Once a video is processed, share it with friends using its link, or embed the player on your site. If you're monetizing, the page's webmaster tips are worth applying:

  • Place the Netu.tv player above other players to get more money.
  • Write unique descriptions for each video — the page notes this drives search-engine traffic.
  • Use PageSpeed Insights to check load speed, since faster sites get more traffic from Google.

Quick method comparison

Method Best for Key limit / note
Desktop One or a few files, quick share Multiple files supported; no login required to upload
Remote URL Videos already hosted elsewhere Up to 50 URLs; ###title for titles; beta
FTP Bulk or very large transfers Credentials from your account; keeps browser free

If you just want a shareable link fast, use desktop upload. If your files already live on a server, remote URL saves re-uploading. If you're moving a library, FTP is the least babysitting.

Website Overview

Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks. An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2006, this domain has about 20 years of history. That suggests continuity, although ownership and purpose may have changed. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

The observed email authentication setup is incomplete: SPF is missing. Nameservers are provided by rzone.de, indicating managed DNS hosting. MX records point to the rzone.de email service. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed. The lowest observed DNS TTL is 150 seconds.

TLS and Certificates

The certificate issuer is Sectigo Limited, a commercial certificate authority. The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate is valid for about 386 days in total, with 54 days remaining.

HTTP and Browser Security

The Server header exposes the software version: Apache/2.4.68 (Unix). This makes version-targeted checks easier, but is not proof of an exploitable vulnerability. X-Powered-By exposes backend information: PHP/8.3.35. The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. No obvious internal addresses or debug information were found in the headers. Cookie security attributes are unknown.

Technology Stack Analysis

The public page identifies Apache 2.4.68, PHP, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability.

Search and Social Sharing

The title has 69 characters and may be truncated in search results. No Open Graph metadata was detected, so social previews may depend on platform inference. A meta description is present, with 155 characters. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed.

Hosting and Email

DNSrzone.de
Hostingtinywebgallery.com
Emailrzone.de
Location Germany flagGermany 81.169.145.79

User reviews (0)

  • No reviews yet.

Pages, Search and Sharing

Meta descriptionTinyWebGallery is a free image gallery /php web photo gallery /web gallery that is very easy to install, extremely user friendly with many unique features.
Canonical URLhttp://www.tinywebgallery.com
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 21 disallowed
  • Disallow/counter/
  • Disallow/download/
  • Disallow/download/plesk-stat/
  • Disallow/test/
  • Disallow/png/
  • Disallow/stat/
  • Disallow/demo/admin/
  • Disallow/demo2/admin/
  • Disallow/demo3/admin/
  • Disallow/demo/i_frames/
  • Disallow/demo2/i_frames/
  • Disallow/demo3/i_frames/
  • Disallow/demo/html/
  • Disallow/demo2/html/
  • Disallow/demo3/html/
  • Disallow/demo/index.php/*
  • Disallow/demo2/index.php/*
  • Disallow/demo3/index.php/*
  • Disallow/forum/profile.php
  • Disallow/de/faq.htm
  • Disallow/en/faq.htm
googlebot-image 0 allowed · 21 disallowed
  • Disallow/counter/
  • Disallow/download/
  • Disallow/download/plesk-stat/
  • Disallow/test/
  • Disallow/png/
  • Disallow/stat/
  • Disallow/demo/admin/
  • Disallow/demo2/admin/
  • Disallow/demo3/admin/
  • Disallow/demo/i_frames/
  • Disallow/demo2/i_frames/
  • Disallow/demo3/i_frames/
  • Disallow/demo/html/
  • Disallow/demo2/html/
  • Disallow/demo3/html/
  • Disallow/demo/index.php/*
  • Disallow/demo2/index.php/*
  • Disallow/demo3/index.php/*
  • Disallow/forum/profile.php
  • Disallow/de/faq.htm
  • Disallow/en/faq.htm

No sitemaps found

Registration details RDAP / WHOIS

RegistrarCronon GmbH
Registered2006-02-09
Expires2027-02-09
Domain statusactive
Nameserversdocks02.rzone.de、shades17.rzone.de
DNSSECunsigned

DNS records

TypeNameValueTTLPriority
Atinywebgallery.com81.169.145.79150—
AAAAtinywebgallery.com2a01:238:20a:202:1079::150—
MXtinywebgallery.comsmtpin.rzone.de1505
NStinywebgallery.comdocks02.rzone.de150—
NStinywebgallery.comshades17.rzone.de150—
CNAMEwww.tinywebgallery.comtinywebgallery.com150—
DMARC_dmarc.tinywebgallery.comv=DMARC1;p=reject;150—

TLS and certificates

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwww.tinywebgallery.com
IssuerSectigo Limited
Valid until2026-11-25T23:59 · Remaining when checked: 54 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HeaderValue
content-typetext/html; charset=utf-8
cache-controlmust-revalidate
serverApache/2.4.68 (Unix)
set-cookieRedacted

Identified technologies

Apache 2.4.68PHP