LH.pl in Poland: pricing and restoring WordPress media

Who LH.pl may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Polish.

Control panel

Labels documented in Polish. Confirm other languages.

Support

Phone, chat and written support. Public documentation in Polish. Confirm English or French availability.

LH.pl in Poland for recovering a WordPress image

LH.pl markets WordPress hosting in Poland with an installer, daily backups and access to copies of files and the database. The provider maintains the platform and supplies installation and backup-access tools. The site owner manages plugins and updates, identifies the lost item, chooses the version to restore and checks the result.

The fictional community museum in Poznań publishes a temporary exhibition page. A photo has been deleted from storage while its media record, caption and association with the page still exist in WordPress. A volunteer has since corrected the opening time. The goal is to recover the image and the sizes needed for display while preserving this correction. The first observation distinguishes a missing file from a deleted media record. These incidents require different backup components.

The scenario leads to testing selective restoration on a local copy, then checking the image in the page’s current state. This profile examines hosting and AI builder costs over two periods, limits affecting exports and how to recover a site elsewhere. For the first decision, choose a plan covering the media library’s storage needs and arrange a separate location for the working copy.

Calculate the first year and renewal

On 10 November 2026, the WordPress page highlighted Mango at 37.50 PLN before tax for the first year and 399 PLN before tax for the renewal year. The ordering help also lists Orange at 50 then 199 PLN before tax, Kiwi at 60 then 249 PLN before tax and Apple at 100 then 599 PLN before tax. These are annual prices in Polish zlotys. Mango’s first year is displayed below the prices of the two smaller plans. For a two-year comparison, add the introductory year and first renewal. Excluding domains, options and taxes, this gives 249 PLN for Orange, 309 PLN for Kiwi, 436.50 PLN for Mango and 699 PLN for Apple at the recorded prices.

The recorded prices exclude VAT. As an example for local billing at the standard Polish rate of 23%, Mango represents approximately 46.13 PLN including VAT initially and 490.77 PLN including VAT at the first renewal, excluding options. The billed amount depends on the billing profile and items actually purchased. The guide states that a renewal pro forma invoice is issued for the next year, with a separate procedure for a longer renewal. Compare the same duration on both sides and note the due date shown on the pro forma invoice.

Treat the domain as a separate item. The extension price list shows, for example, .pl renewal at 129 PLN before tax. Registration prices marked promotional follow their own terms. The fictional museum can retain its registrar and ask the account owner to check the domain price, tax treatment, due date and status of the AI creation option. This last item can change renewal costs even when hosting remains on the same plan.

Choose capacity and understand LH.pl’s role

Orange, Kiwi, Mango and Apple list 5, 10, 30 and 100 GB respectively in the help pages and hosting range. The security documentation gives 10, 10, 15 and 20 simultaneous PHP processes, and 10, 20, 30 and 40 simultaneous database connections. Advertised memory increases from 1 to 4 GB. The table also distinguishes PHP script execution time from HTTP request duration. When regenerating many images, free space, process count and execution time matter as much as the size of the files being restored.

Mango lists SSH and Redis, a Let’s Encrypt certificate and an advertised unlimited traffic volume. These features do not remove the account’s technical limits. For the museum, measure the media folder, database size and mailboxes used, then reserve room for new image sizes. For a private copy, use a separate installation and verify its root directory, database and protection against visitors. If a volume of one-off work pushes the team toward Mango, compare that need with the recurring cost.

LH.pl supplies the platform and auto-installer. The guide places installation under Serwery then Autoinstalator and describes creating the database and WordPress user. The museum remains responsible for dashboard access, plugin versions, image sizes and updates affecting presentation. The PHP schedule specifies that older versions can incur an extra charge. Record the version used by the copy before reproducing the exercise and check available image functions.

Check the WordPress builder and support

LH.pl’s AI WordPress builder is activated in the panel for a new installation through a dedicated process. The documentation describes creation at no extra charge during the paid hosting period and advertises 49 PLN per year before tax at renewal to retain the builder and AI features of generated sites. It states that this is added automatically to the renewal invoice in this process. Based on the recorded Mango price, hosting plus builder totals 448 PLN before tax at renewal when the option applies, before the domain and other services. Ask how to remove the option if it is no longer useful.

The builder offers text and images. A new generation can replace existing content. To test settings, use a fresh installation with a fictional page and keep the original before generating again. After export, open the page at the destination and check whether blocks remain editable, images are present and plugin-dependent features remain accessible. The conditions for retaining AI features outside LH.pl and exact quotas require confirmation.

The website, help pages and documented menus are in Polish. LH.pl provides phone, chat and email contact channels. Chat is advertised from 8 to 22 on weekdays and from 8 to 16 on weekends, Polish time. The standard phone line closes at 20 on weekdays and 16 on weekends. The out-of-hours emergency line is for reporting outages. Confirm response languages and restoration times. For a media incident, send the time, affected page and expected file path. Explain whether the item still appears in the media library and whether the fault affects the original, a thumbnail or the entire page.

Practice selective media recovery

