NBDesigner System Requirements for WordPress & WooCommerce

Applies to Cmsmart Product Designer (NBDesigner) 2.17.0 · Updated October 2026. Confirms the WordPress, WooCommerce and PHP versions NBDesigner needs today, plus the server settings its upload and print-ready PDF pipeline depend on.

In short

  • Get the server right once and you stop losing hours to blank product pages, failed logins to the online designer, or print-ready PDFs that time out mid-render.
  • NBDesigner's in-browser canvas and server-side rendering lean on specific PHP extensions, upload limits, and your WordPress/WooCommerce version — not just "WordPress runs fine."
  • It takes a five-minute PHP info check, a handful of php.ini values, and — if your host won't change them — Cmsmart can configure or migrate the hosting as part of setup.

NBDesigner system requirements are more specific than a generic WordPress checklist: Cmsmart Product Designer can look perfect in the demo and still show a blank product page, refuse to save a design, or hand you a print file with the wrong colors the moment it lands on a server that misses a few exact settings — and nearly every one of those failures traces back to PHP, WooCommerce, or an upload limit your host configured years ago and never revisited.

What does it cost you when your server misses NBDesigner's requirements?

Cmsmart Product Designer (NBDesigner) runs its own JavaScript canvas plus server-side PDF rendering, so a host that satisfies a generic WordPress checklist can still miss the PHP extensions, upload limits or WooCommerce version NBDesigner needs — blank product pages, stuck logins to the online designer, and failed print-ready exports usually trace back to exactly one of these gaps.

The pattern repeats across support tickets from print shops and POD stores alike:

  • Blank or partially loaded product page. The designer's modern editor needs enough PHP memory and a current browser-facing build of WordPress/WooCommerce; a tight memory_limit or an ancient PHP build cuts the page off mid-render.
  • "Can't log in to admin Online Designer" or the selected product shows blank. Classic symptoms of a low PHP configuration limit (execution time, memory) rather than a broken install.
  • JPG proof downloads fail silently. NBDesigner's own Settings screen flags this directly: JPG design downloads need the PHP Imagick extension enabled, or that one file type never generates.
  • Uploads get truncated or rejected. NBDesigner's own Upload design settings let you cap file size per product (Cmsmart's demo store sets this to 100 MB) — but if the host's upload_max_filesize is lower than that, the host silently wins and customers see a rejected upload.
  • Print-ready PDFs stall or render with missing colors. The cloud and server renderers depend on the same PHP extensions (ImageMagick/GD) and a reachable Ghostscript binary; when one is missing, the Overview screen raises a system-health alert instead of a finished PDF.

The cost rarely shows up as a single outage — it shows up as a support ticket cycle: (hours your team or your host spends diagnosing) × (your blended hourly rate) + (orders paused while the designer is down) × (your average order value). On a store doing even a few web-to-print orders a day, that formula adds up fast, and it repeats every time a host-level update quietly changes a PHP setting.

Checking NBDesigner system requirements in Settings General: the JPG design download option requires PHP Imagick
NBDesigner's own settings screen calls out the PHP extension a feature needs — JPG downloads require PHP Imagick.

What does a correctly provisioned product designer look like for your store?

When your server already matches NBDesigner's requirements, Cmsmart Product Designer opens instantly on every device, saves every design on the first try, and hands production a print-ready PDF with no manual troubleshooting — the infrastructure disappears and only the buying and designing experience is left.

Example scenario: a buyer opens your invitation product page on their phone at 10 p.m., taps the design button, builds their layout in the online editor, and adds it to cart without a stalled spinner or an unresponsive page. At checkout, the design preview travels with the line item. The next morning, your team opens the order, clicks Create PDF once, and a print-ready file with the correct bleed and color profile is sitting in the downloads list before the first coffee, instead of stuck in a queue because Ghostscript couldn't be found.

Cmsmart insight: in our setup work, the single most common reason a designer that worked fine in testing breaks in production is a shared-hosting plan that silently reset upload_max_filesize or disabled an image extension during a routine host update. Check the server values again after any hosting-side change, not just at launch.

How does Cmsmart's product designer stack meet NBDesigner system requirements?

Cmsmart Product Designer (NBDesigner) is built on five layers — WordPress/WooCommerce core, the PHP runtime and its extensions, upload handling, the print-ready output pipeline, and the license/update layer — and Cmsmart verifies all five are correctly configured as part of every setup engagement, in the plugin today or built around it as custom development.

