Choose AutoCAD or AutoCAD LT by the work, not the price

The difference between the full and lower-tier editions does not concern line quality or the DWG format. AutoCAD LT is suitable for serious 2D production work. It becomes the wrong choice when an employee needs to create three-dimensional geometry, connect corporate data sources, or run extensions written in something other than AutoLISP.

That is why arguing that "LT is limited" does little to help procurement. Break down the working day of a specific department into operations. If eight hours go into plans, sections, callouts, blocks, sheets, and PDFs, the license difference may barely be noticeable. If a drawing becomes the source of a schedule, receives a point cloud, or passes through an industry toolset even once a week, the limitation will appear at the most expensive moment.

This comparison follows the current product logic, not old reference sheets. AutoLISP makes that distinction important: current LT releases can run these programs, so the claim that "LT has no automation at all" is no longer true. But this change does not make the two editions identical.

LT covers full 2D documentation production

AutoCAD LT is enough when the deliverable is a set of two-dimensional DWG files and sheets, and standard commands create the geometry. Lines, polylines, hatches, dimensions, text, tables, layers, blocks, external references, and plotting do not become simplified substitutes. For an ordinary drafter, the quality of the final PDF does not depend on which edition assembled it.

LT includes dynamic blocks, the Blocks palette, instance counting, DWG version comparison, markup tracing, sheet sets, and publishing. You can attach DWG files, images, DWF, DGN, and PDF files, import geometry from a PDF, customize the interface through CUI, and monitor system variables. Autodesk's official features page explicitly calls the product a tool for 2D design and documentation. That description is more accurate than the familiar label "lightweight viewer."

The boundary does not appear because a plan is complicated. LT can handle many layers, annotative objects, viewports, and references when the computer and file structure suit the project. The boundary appears in where the data comes from and how the user processes it.

Instead of asking whether a department draws complicated objects, ask these questions:

1. Does the employee create spatial geometry, even if the final sheet remains two-dimensional?
2. Do they obtain properties from a model, database, or set of other drawings?
3. Do they run an add-in without which the team cannot issue the set?
4. Do they need industry objects and AutoCAD catalogs?

Four "no" answers make LT a strong candidate. One "yes" does not automatically require the full edition, but it does require a test with a real file.

Opening a 3D model is not the same as developing it

AutoCAD LT preserves compatibility with DWG files that contain three-dimensional objects, but it does not provide the complete toolset for creating and modifying them. This is the most dangerous confusion in the comparison. A manager opens a sample file, sees a solid on screen, and decides that the product supports 3D work. The designer receives the license and finds that they cannot build or properly correct the required part.

Autodesk documentation states the limit precisely: AutoCAD LT for Windows does not support the creation of three-dimensional surfaces and solids, and it offers limited modification of three-dimensional objects. The full edition includes solid, surface, and mesh modeling, extrusion, union, subtraction and intersection operations, section creation, visual styles, and visualization tools. LT can retain many previously created objects without damaging the DWG, but object preservation does not give the author control over it.

The practical effect depends on the role:

• An architect who receives a spatial base only for checking and issues a separate 2D plan may be able to use LT.
• A designer who extrudes a profile, cuts holes, and derives views from a solid cannot.
• A process engineer who edits an equipment layout in 3D cannot.
• A drafter who receives approved projections and adds dimensions probably can.

There are less obvious limits too. LT cannot attach point clouds or NWD and NWC coordination models. A drawing in which the full edition has already attached a cloud may open, but the employee does not get a proper process for indexing, attaching, and working with the original scans. Similarly, the ability to see someone else's perspective does not make LT a view-management tool: the documentation says you can turn perspective off but cannot turn it on.

Do not assign LT because "we do not deliver 3D." Many departments do not deliver a model to the client but use one as an intermediate tool for projections, clashes, sections, or counting. Test how the drawing is produced, not the delivery format.

Check dynamic blocks with parametric constraints separately. LT can use dynamic blocks and change available properties, but its constraint-authoring capabilities differ from those of the full edition. Autodesk's help on working with drawings says LT displays and lets users edit existing geometric and dimensional constraints, but does not create new ones. In the Block Editor, you can change a value or delete a constraint, yet you cannot add a new constraint parameter. That does not hinder a catalog user, but it limits the author of a corporate library.