The supplied script creates a local WordPress site with an isolated SQLite database and generates a PNG illustration using PHP GD. It creates a media record and its sizes, then associates it with a page. The page initially announces opening at 10, then is corrected to 11. The test removes the original and one thumbnail from the fictional storage while retaining the media record in the database. It checks that the image remains attached to the page and that both expected files are absent. A copy of the original was kept separately at the start of the exercise.

The script puts only the PNG back in place and asks WordPress core to rebuild the media sizes. The original’s SHA-256 hash matches its hash before deletion. The readable thumbnail measures 150 × 150 pixels. The same media ID remains attached, the caption is intact and the page text still states an opening time of 11. The ZIP in “Prepare your site” contains the script and expected result. To replay it, use PowerShell with PHP, GD and PDO SQLite, the extracted WordPress folder, the SQLite Database Integration plugin, the WP-CLI file and a fresh working path on D:. The script creates its own command-line instance.

On a real site, start from the image URL and media record to identify its path, often in wp-content/uploads. Put the file back in place after verifying its provenance, then check the original in the media library. If a size is still missing and WP-CLI is available, run wp media regenerate ID_DU_MEDIA --image_size=thumbnail --skip-delete on the verification copy, using the relevant media ID. If the theme expects other sizes, record the registered sizes before choosing the scope. Check the page’s appearance and recent text. If the media record has disappeared, account for database references and attachment relationships before replaying this procedure.

To distinguish a storage error from a missing thumbnail, follow “Empty WordPress media library or missing thumbnails: find the right diagnosis”.

Compare the provider’s archive and working copy

Guidance for preparing a targeted restore. — Illustration by BlogPasCher.Open full-size illustration ↗

LH.pl advertises a daily backup retained for thirty days on a separate server. Its access guide specifies the backup server backup.lh.pl, using the main FTP account, with separate areas for web files and MySQL databases. The general restoration procedure still mentions fourteen copies in its download workflow, while its introduction and the recent access guide state thirty days. Confirm how many recovery points are actually available in the account. For the museum photo, open the web-files folder and choose a point when the original was present.

Download the chosen file before intervening and record its date, size and original path. Verify that the PNG opens independently. If a file with the same name already exists at the destination, back it up separately before writing. Check permissions and the site root from the panel. The database backup provides a fallback if an intervention deleted a record or references. In the selected scenario, the current database retains the media record and recent opening time. Restoring the entire database would revert other content to the date of the chosen recovery point.

A copy usable outside the account must contain files and a database from a consistent point in time if it is intended to reconstruct the entire site. Record both timestamps, the database engine and planned PHP version. To classify copies by the operations they support, consult “25 WordPress backup tools by recovery need”.

Prepare migration and check portability

LH.pl’s migration service describes moving a site and its email in, with a copy prepared and checked before the DNS switch. To leave LH.pl, prepare site files and the database on separate storage, then import them into an isolated destination. Check the relationship between the page, media record and file. WordPress content export can supplement this process. A content export alone does not include plugins, all their settings or media-library files in a self-contained set.

LH.pl states that builder pages use the block editor and that a plugin adds the assistant. On the exit copy, check blocks and images, along with theme elements. Keep the old copy available until you have observed a page opening and being edited on the new installation. After an address change, if media remain accessible in WordPress but return an error on the site, consult “WordPress images returning 404 after migration: repair files and their URLs”.

Mailbox and domain transfer follow a different schedule. Export messages according to the service and check the DNS records enabling receipt. Record the account owner, renewal date and transfer procedure for the extension. For a mailbox hosted at LH.pl, the help pages describe free email restoration through support, with a dated recovery point and a request from the authorized address. They advertise copies retained for thirty days and specify the case of messages retrieved by POP3 without a server copy. Access to web files and the database therefore does not constitute an email recovery plan.

Decide with a verifiable budget and recovery process

Mango is the plan highlighted for WordPress, but the museum can start by measuring actual usage. If all media, the database and mailboxes fit a smaller tier with room for the exercise, compare its cost over two years. If the media library is expected to grow quickly or the operation requires more PHP processes, compare Mango and Apple by renewal amount. The homepage places the servers at ATMAN in Warsaw. The exact backup location and server assignment for the chosen offering remain to be checked if the museum needs them for its inventory.

Two conditions make recovery verifiable. The chosen file must match the media record’s path. The corrected page must still display its new opening time after the file is restored. For a single media item, keep a copy of what exists at the destination before changing files. For a set of media items, produce a record by ID and check a sample of sizes before rerunning the entire library. If the original is absent from available backups, retrieve the source from the editorial team and verify that it matches the version used on the site. Once restored, also check that the public can open the file from the page and that its alternative text remains in place.

The provider states that removing the AI plugin leaves generated pages and content editable and removes generative features. Verify this on a copy of a representative page with its theme before relying on this portability. Finally, if the museum bundles its domain with hosting, review the promotion terms. The authinfo code issuance guide mentions prior renewal for domains registered under a promotion. Record this condition and the possible exit date in the budget.

Prepare your site

• Empty WordPress media library or missing thumbnails: find the right diagnosis
• 25 WordPress backup tools by recovery need
• WordPress images returning 404 after migration: repair files and their URLs
• Download the media recovery exercise