Five building blocks, and what each one needs to run well:

  • WordPress + WooCommerce core — the storefront, cart and checkout NBDesigner's design data attaches to.
  • PHP runtime and extensions — Imagick or GD for image processing, JSON support, and enough memory/execution time for the modern editor and the server-side renderer.
  • Upload and storage settings — upload_max_filesize, allow_url_fopen, and fix_pathinfo, which NBDesigner's own system-check guidance calls out directly.
  • Output pipeline — Ghostscript/ImageMagick (or Cmsmart Cloud's managed rendering) turning a saved design into a print-ready PDF with bleed, embedded fonts and the right color profile.
  • License, updates and health — the Plugins screen and NBDesigner's Overview screen, which raises a system-health alert the moment ImageMagick, GD, Ghostscript or the uploads directory stop behaving (added in the 2.10.0 changelog), rather than letting a render fail silently.
WordPress Plugins screen showing the active Cmsmart Product Designer row with its version and WooCommerce listed as a required plugin
The Plugins screen confirms the version you're running and lists WooCommerce as NBDesigner's one hard plugin dependency (this capture is from a newer development build; your own Plugins screen will show the 2.17.x release number).
NBDesigner storefront product page loading normally with the Start and upload design button
What a correctly provisioned storefront looks like: the product page and "Start and upload design" button load without delay.
RequirementPlugin default (in NBDesigner today)When it becomes custom development
WordPress / WooCommerce / PHP floorWordPress 5.6+, WooCommerce 8.0+, PHP 8.0+ (plugin readme)Planning the upgrade path when your store still runs an older stack across multiple sites
Upload limitsConfigurable per product in Settings > Upload design (Cmsmart's demo store caps it at 100 MB)Negotiating host-level upload_max_filesize/post_max_size increases on locked-down shared hosting
PDF/image extensionsUses PHP Imagick/GD and Ghostscript when presentInstalling or compiling these on a restrictive host, or moving to a VPS that allows them
Health monitoringPer-site Overview alert when a dependency is missingA central dashboard across a multi-store or multi-vendor install

What's the business value of getting system requirements right the first time?

Matching your server to NBDesigner's requirements before launch turns Cmsmart Product Designer from a support liability into a reliable sales channel — fewer abandoned designs, fewer reprints from bad color output, and a support team that spends its time on customers instead of PHP configuration.

BenefitHow it shows up in your businessKPI to track
Fewer abandoned designsThe editor loads and saves on the first try instead of timing out mid-sessionDesign-started vs. design-completed rate
Fewer reprintsPrint-ready PDFs carry the correct bleed and color profile instead of a fallback renderReprint rate / cost per reprint
Less support timeStaff aren't opening host tickets to chase "blank page" or "upload failed" reportsSupport hours per order
Faster go-liveRequirements are checked once, during setup, not discovered after launch dayDays from install to first live order

Rough-cut worksheet: (support hours per month spent on designer/PDF issues) × (blended hourly cost) + (reprint rate × cost per reprint × monthly order volume) = your current cost of an unverified server. Run the same numbers after setup to see what a correctly provisioned stack is worth to your store.

Cmsmart Orders dashboard showing order counts in production and revenue for the last 30 days
A correctly configured install means every one of these orders reaches production with a usable design file — no manual rework.

How do you set up and configure your server for NBDesigner?

Setting up Cmsmart Product Designer (NBDesigner) correctly means checking your PHP, WordPress and WooCommerce versions against the plugin's floor, confirming a short list of php.ini values, and testing one full order before you consider the store launch-ready.

  1. Check your current WordPress, WooCommerce and PHP versions from Tools > Site Health or your host's control panel.
  2. Compare them against NBDesigner's own floor — WordPress 5.6+, WooCommerce 8.0+, PHP 8.0+ (plugin readme) — and note that PHP's currently supported branches start at 8.2, so PHP 8.0 and 8.1 no longer receive security fixes; treat the plugin's floor as a minimum to clear, not a target.
  3. Ask your host (or check phpinfo) to confirm fix_pathinfo = 1, allow_url_fopen = on, and that the server supports JSON — NBDesigner's own system-check notes call these out directly.
  4. Raise upload_max_filesize and post_max_size to at least match what you configure in Settings > Upload design (Cmsmart's demo store uses 100 MB per file).
  5. Confirm PHP Imagick (or GD) is enabled if you want customers to download JPG proofs — NBDesigner's Settings screen flags this requirement next to the option.
  6. Confirm Ghostscript and ImageMagick are reachable on the server, or enable Cmsmart Cloud rendering instead, so print-ready PDF generation doesn't fail at the order stage.
  7. Set the WordPress memory_limit to at least 256 MB, in line with WooCommerce's own published server requirements.
  8. Activate the plugin and check the Plugins screen shows no "Requires: WooCommerce" warning.
  9. Open Settings > Output to set your watermark, bleed and embedded-font preferences before your first real order reaches production.
  10. Run one full test order — design, add to cart, checkout, then Create PDF from the order screen — before you call the store launch-ready.
NBDesigner Settings Output screen showing watermark, bleed and AI preflight configuration
Settings > Output is where bleed, embedded fonts and AI preflight are configured once your server requirements are confirmed.

Going further: when do you need custom development instead of a settings tweak?

Most system-requirement issues are a configuration fix, but a few need more than a settings screen — Cmsmart builds the hosting, monitoring or integration work around NBDesigner as custom development when a store's infrastructure genuinely can't be reconfigured from wp-admin.

  • Locked-down shared hosting. When a host won't raise upload_max_filesize or enable Imagick, Cmsmart builds a managed hosting or VPS migration so the designer runs on infrastructure you control.
  • Multi-store or multi-vendor health monitoring. NBDesigner's Overview alert covers one site; running the designer across several stores calls for a custom dashboard that rolls those health checks up in one place.
  • Staged PHP upgrades. For stores with heavy customization, Cmsmart builds a staging pipeline so a PHP version bump is tested against your specific design templates and print options before it reaches production.
  • ERP/MIS or print-API connections. Server-to-server integrations often need PHP extensions or authentication a generic host doesn't provide out of the box — Cmsmart builds (custom development) the connector and the server configuration it needs together.

Every custom engagement follows the same delivery model: discovery, solution design, sprints, QA, launch, and ongoing support — see Cmsmart's product designer customization service or how we run a project on Ecommerce Projects.

Get my server and designer setup checked

Why work with Cmsmart on your product designer infrastructure?

Cmsmart has built and supported Cmsmart Product Designer (NBDesigner) installs since 2012 as a Netbase JSC division, with 6,300+ client projects delivered and a 4.2-star Trustpilot rating — so the requirements check above comes from setups we've actually run, not a generic checklist.

Cmsmart is a Netbase JSC division, in business since 2012, with 6,300+ client projects and 1,800+ live stores running today across 80+ countries. Reviewers who've run NBDesigner for years back this up directly:

"We have had the NB Designer plugin installed for three years and have experienced absolutely no problems during that time. It is wonderful to see their commitment to continuous development... The designer works exceptionally well across all devices." — Web Developer, Trustpilot

Rated 4.2/5 on Trustpilot (404 reviews) — see more real client work on Ecommerce Projects or explore the plugin itself on the Cmsmart Product Designer product page.

Frequently asked questions

What's the minimum WordPress, WooCommerce and PHP version for NBDesigner?

NBDesigner's published floor is WordPress 5.6+, WooCommerce 8.0+ and PHP 8.0+ (plugin readme). Because PHP 8.0 and earlier no longer receive security updates and current WordPress.org requirements (2026) and WooCommerce server requirements both recommend PHP 8.3+, treat the plugin's floor as the minimum to clear, not the version to run in production.

Why does my designer show a blank product page even though I technically meet the minimum?

This is almost always a low PHP configuration limit — memory or execution time — rather than a broken install. Raising memory_limit and checking fix_pathinfo, allow_url_fopen and JSON support (per NBDesigner's own system-check guidance) resolves most cases.

Do I need Ghostscript or ImageMagick installed?

Yes, if you want print-ready PDF rendering and JPG design downloads to work locally. NBDesigner's Settings screen flags the Imagick requirement directly next to the JPG download option, and the Overview screen raises a system-health alert when ImageMagick, GD or Ghostscript aren't reachable. Cmsmart Cloud rendering is the alternative when your host won't install them.

Can Cmsmart check or fix my server configuration for me?

Yes — this is a standard part of NBDesigner setup engagements. When a host's shared-hosting plan can't be reconfigured, Cmsmart builds the hosting migration or VPS setup as custom development; see web-to-print solutions for the broader setup service.

Does upgrading PHP break my existing designs or orders?

Not when the upgrade is tested first. Cmsmart's 2.14.1 release was verified on WordPress 7.1 with WooCommerce 11.0.1, PHP 8.3.31 and HPOS enabled, with existing orders round-tripping their design data intact — the same staged-testing approach is what we recommend before any store raises its PHP version.

How do I confirm my store is compatible with WooCommerce's High-Performance Order Storage (HPOS)?

Check the Customer Design approval box loads on the HPOS order screen (woocommerce_page_wc-orders) and that a test order's design data survives checkout — both are part of the verified test run behind the 2.14.1 release and the setup checklist above.

Ready to install or compare? See the free trial download and activation guide or the full NBDesigner installation walkthrough next.

How much PHP memory_limit does NBDesigner require?

NBDesigner's documented minimum is 256 MB of PHP memory_limit. Lower limits are a common cause of a blank product-designer page or a design that silently fails to save, even when WordPress, WooCommerce and PHP versions all meet the stated minimums.

Why do upload_max_filesize and post_max_size need to match NBDesigner's upload caps?

These two PHP settings cap how large a file a customer can upload before WooCommerce ever sees it. If either value sits below NBDesigner's design-upload limit, high-resolution artwork or print files can be rejected or truncated during upload, independent of memory_limit or PHP version.

How do I pay securely?

Contracts and payments go to the company, Netbase JSC: plans are paid through PayPal; services are invoiced by Netbase JSC under a written proposal and paid by bank transfer to Netbase JSC's company account or by PayPal Business. Cmsmart (Cmsmart Ecommerce) is the ecommerce brand of Netbase JSC, a company based in Hanoi, Vietnam.

How do I contact Cmsmart or get a quote?

Message the Cmsmart team on WhatsApp at +84 937 869 689 or email project@cmsmart.net; the contact page at cmsmart.net/contact lists every channel, and Request a quote (cmsmart.net/project-proposal) sends a project brief. Customers with a licence open a ticket from the dashboard.

Further reading