Finally, do not confuse the thickness of a two-dimensional object with a solid model. A polyline with a nonzero thickness can look three-dimensional, and a 3D polyline can have vertices with different Z coordinates. Neither fact gives LT solid-modeling operations. In the pilot, ask the engineer to modify the object exactly as they do in a project rather than merely display it: move a face, cut a hole, recalculate a section, and derive an updated view. Those actions reveal the difference.

AutoLISP in LT helps but does not replace an extension platform

Current AutoCAD LT releases run AutoLISP, so simple corporate commands, layer checks, and batch corrections no longer automatically require the full edition. Autodesk lists support for LSP, FAS, and VLX files. A program can invoke built-in commands, read system variables, create and change objects in the drawing database, request input, and display DCL dialogs.

That is a meaningful change for departments that have bought the full edition for years because of a dozen small LISP commands. Retest such code in LT. The short program below counts block references throughout the current drawing and shows an output shape that is easy to verify:

(defun c:COUNTBLOCKS (/ ss total)
  (setq ss (ssget "_X" '((0 . "INSERT"))))
  (setq total (if ss (sslength ss) 0))
  (princ (strcat "\nBlocks found: " (itoa total)))
  (princ)
)

After loading the file with APPLOAD and running COUNTBLOCKS, the command line returns a string such as Blocks found: 184. This is a real test of the interpreter, object selection, and a custom command rather than a button demonstration.

But AutoLISP covers only part of automation. Autodesk's "About Supported Programming Interfaces" table shows the API difference: LT does not support ObjectARX, managed .NET libraries, VBA, or the desktop JavaScript API. ActiveX is available in LT only to a limited extent through AutoLISP, and the full Visual LISP IDE is absent. The official comparison also assigns access to the Autodesk App Store to the full edition.

The consequence is straightforward: you cannot assume that an extension with a DLL, a .NET module, an ARX plug-in, or an old VBA application works in LT just because an LSP file sits beside it. Sometimes the vendor has made a separate LT version, sometimes part of the functionality can be rewritten in AutoLISP, and sometimes the architecture requires the full edition. The documentation for the particular add-in and a test workstation provide the answer.

I do not recommend promising to rewrite a large plug-in in advance to save on licenses. Development, testing on new releases, and support often consume the difference. Porting makes sense for short, stable commands with a clear owner.

Inventory automation by examining how the application loads, not by looking at custom command names. The same ribbon button may run an LSP file, invoke a command from a DLL, or pass a file to a separate program. Open the CUI settings, support folders, and loaded-application list, then match every required command to its files. The .lsp, .fas, and .vlx extensions justify a test in LT. The .dll, .arx, and .dvb extensions immediately require separate compatibility confirmation.

Even pure AutoLISP must run against a project copy. The code may call a command that LT lacks, access a limited ActiveX object, or depend on an industry toolset. A good acceptance test checks more than the absence of an error message. It compares the number of created objects, layers, properties, text output, and final DWG with the result from the full edition.

External references and external data solve different problems

AutoCAD LT can assemble a project from external references, but that does not make it a data-integration system. An xref maintains a link to another DWG and reloads changes from the source file. You can attach a PDF or DGN as an underlay and scale or clip an image. This is often enough for coordinating two-dimensional plans.

Departments commonly mix four different processes under the phrase "external data":

• attaching another drawing or underlay;
• linking table cells to a spreadsheet;
• extracting attributes and object properties into a schedule;
• reading GIS, engineering databases, or corporate systems directly.

LT handles the first process confidently. For the second, test the particular platform, format, and update direction. The third is especially deceptive: LT can open a drawing with a data-extraction table created in the full edition, but Autodesk documentation warns that LT cannot update the extracted data or change its associated data link. A table visible on the sheet does not prove that the employee can rebuild the schedule after changing blocks.

The fourth process usually needs the full edition, a specialized toolset, or a separate application. Map 3D, for example, uses FDO providers to access spatial files and databases. Plant 3D maintains a project structure and piping data. An ordinary xref cannot replace these capabilities because a reference passes graphical DWG content, not the rules of a domain database.

The test must reproduce the entire change cycle. Change attributes in several blocks, add a new source file, update the schedule, close the DWG, open it on another workstation, and issue a PDF. If the employee must ask a colleague with the full edition to run one command, LT has already created a dependency. Sometimes a single designated full workstation makes this acceptable. Sometimes it creates a queue before every issue.

Do not assess a spreadsheet link from one screenshot either. The command set and supported sources vary between editions and between Windows and macOS. Test both directions required by the department: changing the source sheet and updating the table in the DWG, and, if the process allows, writing corrections from the DWG back to the source. Move the set to another folder as well to see whether the link survives a path change.

If the task only needs a block schedule, do not assume an external database is mandatory. Attributes, ordinary tables, the counting command, and a short AutoLISP program can sometimes make the process more reliable in LT than a complex link. Approve that substitution as a new procedure. Quietly turning an automatically updated schedule into a manual table creates discrepancies that appear only during plotting or procurement.

The full edition includes industry toolsets

The subscription difference covers more than the base AutoCAD commands. Autodesk supplies the Architecture, Mechanical, Electrical, Map 3D, MEP, Raster Design, and Plant 3D specialized toolsets with the full edition. Each is installed separately, but entitlement to them is part of the AutoCAD including specialized toolsets offering. LT does not include them.

This is the hidden cause of many failed comparisons. Procurement looks at two similar base AutoCAD windows and misses the fact that an engineer opens a third shortcut. Their file may contain intelligent walls, electrical symbols, mechanical parts, piping, georeferenced objects, or processed raster data. The DWG may open in LT through proxy objects, but the process for creating and changing the industry content disappears.

Check these departments with particular care:

• site planning and GIS, if employees connect spatial sources and coordinate systems;
• electrical, if they use project structure, schematic checks, and component catalogs;
• mechanical, if production depends on standard-parts libraries and calculation tools;
• process piping, if the project lives in Plant 3D rather than a set of independent lines;
• archives and digitization, if Raster Design cleans scans and converts raster geometry.

An ordinary inserted image is available in LT. Raster Design tools for cleanup, correction, and raster-to-vector conversion belong to a different level. Likewise, a manually drawn wall line is not an Architecture object that knows its properties and interacts with other objects.

Do not give an employee LT merely because they need an industry toolset "rarely." A rare operation can determine the integrity of the whole project. First establish whether one specialist can centralize it without constant file transfers and loss of responsibility.

2D collaboration rarely requires the full edition

LT usually retains the tools needed to review, exchange, and issue standard drawings. It works with DWG, compares versions, supports Trace, shares a controlled copy, and publishes sheets. Cloud storage and access through web and mobile applications belong to both Autodesk offerings, although particular service availability depends on the subscription and account.

Within a local project, LT supports relative external-reference paths, eTransmit packaging, sheet sets, templates, plot styles, and the familiar paper-space model. These functions determine the reliability of most 2D documentation sets. The full edition will not fix poor file names, absolute paths to a personal drive, or missing fonts.

Separate collaboration into preparation and consumption. An LT employee can receive a current DWG, add comments, correct geometry, refresh ordinary references, and issue a PDF. They should not own a stage that requires attaching a point cloud, updating an extraction table, running an industry check, or launching an incompatible plug-in.

Create one test electronic package with ETRANSMIT. The result folder should contain the main DWG, every external DWG, images, fonts when their transfer is permitted, plot-style tables, and a package report. Open it on a clean workstation without the author's network paths. This exercise says more about LT suitability than a comparison of dozens of marketing checkmarks.

A group manager should note one more detail: different editions do not remove the need for one standard for templates, layers, paths, and DWG versions. A mixed environment works well when roles are defined and files are tested. Without rules, an employee using the full edition can easily create an object that a colleague in LT can see but cannot maintain.

LT suits departments with a stable work boundary

Assign AutoCAD LT by role, not by a job title in the organization chart. Two engineers with the same title may perform different operations. One documents approved projections, while the other builds the base in 3D and manages schedules.

LT is usually enough for these groups:

• production drafters who prepare 2D plans, diagrams, details, and sheets;
• specialists correcting as-built diagrams when the source arrives as ordinary geometry;
• reviewers who add markup, compare DWG files, and resolve simple comments;
• employees who maintain standard blocks, borders, title blocks, and templates without .NET or ARX add-ins;
• training or administrative units that need a precise DWG editor rather than a modeling system.

The full edition is necessary for roles that create or change 3D solids and surfaces, attach point clouds, use coordination models, run corporate DLL and ARX extensions, work in specialized toolsets, or own live extraction of project data. It is also safer for a CAD administrator who must diagnose unfamiliar objects and support several types of automation.

A practical middle arrangement gives LT to most production workstations and reserves a small number of full licenses for modelers, coordinators, and administrators. It saves money only under three conditions. The queue for the full edition does not delay issue, every operation has a known owner, and files remain editable during transfer.

Group leaders often benefit from the full edition even when they do little drafting themselves. They receive files from different contractors, find the cause of incompatibility, restore references, and decide how to convert objects. A narrow production role is predictable; the role of technical arbiter is not. Save on workstations with a stable set of actions, not on the person who receives every exception.

The same principle applies to temporary employees and contractors. A short project does not make LT sufficient. The lower-tier edition fits someone responsible for manually documenting approved projections. If they were hired specifically for a point cloud, an industry model, or a corporate plug-in, a limited license defeats the purpose of their specialty.

Do not use a floating "shared" full license as an excuse until you have checked named-user rules and the actual schedule. Licensing and access terms change, so verify them against the current Autodesk or supplier offer rather than an old purchase.

For an organization in Kazakhstan, the supplier's role can extend beyond issuing a license. GSE.kz sells and integrates Autodesk software and can connect the license mix with workstations, infrastructure, and support, but the customer still needs to prepare the role inventory.

Savings disappear when one required operation must be handed off

LT costs more than the full edition when an employee regularly stops at a function that cannot be delegated without wasting time. A typical failure starts quietly. The department buys LT after testing a couple of completed plans. The drawings open, dimensions can be edited, and the PDF comes out correctly.

A month later, a project arrives with a dynamic equipment schedule. The drafter changes block attributes and sees old numbers in the extraction table. The update command is unavailable in the required process. The file goes to a colleague with the full edition, who updates the table but is already working on another copy of the DWG. Before issue, someone moves the current table into an outdated drawing. The error did not come from the DWG format or poor skill. Procurement tested the opening of a result but not its production cycle.

The same thing happens with a single operation on a 3D solid or industry object. Five minutes of work turns into a request, file transfer, wait, and repeated check. If these episodes are frequent, coordination consumes the savings. If the operation occurs once a quarter and can be scheduled, one designated full workstation remains sensible.

Count more than the subscription price. Include waiting time, support for two processes, script rewrites, training, risk of a late issue, and workstation cost. Do not assign LT an automatic hardware saving: a heavy two-dimensional DWG with many references and raster files still needs memory, fast storage, and capable graphics.

Use one simple pilot measure: record how many times over two weeks a user cannot complete an operation independently and how many minutes the handoff takes. Record the command, object type, and file rather than the impression that "the edition is weak." After ten working days, recurring causes will show whether the person needs a full license all the time or whether only a specific process owner needs it.

A control set decides the issue, not a feature table

Choose AutoCAD or AutoCAD LT using a copy of the most awkward completed project. A tidy training DWG almost always validates LT because it contains no broken references, corporate add-ins, old proxy objects, or live schedules. Use a set on which the department has already lost time.

The pilot should pass five checks:

1. Open the main file and restore every external reference without manually substituting paths.
2. Change a typical object, update associated tables, and issue the sheet again.
3. Run every required custom command and record its technology: AutoLISP, .NET, ARX, VBA, or something else.
4. Perform the operation involving 3D, a point cloud, or an industry object if it has occurred in any working project.
5. Build a transfer with eTransmit and open it on a second clean workstation.

Mark each action with one of three results: "LT performs it," "another employee performs it," or "the full edition is required." The second result is acceptable only when it includes the owner's name and an acceptable wait time. The comparison then becomes a responsibility map.

Also record the application version, operating system, list of loaded LSP files and add-ins, types of external sources, and names of specialized toolsets. "We use AutoCAD" is too vague for procurement. "We edit 2D DWG files, run three LSP programs, refresh an Excel link, and attach an RCP once a week" immediately exposes the boundary.

Do not apply one pilot result to the whole office without separating profiles. Define at least three control roles: geometry author, production drafter, and data coordinator. Each opens the same file for a different purpose. If LT passes the production scenario, that supports buying LT for those workstations but says nothing about the modeler.

After the decision, keep the protocol with the workstation standard. It should retain the tested release, list of required commands, known limitations, and employee who performs full-edition operations. When AutoCAD is updated or a plug-in or data source changes, repeat only the affected checks. The decision then remains testable instead of becoming a permanent argument or depending on the memory of the person who ran procurement several years ago.

AutoCAD LT does not lose to the full edition in 2D accuracy and need not be a temporary compromise. It is an appropriate permanent tool for a clearly bounded production role. Full AutoCAD is necessary where an employee creates a model, owns the data, or extends the application beyond AutoLISP. Buy the boundary of responsibility that you verified on a file, not the longer feature list.